iOS Enterprise App
Posted: 03. May 2018, 18:06
We have just started testing the use of in house Enterprise iOS app in Silverback and are having an issue with the installation. The app we are using can be side loaded from the IPA file thru iTunes onto the device without issue but we must go into Settings>General>Device Management to trust the developer (which is us). If I try to install the same app thru Silverback via push or from the App Portal the status changes to Installing but then goes back to "install" after a few seconds with the app not getting installed.
What I am trying to figure out is if the problem is with the plist file or the IPA file? For the PLIST we are using the template provided from the HelpCenter https://help.matrix42.com/20Unified_End ... prise_apps. We are not using any parts of the original PLIST that was provide with the IPA file from the developers, just an updated version of the template from the link. As for the IPA file, I am assuming that since I can side load it from iTunes the app is good and not the cause. The last piece is the trust notice that one would get with a Enterprise app. However, if you deploy the Enterprise App with an MDM tool (I.e. Silverback) you should not have to worry about trusting the developer as the MDM system already manages this, correct?
Any suggestions would be appreciated.
What I am trying to figure out is if the problem is with the plist file or the IPA file? For the PLIST we are using the template provided from the HelpCenter https://help.matrix42.com/20Unified_End ... prise_apps. We are not using any parts of the original PLIST that was provide with the IPA file from the developers, just an updated version of the template from the link. As for the IPA file, I am assuming that since I can side load it from iTunes the app is good and not the cause. The last piece is the trust notice that one would get with a Enterprise app. However, if you deploy the Enterprise App with an MDM tool (I.e. Silverback) you should not have to worry about trusting the developer as the MDM system already manages this, correct?
Any suggestions would be appreciated.