Post

Replies

Boosts

Views

Activity

"Unable to Verify App" message started to appear for an already existing app
I have an app being deployed to QA ad hoc. All the builds have always been signed with the same provisioning profile under the same developer account. In the last two weeks, I built two different versions (e.g. 0.0.2 and 0.0.3). So, QA has been working with version 0.0.2 until last Wednesday when 0.0.3 was ready. The new build was signed in exactly the same way as before. However, on a test device with iOS 16.3.1, it did not start, showing the following message: . (Note: Everything was OK with Internet connection there, as QA tried to run the app immediately after downloading it and also tried it dozens of times.) NB1: After the problem appeared, QA checked the previous version 0.0.2, and it still ran fine on the target device. However, the issue persisted when returning to 0.0.3. NB2: The app does not appear in Settings/General/VPN&Device management section, so there is no way to actually verify it NB3: The same IPA file runs on iOS 12 and 14 without any issues all the time. I would greatly appreciate it if somebody could clarify the reasons of such behaviour or at least point out how to avoid it in future.
3
1
826
Sep ’23