Using Web https to install app, the app is in waiting... state on the device

If you plug the device in to your Mac and view the console output in Xcode while installing the app from your web server, what errors do you see? (In Xcode, Window > Devices, choose device on left column, look at the bottom part of the right column. You may need to click the upward pointing triangle in the bottom left corner of the right hand column to show the console output.)

I'm having the same issue. Just started with all my apps this week. Thanks for the tip on the console output. It seems that SpringBoard cannot successfully kill the running app for installation of the new version.

Killing com.mydomain.myapp for app installation

Kill failed. Error: No such process (3)

Only if I manually close the app via the Home button will the installation (update) complete. Any ideas?

I have not seen this problem. I just tested on an iOS 9.2.1 device and an iOS 9.3 beta 2 device, and it worked even if I did not force-close the app. I'm in the process of installing the updated versions of Xcode right now, so I can't test this, but does it make a difference if the app was last launched from Xcode versus launched by tapping on the icon?

I can't reproduce the problem. Even if I launch the app and leave it running from Xcode, installing from the server succeeds (it causes Xcode to exit the app). Not sure what would cause the problem.

Thanks guywithmazda for the insight. It appears that some of our bundle ids are somehow corrupt on our devices. If I create a new bundle id the update process works as expected on the same devices. I've deleted the app and reinstalled, but the device must be hanging onto something cached or otherwise but related to the bundle id (even after the app is deleted). When the app with the same bundle id is reinstalled the problem returns. Unfortunately, changing the bundle id is not an option since this is an already deployed app. I've tried restaring the device, but to no avail. Seems odd that SpringBoard can't kill a currently running app. Thanks for the testing and support.

Just a follow up. By using a new bundle id the runtime update process works fine on iOS 9 devices, but still no luck for iOS 8.4 users. They still gets the install alert, taps Install, but app never closes. This is on multiple devices. Adding an exit(0) after the openURL line fixes the issue, but that doesn't help the apps that are already deployed. Thanks again for the confirmation. Hope to eventually figure out what changed, and why now. Been deploying this way for 3 years.

I'm curious what you mean by "changing the bundle id". If you use a different budle id, doesn't it install as a new app instead of replacing the old one?

That's correct. Merely as a test I created a new App ID and installed the same app as a new app. Then triggered an update scenario to see if openURL would successfully close the app upon install (update) like it's supposed to... it did. Under the original App ID it does not. Very strange.

OK, that makes sense. I was thinking you meant you were changing the bundle id and it was successfully closing and updating your original app, and I wasn't sure how that was possible 🙂.