Accepted Solutions (1)

Accepted Solutions (1)

Answers (15)

Answers (15)

Christophe_Joss

Employee

24-08-2015

Just FYI, I'm following up with this customer offline but I want to mention I did run a test of my own with my account and I'm not getting any error, just the same warning.

The DPS 2015 Distribution binary has uploaded.

Screen Shot 2015-08-24 at 09.58.26.png

dpsa53128946

22-08-2015

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:

Captura de Tela 2015-08-22 às 12.55.44.pngCaptura de Tela 2015-08-22 às 12.56.41.png

Captura de Tela 2015-08-22 às 12.57.09.png

dpsa53128946

21-08-2015

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_Enns_-_Ado

Employee

21-08-2015

Information about the version field is available at Digital Publishing Solution Help | Change the app version number. This topic is available via the "learn more" link directly next to the version field in App Builder.

You should call enterprise support for assistance with your signing issue, especially since it's time critical.

Neil

dpsa53128946

21-08-2015

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 'Payload/Jupiter.app'?

Neil_Enns_-_Ado

Employee

21-08-2015

Are you sure the certificate you used to sign the file was the one from Apple, and was the distribution certificate? Given the error message ("not signed using an Apple submission certificate") that sounds suspiciously that the certificate you used isn't correct, or wasn't the right one.

Neil

dpsa53128946

21-08-2015

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:

  1. we did the build
  2. we downloaded a unsigned build
  3. we've signed
  4. once we try to upload to app store this error appears

dpsa53128946

21-08-2015

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?