- Jamf Nation Community
- Products
- Jamf Pro
- Re: Deploying in-House iOS app - "the app cannot b...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Deploying in-House iOS app - "the app cannot be installed because its integrity could not be verified"
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 01-28-2021 10:19 AM
Good afternoon!
We are dabbling with trying to deploy an in-house app to some of our ipads. We have a developer signed app made, but when added and scoped to an iPad and "installed" from self service, if you click the app you get "Unable to install "appname.ipa" This app cannot be installed because its integrity could not be verified".
I have done ample searching and read through the JAMF documentation on In-House app deployment and clearly I am missing something :-D. Is it required to have an AD/Certificates in order to deploy in house apps with App Configuration? This is for a hosted JSS. Or do the apps have to be made with an enterprise account?
Any help / guidance is much appreciated.
Reply
7 REPLIES 7
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 06-02-2021 09:46 AM
Did you ever find a solution to this? We have an in-house app that literally just stopped working today. When I try to install it fresh on a device I get this error message. For the devices it was already installed on it's now saying the app "is No Longer Available".
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 05-19-2022 11:28 AM
HIHad you had an opportunity to get any info from developers on the solution?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 05-19-2022 12:08 PM
Honestly I think they just rebuilt the app in XCode and we re-uploaded it. Not sure what triggered the issue in the first place, but I'm starting to think in-house apps need to be updated (at least rebuild and re-uploaded) at least once a year to keep running.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-02-2021 09:46 AM
I am looking for some answers to this as well.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 01-19-2022 11:44 AM
Did anyone ever find a solution here? I'm experiencing this on iOS 15.1 now.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 01-19-2022 02:16 PM
Can't remember exactly how we resolved it (I'm the deployment guy but the issue was fixed by the developers) but I think the developer had to re-sign and republish the app and then I uploaded it as an update. iOS 15 changed something about how in house app signing works.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 05-20-2022 08:31 AM
The issue we encountered was because we were transitioning our ABM license from one instance of JAMF to another and the application licenses were getting hung up on the old JAMF instance where no devices were assigned. JAMF should have pulled everything and deactivated the old instance, which appeared as if it did. This issue was only resolved by removing the ABM account from the old instance of JAMF entirely. After that deployments worked swimmingly.
