You can download the unsigned-app from the DPS Portal and use the DPS App Signing utility to generate your distribution zip.
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:
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, 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'?
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.