Neil, when we use the same certificates to sign the distribution package of an app built in the old version of DPS it works well with the application loader. Using these same certificates on the Adobe DPS app signing tool to sign an app built in DPS 2015, it doesn't work well. Screenshots below:
Another thing, we are building this app to upgrade an old DPS app. But the old one don't have in-app purchase, and for this one, by default we need to configure ID for collections – even if they are free. This could be impacting?
Neil, what's the difference between version of marketing and version? The marketing version that we put when we are building is the same that we need to use on itunes? We need to upload it today. We reviewed our certificates, and apparently they are correct. What's the meaning of bundle path 'Payloa...
We did this. Actually it's basically the same that we do with android apps, right? I'm putting step by step. Here what we did:we did the buildwe downloaded a unsigned buildwe've signedonce we try to upload to app store this error appears
Klaasjan, we downloaded our unsigned-app and we used the Adobe Publishing signing tool to sign with distribution certificates, but it just generates a .ipa, not a zip for distribution. What should we do to generate the zip?