Not a great solution for you, but you may be able to learn more information about your installation error by viewing the Mac Console.app, viewing the console for your phone if connected via usb. I am facing installation issues for all enterprise builds I have done since 9/12/23 (the build from 9/11/23 still works), but I don't get any error message popup. Good luck resolving your issue and please post back any solution that you find!

The short answer here is, yes, if provisioning profile or certificate expires, the apps will fail to open or install. It's different from the App Store where once the app is available on the store, that version lives forever. Especially the certificate part of this process creates painful hassles every 3 years for teams that actively use both allowed distribution certificates, since it means that you must either wait for it to expire, or revoke it early in order to free up a spot for a new cert - which obviously is downtime in either case. With provisioning profiles, it's a bit easier since you can get ahead of the game with a new build on a fresh provisioning profile at any time in the annual expiration cycle, and you can also upload fresh provisioning profiles to previous copies of your app in the MDM provider (we have had mixed results with this).

I'm having the same issue, no tester lists are able to load additional pages of testers - standard and edit modes broken.

Can't speak directly to this, but both the large and small companies I have worked at have struggled with the way enterprise certs work since you are only allowed essentially 1 cert at a time (with the 2nd cert allowing for overlap to avoid any downtime). This has caused common scenarios where multiple teams or business units are trying to ship apps to result in either a shared machine that needs to build all apps across the teams, or sharing of private keys. There is now the cloud cert process, but it's very unclear from the docs on how to build apps in this way.

@eskimo can you please share more details regarding cloud signing - the docs are very unclear about how to actually build enterprise apps that use these certs instead of the normal ones - seems like it's a path Apple has added to solve some of the issues, but it's so far unclear to me how to make use of it.

I'm curious on this too - can anyone repost the help link as it seems to have been broken now?

I'm coming here for the same reason - curious what the "managed" cert is and how to actually use it to sign, given that my normal cert is expiring this week. Being an enterprise account, and having 2 separate development teams, I need to find a way to get an update out on MDM before the expiration, but have no way to renew anything. I'm wondering if somehow I can actually use the managed cert. @pyrtsa-sanoma FYI your link seems to be broken now - please repost if possible.

I am curious as to the ad-hoc/enterprise answer here. A newly refreshed (in December) profile of ours has been marked invalid and we are noticing iOS 12 devices in the field start to display inability to download/install/launch with a new version we have released. It is unclear if the invalid mark occurred before or after the signing of the new version, although I would have expected a full-out failure if it was invalid at the time. Strangely, Xcode does not seem to show the invalid state in its little info button/popup that shows the profile expiration and capabilities (this is after a download command on all latest profiles and a restart of xcode).

I see something similar in our application where we have WKWebview on an AWS Chime WebRTC meeting. For devices running 14.3+, they transmit video, but it's blank for themselves. And then when another video comes online, the entire meeting flickers. The original phone also will start to be excluded from meeting events and audio/video transmission over time.

I'm curious about this answer as well - we have a sample of AWS Chime service meeting and it is able to detect devices and broadcast audio/video, but only on iOS 14.3 devices and above - the problem is that the actual WebRTC traffic doesn't seem to be working properly for some reason; other participants joining/leaving, audio/video has a number of issues. SFSafariViewController works without issue as does Safari browser.