Ive answered on of my questions about the app being a older version. I didn't know you had to publish the layouts, after I did that the App was up to the current version.
But, I still cant seem to figure out why the AEM signing tool wont work and the older version will.
I have the developer certificate now. But my developer certificate and mobile provisioning will only work in the "adobe publishing signing tool", and not the "AEM signing tool" ?
When I do sign the app with the adobe publishing signing tool and upload the app to my ipad, its a very old version of the App, how is that possible ?
To test an app, you need to use a development certificate and a mobileprovision file that includes the UDIDs of your devices. To distribute an app within your organization, you need to sign the app with an Enterprise certificate and mobileprovision file. Creating an using an Enterprise certificate requires an Enterprise iOS subscription with Apple ($299/yr instead of $99/yr).
Thanks for that info Bob. Im trying to sign this for a in-house distribution to internal iPads which will never see a iTunes store. The app will be distributed through air watch. What time of certificate and mobile provisioning should I be using?
To answer your previous question, you should not sign a preflight app with a distribution certificate. Under the hood, a preflight app is set as a development app, while a non-preflight app is set as a distribution app. You can sign either app type with either certificate. However, while there is a reason to sign a non-preflight (distribution) app with either a development certificate (for testing entitlement) or a distribution app (for submitting to the store), there is never a good reason to sign a preflight (development) app with a distribution certificate. If you submit a preflight/distribution app to the store, you can't control the visibility of your content through publishing—everything appears, including incomplete articles—and entitlement doesn't work.