i had upload new build(version 6.8.9) with application loader about 20 hours ago, and loader show success, but the new build 6.9.9 not show in app store connect activity list.
when i reupload the version, loader show ERROR ITMS-90189, same build string build exist.
how to fix this suitation? is there some bugs in app store connect?
Hi,
I'm having the same problem. After a week, trying submit a lot of builds, but without success, just disappears, nothing else.
I am continuously getting this error. Could any one guide me? What is the solution to this error no one mentioned in all 10 pages.
Had the same issue. Turns out I was missing NSCameraUsageDescription and NSPhotoLibraryUsageDescription in my plist.
This worked for me, for some reason my info.plist were missing those keys.
Hi, Not sure if this help anyone or not. In my case it is because I updated the version. The old version was 1.0, but I upload a new build with version 1.0.1. It showing that version for a while and then disappeared.
It only working when I change version to 1.1 > archive and Distribute again.
Sorry, above not working, I cannot edit the comment so I reply here.
Please try checking your update in podfile, info.plist,... In my case I use custom pod from a github link and it causing the issue, remove the pod > pod install > archive and the build upload fine again
how you detect the problem with your custom pod?
Same issue. Still.
Also faced the issue now. No problem earlier in the summer.
Same issue, 24.11.2023
I thought I was making some mistake when uploading my app, I see that we have the same problem, it must be some platform problem
Look for an email with this error ( ITMS-90683: Purpose string missing in Info.plist ), this is some permission that your application needs, add it and that's it.
In my case it was this: NSMicrophoneUsageDescription
I added it and everything working again
You can check below the tap of the app version. It doesn't exist write an email to the app review team.
-
—
TradecomNV
-
—
AmoseSuwali
-
—
rdamontz
Add a CommentDid this ever get solved? I see multiple posts of 3 years ago where people say this can take up to 36 hours but never a solution or official answer.
3 Years later still facing the same issue
I am having this issue ( 11 January 2023 ).