Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iPhone [MERGED] iOS 13 - app updates stuck on "Waiting"
- Thread starter mzanker
- Start date
- Sort by reaction score
For now for me the simplest way to update is by offloading the app and re-install using the iphone storage section of general settings. Bit of a hazzle but this works.
I assume there was a ruling change pushed recently on Apple server’s side; probably when user’s Apple ID is used for TestFlight sandbox account, even if that happened in the (far) past. Maybe a conflicting certificate used to sign the ipa’s (handshake issue installed app - Apple ID/sandbox- simulated purchase vs the AppStore live app). If that’s the case, then I‘m afraid that Apple has a tough challenge to solve. I’m 100% sure that they already were aware of this issue as they monitor via analytics what’s going on 24/7. Understandable as well to keep the storm silent until they completely know what the issue/impact/solution is, also taking into account that there are some small letters which we all agree on when testing via TestFlight ... unfortunately 😔
Nope, it won’t indeed. Looking into our linked Apple ID’s with sandbox, and removing any changes made by it probably will. Hopefully our installed apps are signs with the same certificate used for live Apple store.
[automerge]1574256366[/automerge]
I might be wrong, but looking at the with/without sandbox overview below I assume that they somehow have mixed the ApplelD with both live and sandboxed environments and/or related rulings.
Last edited:
Once this gets to the correct person in Apple I don’t see this taking too long to fix as this was working fine up until recently with no client side change to cause it. Also purchasing new app, subscriptions and deleting and re-downloading apps works. As such the App Store knows that the apps were purchased with that account.
One thing I’ve noticed is that on my iOS 12 device if I try to update an app when not signed into the App Store it will prompt me to log in. On iOS 13, it won’t ask me and will just silently fail the same way it does when I’m logged in. When I mentioned that on Twitter someone responded that he could not even attempt to update apps if not logged into the App Store.
What happens if you sign out of the App Store and attempt to update Apps?
The reason that you are able to first delete and then install the app, versus update, has probably to do with handshake error caused during recent updates during this mixup, or changes from Apple server side (AppleID and/or ipa). When updating an app via AppStore there is an handshake going on to determine purchases validation and certificate validation. I hope that you’re right.. let’s hope that our installed apps are not signed with a different certificate then the ones that non-testflight users have.
regarding non logged in attempt to update; the installed apps are linked to your Apple ID. You most probably will not be able to update them with another Apple ID, other then yours.
I got a feeling this is either going to take a long time or never going to get fixed since is not affecting everyone.
Any iOS devs that can check something?
It seems that the TestFlight installed apps are using the same bundle ID as the ones in the AppStore. This means it is in fact the same app and no beta/release candidate. So installing an app via TestFlight and then via AppStore it will result in replacing the same app.
Is this supposed to work that way??
It seems that the TestFlight installed apps are using the same bundle ID as the ones in the AppStore. This means it is in fact the same app and no beta/release candidate. So installing an app via TestFlight and then via AppStore it will result in replacing the same app.
Is this supposed to work that way??
stranger still, it is our other sources of information that have not reported the problem yet, to get the attention of apple developers
if you do like me, report the situation to apple support, the more you do it, the faster the situation will be resolved
if you do like me, report the situation to apple support, the more you do it, the faster the situation will be resolved
I'm having the same issue with the "Update" loop for app updates on all of my devices - iPhone 11 Pro Max, iPad Pro 10.5, iPad Mini 4, MacBook Pro 15, and Apple TV 4K.
I'm a beta tester for the Apollo Reddit client and we all had to do an in-app purchase so that the Pro and Ultra tier features of the app were accessible in the Test Flight version and not just in the live production version. At the time, Apollo's developer had said this was just a simulated purchase that wouldn't actually charge us etc, so I thought nothing of doing it and had no idea what I was doing was actually creating a separate environment for my AppleID like this.
I realized after reading the information here that the problem likely began the other day (same day as the iOS 13.2.3 release) when I installed the live production version of Apollo on my iPad Mini and restored the purchases. (while still using the Test Flight version on my iPhone and the other iPad). Not sure if that helps at all as far as understanding the exact trigger, but it could possibly explain why some people had the problem start at different times.
Super frustrating bug though - I'm in the medical field and I have required hospital apps for the electronic medical record and stuff that won't update now.
EDIT - I've made a post on the Apollo subreddit asking the author to help us get this to Apple's attention - it's a very popular app and I'm assuming he may have some contacts there who can expedite/escalate it.
Also - in my case I previously had the actual paid subscriptions (Apollo Pro and Ultra) on the production version of the app before being invited to the beta and doing those "purchases" again in the Test Flight version.
I'm a beta tester for the Apollo Reddit client and we all had to do an in-app purchase so that the Pro and Ultra tier features of the app were accessible in the Test Flight version and not just in the live production version. At the time, Apollo's developer had said this was just a simulated purchase that wouldn't actually charge us etc, so I thought nothing of doing it and had no idea what I was doing was actually creating a separate environment for my AppleID like this.
I realized after reading the information here that the problem likely began the other day (same day as the iOS 13.2.3 release) when I installed the live production version of Apollo on my iPad Mini and restored the purchases. (while still using the Test Flight version on my iPhone and the other iPad). Not sure if that helps at all as far as understanding the exact trigger, but it could possibly explain why some people had the problem start at different times.
Super frustrating bug though - I'm in the medical field and I have required hospital apps for the electronic medical record and stuff that won't update now.
EDIT - I've made a post on the Apollo subreddit asking the author to help us get this to Apple's attention - it's a very popular app and I'm assuming he may have some contacts there who can expedite/escalate it.
Also - in my case I previously had the actual paid subscriptions (Apollo Pro and Ultra) on the production version of the app before being invited to the beta and doing those "purchases" again in the Test Flight version.
Last edited:
If this is affecting some or all users who've purchased IAPs/subscriptions via TestFlight, it will disproportionately affect power users (i.e. people who enroll in TestFlight betas) and developers. Believe me, even if those are a small proportion of the overall user base, they have an outsize capacity to make themselves heard.
Along with contacting Apple Support, I've done some signal-boosting across tech communities I'm a member of, and I've mentioned it to people like Michael Tsai, who is absolutely read by people at Apple.
Along with contacting Apple Support, I've done some signal-boosting across tech communities I'm a member of, and I've mentioned it to people like Michael Tsai, who is absolutely read by people at Apple.
I agree with you partially. I think that since it's only affecting a minority of users, Apple is going to put basically no effort into fixing it unless a tech news outlet or influencer publicizes it. But based off of the times this has happened in the past, I'm expecting the issue to "fix" itself again and Apple to just stop investigating it. Then we wait for it to happen to another handful of unfortunate souls 4-6 months from now. An endless cycle.
1. Yes
2. Subscription (but free for testing purposes obviously)
3. Installed release version/did not subscribe
I too am having the same issue. For me it started on the afternoon of November 17th. I got some updates to work in the morning. I spent over an hour on the phone with a senior tech from Apple. No resolution. He said he will need to talk to the engineers and call me back today. Hopefully, I will have some answers.
One thing I noticed... There is 1 app I installed on Sunday and subsequently deleted because I did not like it. When I go to the store and click on "purchased" the app shows up with a cloud icon but says it was updated yesterday. I know for a fact that it had been installed and deleted 2 days ago, not yesterday. So I wonder if the problem has something to do with the time and date. I checked the system date and time and regional settings and all are set to automatic. I switched to manual, but that did not change anything.
I too think it is something to do with my Apple ID or something of the sort because I have the same issue with my older iPhone 6. I have not updated apps in a while on it so I have over 100 apps to update, but I cannot update any of them.
I remember this problem happening to me a few times in the past. The problem always seemed to resolve itself, usually about a week or so after it occurred. I am of course hoping that it goes away on its own, but who knows.
I too have TestFlight installed, but have not installed or updated any of the apps there in over 10 days. So I cannot say if updating an app from there would work or not.
Hopefully, I will have some news this afternoon when I am supposed to get a call back from the senior tech after he talked to the engineers.
One thing I noticed... There is 1 app I installed on Sunday and subsequently deleted because I did not like it. When I go to the store and click on "purchased" the app shows up with a cloud icon but says it was updated yesterday. I know for a fact that it had been installed and deleted 2 days ago, not yesterday. So I wonder if the problem has something to do with the time and date. I checked the system date and time and regional settings and all are set to automatic. I switched to manual, but that did not change anything.
I too think it is something to do with my Apple ID or something of the sort because I have the same issue with my older iPhone 6. I have not updated apps in a while on it so I have over 100 apps to update, but I cannot update any of them.
I remember this problem happening to me a few times in the past. The problem always seemed to resolve itself, usually about a week or so after it occurred. I am of course hoping that it goes away on its own, but who knows.
I too have TestFlight installed, but have not installed or updated any of the apps there in over 10 days. So I cannot say if updating an app from there would work or not.
Hopefully, I will have some news this afternoon when I am supposed to get a call back from the senior tech after he talked to the engineers.
Yes, that’s what I would suspect, but I can’t figure out why I’m not being asked to sign in under iOS 13 if I try to update apps when not logged in.
My understanding on how App Updates work, is that the request to update includes the purchase Apple ID embedded in the app (which is added when initially downloading the app). The server then checks whether that app was actually purchased under the logged in Apple ID and if not prompts to sign in, otherwise it just updates.
The fact that I have apps installed on an old iPhone 5s that I’m pretty sure predate my attempt at making an IAP in a TestFlight app or at the very least pre-date the IAP of a subscription in a TestFlight app, would seem to indicate that the app’s ID specific data should be fine.
Likewise I had the same app on both my iPad and iPhone and my iPhone updated it because it did the update on Nov 13, prior to me having a problem. The iPad failed on Nov 14.
As such I’m pretty sure the installed apps are properly signed and it’s the server that is mistakenly returning a “not allowed” response.
The problem seems to be starting at different times for people. I had it start Nov 14 (6 days ago). Some people had it start Monday. I found one person who claims it started 2 weeks ago. As such it is definitely tied to the account, but Apple must have changed something server side sometime recently which is causing this.
All we need to do is somehow get the information to that person or team at Apple. Unfortunately that’s easier said than done when tier 1 support is oblivious and tier 2 (senior advisor) keeps indicating that it’s not a known problem. Tier 2 can’t do much other than grab logs and submit them. Those go to engineering. Actually cause of this problem was likely a caused by something being miscoded, which would be even higher still up the chain.
The only way to get someone inside Apple that high up to notice the problem is if it is a widespread problem, which to be honest this isn’t. I’m talking a problem affecting hundreds of thousands or millions of customers, not a few hundred.
I’m supposed to here back from engineering again tomorrow. The problem is that iOS/macOS senior advisors can only file engineering tickets with the iOS/macOS engineers. The problem is on the App Store server side, which is what the engineers came back on my first escalation. This needs to be escalated up to the App Store backend/server engineering team and so far tier 1 and tier 2 iTunes Media support has refused to do that as they are saying it’s not a billing issue, which is the only thing they can escalate.
Basically until Apple acknowledges there is a problem affecting multiple users, it will never get fixed.
Created an account to chime in on this issue. Reading through all the replies on this thread. I’ve been in contact with Apple Support since last week. I own a macbook and an iphone. Both are unable to update
As for testflight, I use it a lot. I’m a registered developer. And recently “bought” the ultra version of Apollo as part of their beta testing program. One week after, I wasn’t able to update my apps anymore.
I’m also unable to update apps on my macbook. I’ve contacted Apple Support and my case is currently handled by two senior Advisors (one for iPhone and another for macbook).
even though it seems like the same issue to me, they INSIST that it should be handled separately. I tried pointing them to this forum but they weren’t that interested. Today, they called me again to request for more log files and log files from my MAC. I have them all the log files they required.
I also mentioned to them that it might be testflight causing the issue. The advisor assured me that he will note this to the engineering team.
will be hearing from them again in the next few days. I wasn’t very happy as they seem to all think that the problem came from my phone or MAC and not their end. The MAC advisor even suggested that I delete all third party apps and try again (it didn’t work of course).
this issue took me a Long time talking over the phone with Apple support and till now no resolution. I’ve spent almost 3hours on the phone with them. I know I shouldn’t think this way but I almost told them to drop the case as I didn’t want to waste more time with them, solving THEIR ISSUE.
good luck to all of us
As for testflight, I use it a lot. I’m a registered developer. And recently “bought” the ultra version of Apollo as part of their beta testing program. One week after, I wasn’t able to update my apps anymore.
I’m also unable to update apps on my macbook. I’ve contacted Apple Support and my case is currently handled by two senior Advisors (one for iPhone and another for macbook).
even though it seems like the same issue to me, they INSIST that it should be handled separately. I tried pointing them to this forum but they weren’t that interested. Today, they called me again to request for more log files and log files from my MAC. I have them all the log files they required.
I also mentioned to them that it might be testflight causing the issue. The advisor assured me that he will note this to the engineering team.
will be hearing from them again in the next few days. I wasn’t very happy as they seem to all think that the problem came from my phone or MAC and not their end. The MAC advisor even suggested that I delete all third party apps and try again (it didn’t work of course).
this issue took me a Long time talking over the phone with Apple support and till now no resolution. I’ve spent almost 3hours on the phone with them. I know I shouldn’t think this way but I almost told them to drop the case as I didn’t want to waste more time with them, solving THEIR ISSUE.
good luck to all of us
I have an account associated with testflight, but I haven't used it for months. I ask, how can it be a testflight problem, if last week I updated it without problems, and from yesterday to today I already stopped doing it
That's what we're trying to figure out - there's a trigger somehow. Did you recently install the live/release version of any apps you have Test Flight versions for, or restore in-app purchases that have been made in both the live and Test Flight version of the app? That's my hunch based on how it all started for me. I did the IAP/subscription in Test Flight Apollo at least a month ago, then on the day this started installed the live/release version on a different device and restored the purchase (which I do actually legitimately own prior to being a tester).