I have a Flutter developed App that I want to upload for App Store Review.
The App has been successfully uploaded through Xcode as you can see here— https://prntscr.com/26m7w94
Sadly, the Build doesn’t appear in my App Connect Build section as you can see here— https://prnt.sc/26no755
When I try to re-upload, it let’s me know that the Build is already uploaded to App Store Connect as you can see here— https://prnt.sc/26no84v
I have written to Apple and I don’t understand the answers they are giving me. They are just talking off-point.
Now I have waited for 8 days for this build to appear, but this uploaded build is not appearing.
Without this Build appearing, I cannot Submit to App Store Review.
Everything in the App Store Connect Form has been completely filled. Only Build remains to be added as you can see here— https://prntscr.com/26no94s
I can’t figure out what to do next, and this is 8(eight) wasted days gone by, with me not knowing what next to do.
Has anyone here faced this kind of problem before? How did you solve it?
Regards
Check in the TestFlight section. There might be a yellow triangle next to your build. You may need to answer some additional questions such as encryption usage etc. Just click on the triangle to answer and your build should be available afterwards.
Sometimes the answer to this issue is that there is actually a problem with App Store Connect (like right now).
You can check for issues on the Apple Developer System Status page.
For me changing the version from X.X.X to X.X.X+1 (2.2.2 -> 2.2.3) fixed the issue.
Sometimes it happens and I have also faced this problem .I successfully uploaded my bundle from Xcode but not found in connect.
I waited 30 minutes and refreshed .Then my bundle came in App Store connect.
Solution 1 : wait for some time & Refresh ,
Solution 2 : Create another Bundle and push to connect using Transporter (You can download transporter from appStore)
If the build doesn't show up on App Store Connect. You may want to check your email (the one you used as your Apple Id when uploading the build).
In my case Apple sent me an automatic email telling me that my build had some issues. Xcode didn't complain about anything and neither App Store Connect.
UPDATE: This might have boiled down to timing. After changing the version number to 1.0.0, that build showed up immediately. Half an hour later, the 0.0.1 build appeared out of the blue as well.
If you've set your version number to 0.0.1+X because you thought that makes sense while the app is still under development, change that back to 1.0.0+X. The upload will succeed, but app store connect won't list the build without a leading "1." in the version number.
Make sure no webviews are used in your app. It will not show builds in App Store Connect and neither XCode nor Apple will say that anything is wrong.
Related
When I upload a build from xcode I'm able to see the build is processing on itunesconnect.apple.com, the image below is the screen I initially see:
build processing
But after I refresh the page the build disappears and doesn't reappear. It's been over an hour and I still don't see the build anymore. I've tried rearchiving but I get the same result--I see it initially but then it disappears. This is the "empty" screen I see after my build has disappeared:
empty build
Should I keep on waiting, contact support, or is this normal?
Most probably you are missing some key in the plist.
Please check your email for the developer account.
App Store review may send you a email for the above issue.
Make sure you have the key
" NSPhotoLibraryUsageDescription " also added in your plist
I've had issues in the past when I tab to different applications during the build upload process. In those cases XCode seems to mess up and builds can take an exceptionally long time to process (3+ hours in my case). In my case I just incremented the build number and generated a new version making sure to keep Xcode in focus during the upload.
Usually the build might take around 3 hours to get processed and appear in App store depending on the size of your app. But so far I have not seen a scenario where even processing of build is not shown. I would suggest you to logout and login and then check for the same.
I got a email from apple.
I am not using camera and photo in my app, but still i got this email from apple developer team to add in my info.plist file. I don't know why to add it, but it worked.
Below you can see that testing for external testers are turned off:
same for internal testing:
but when I transfer app, one of the criterias are not met:
Why?
I had the exact same issue, resolved by removing all Tester and Build from the TestFlight as discussed above also (!important) remove everything fields at the App Information - Test Information.
For me it was localised test descriptions. Make sure you check that drop down list on the right and clear out info for all languages.
I just solved the transfer issue, you just need to expire your build from tester by following the steps below. and then app will available for transfer..
open your app and click on testflight then click on the icon of your app as shown in below screenshot.
The click on expire build.
Now you can transfer your app :)
I've search for a long time and to me this worked:
Clean all builds inside: My Apps --> App Name --> TestFlight
Go to: Itunes Connect --> Users and Roles --> Tab "TestFlight Beta Testers" and click in the name from another user that isn't you.
Save.
Go back to the App in Itunes Connect: "Itunes Connect --> App Name --> Transfer App" and attempt to transfer again by clicking in "Transfer App".
To me this works. Hope help someone.
i had the same issue i deleted (mark expired) all the versions of app testing version in App TestFlight section and done the trick for me ;) attach is the screen shot of activity.
Another possible reason:
When you delete all test information from TestFlight, make sure you delete it for every language.
In the testinformation page, select every localised language and check if the form is empty.
I struggled with this for an entire day, I tried everything and finally found another workaround:
1) Expire all the builds
2) Delete all testers
3) Clear all the informations in the Testflight tab
4) Delete all langages except the main one
And finally the step which fixed the Testflight criteria for us
5) Create a new app version (no need to submit or even edit it)
now you check transfer.
Good Luck.
I know it's an old question, but it still bugs people to this day.
So the solution here, after you have removed all the testers, and expired all builds, go to TestFlight > Test Information and clear all the fields.
Also make sure you delete any localization you might have there. Give it 5 minutes, after which transfering will be possible.
Not sure if this is going to help,
Check Users and Roles > TestFlight Beta Testers
Do you have a tester who is testing the app that you want to transfer?
I have the exact same issue and I'm currently getting from Apple "our engineering team is still working diligently to have this resolved for you". I have been supplied with a workaround:
Enable TestFlight by adding a tester to a build
Then deactivate the build, by turning off TestFlight beta testing
Attempt to transfer again
unfortunately, I still haven't been able to resolve the issue.
We found that in addition to the other answers here, logging out and logging back in to iTunesConnect allowed us to continue after it was saying TestFlight was still enabled.
I was facing the same issue, going inside tranferring app console multiple times automatically fixed the issue and started showing all criteria as met.
Do the same step as #Imran Iqbal answer, if your app is Sign-in Required, uncheck Sign-in Required also, like:
then, you can transfer app.
I've exactly the same problem and could not solve it. The good news: After contacting Apple, they have confirmed a bug and they're working on a solutions. Apple confirmed also, that many developers ran into this.
Got that workaround from the support (that did not work for me):
1. Enable TestFlight by adding a tester to a build
2. Then deactivate the build, by turning off TestFlight beta testing
3. Attempt to transfer again
It looks like this is being done on purpose for new apps.
Now, A newly created app CANNOT be transferred into an account, until 14 - 21 days have passed.
An expiration period.
First, You must remove all build and user from TestFlight of that app. After its looks like below.
If you still not match last criteria than Sign Out and login again.
Creating new app version did it for me! Thanks!
The tricky solution is to enable testing again, add some tester in. The visit the TestFlight and under test flight users, you will see old active test flight users. Simple delete them.
Maybe I have a stupid question, but after the update to Xcode 7, I sent a new version of my app to the App Store (via standard: Archives - Organizer - Upload to App Store). But now it is my build in iTunes Connect in tab Prerelease with status Processing (btw more than 12 hours), and I do not know why. Why is my build in Prereleasse tab? Previously, I uploaded new build the same way and I could have it for a few minutes to submit for review. Thx for help.
Update: After more than 48 hours, I can finally submit my new build for review! ;-)
The issue seems to be related specifically to Xcode 7. Some people have mentioned these work arounds to get it to go:
1) Use Application Loader and not Xcode to submit to iTunes.
2) Re-submit with new Xcode 7.1 beta.
3) Re-submit with old Xcode 6.4.
Your milage may vary.
Edit: Problem seems to be solved now, it appears to have been related to that exploited Xcode issue in China which caused significant iTunes Connect delays.
It's not the feature of Xcode, instead it's actually a feature of iTunes connect by itself.
All your uploaded archives go directly to "Prerelease" tab and lets you the privilege to distribute those to some specific users for beta testing, through TestFlight(optional), before you actually set it for production.
This process lets you debug your app performance and lets you actually maintain a build log, without actually releasing the app for public. When you are all set, you pick the best from Prerelease builds and release that to actual production environment, for public.
More documentation from Apple is available here
And by the way, I think your Processing issue should be automatically resolved if you give it some time (possibly 24 hours or so) or you might need to remove your app and upload that once more. You might know, Apple is too much busy to maintain it's App Store's security, right now ;)!!!
I uploaded my application to App Store yesterday. I was waiting for a long time as I couldn't find my binary file in Pre-Release option. I thought it may take some time. But on the sudden the UI of iTunes Connect has been changed today and there is no Build still in the app store. Still the status is Prepare for Submission. What am I supposed to do. Kindly suggest me guys.
In my case I had to resubmit my binary file to app store again. May be due to the change in UI. I was uploading last night. I guess after that only the UI might have been changed from Apple.
Tap on Activity tab check that your build.
I want to test in app purchases therefore I uploaded build with xcode. I can see the build under "Prerelase" but not in "Versions". How long does it take to show up in "Versions"? It's been 30 minutes
The build is not visible until the "Processing" step is in progress in the "Prerelease" tab.
It should depends on the size of your app.
For a 10Mb app of mine, it took about 5 min.
Check your inbox for an email from iTunes Store:
Subject: iTunes Connect: Your app [...] has one or more issues
Dear developer,
We have discovered one or more issues with your recent delivery for
[your app]. To process your delivery, the
following issues must be corrected:
This app attempts to access privacy-sensitive data without a usage
description. The app's Info.plist must contain an
NSPhotoLibraryUsageDescription key with a string value explaining to
the user how the app uses this data.
[...]
Once the required corrections have been made, you can then redeliver
the corrected binary.
Regards,
The App Store team
Xcode 8 told me the upload was successful, but the build did not appear in iTunes Connect until I fixed the issues indicated in the email and resubmitted.
May be helpful:
While pushing build to ITunes, i minimize organzier window, so in background everything went smoothly and message got display "Build pushed successfully".
But build do not got display in itunes store and sometime build get display in "Processing" step but do not get to "Versions".
I repeated step 1 and 2 but same result.
Then i pushed build with Organizer window (in Foreground) not Minimised and everything worked. (It takes some time according to size as #cdescours pointed)
This experiment was conducted on dated 30, Oct, 2014 throughout day & also same issue was discovered later too. Hence we can conclude iTunes have the issue when the build is pushed in background.
Check the Activity tab in iTunes Connect after you upload the app and wait until it processes:
To update #cdescours' answer, uploaded builds can now be seen in the "Activity" tab in "Processing" state.
Check your email. You should have issue or missing report on you email. I got email that I miss NSCameraUsageDescription key in Info.plist
When you upload your build from Application loader or directly from your xcode to App Store and it is not showing even on multiple uploads with different build version then
Open your .plist file and check whether there is any key string starting with "Privacy - ........."
If that key string value is empty, then Add some string.
example, for me i was using camera, photo Library, Microphone and Location.
For my project i added the string as follows
a. This app requires access to the Camera.
b. This app requires access to the Photo Library.
c. This app requires access to Microphone of your device.
d. This app requires access to your Location.
e. This app requires access to the Bluetooth.
Now upload the build it will get Accepted.
Note: This permission string is mandatory from iOS 10.
In case you are adding build with deployment target >9, add these keys to info.plist in case you are using camera and photos: Privacy - Camera Usage Description and Privacy - Photo Library Usage Description with a valid description.
I had the same issue when I submitted with blank string for these keys.
Sometimes you may need to check your email. There will be no errors while uploading. But apple may have send an email with the errors in your build. In my case I got an email with the following error mentioned in it.
This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSPhotoLibraryUsageDescription key with a string value explaining to the user how the app uses this data.
I have added the NSPhotoLibraryUsageDescription key, but the description string was empty.
You can see all of your activities (recently uploaded builds here). It will also provide current status of your build.
Building on #sreedeep-kesav's answer (not enough rep to comment), Privacy - Camera Usage Description and Privacy - Photo Library Usage Description can be set by opening your Info.plist file in Xcode and selecting the plus button next to Information Property List:
Wow this was super annoying! Honestly I don't know what the problem was because I've uploaded many apps to the appstore via Xcode over the past few years but past couple days I tried like 8 different build uploads over span of 12 hours but NONE of them would show up in iTunesConnect as Processing or anywhere else. I eventually tried Application Loader even though I've NEVER had to use that before. The first try timed out "Fetching Apple Connect token" or something. I CMD+Q and tried Application Loader again and the 2nd time the upload finished ... and now my build shows up in iTunesConnect as processing. OMG that was annoying, confusing and a huge waste of time (typical Apple Dev experience I guess).
Anyhow ... thought I would share my results.
I have faced the same issue, once I upload build is not showing in AppStore Connect even I did not get any issue mail from apple. So I just wait for a day and that build begins visible on AppStore Connect after a day. It is a weird issue apple team have to look into it.
Happy coding. :)
Check your all privacy access policy option in Info.plist file.
Check the status of the new build on the "Activity" tab. Once the "Processing" label disappears from the build you should be able to use it.
Check your schema that you have selected release not debug.
I came across the same issues, i switched from Xcode6.0 to Xcode6.1 and my builds started appearing in the list.
I want to share my expereince,
I uploaded my build by application uploader and xcode and after 10 hours i couldn't see any build on the itunes connect.
Finally I contacted apple and they explained that a build validation can take 24 hours maximum.
After 24 hours, if the build is not visible on the related page, they advise to upload a newer version.
And if after the second 24 hours if there is still not any build, you can call apple developper program assistance.
Here is the page where you can find phone numbers :
https://developer.apple.com/contact/phone/
Publishing the first version of your application can takes a few days but a newer version takes much less time.
Check all the key and values in info.plist file.
if any key is missing then it will cause this issue.
AppIcon and other thing written in info.plist file must be prefect then u will not able to get this issue.
This worked for me
If build are missing from Itunes 'Activity' tab. Then check your info.plist keys. If all keys are there, then check all keys description. if their length is short then increase your keys description length.
Just wanted to share my experience as well. My Build had crossed Processing Step(it was a mere 984kB app) but did not show up in "Versions" tab for more than 30 minutes. I also double checked my email but had not received anything from Apple. However, under versions tab I had 3 builds listed excluding the latest one. What worked for me was that I just clicked on the least recent one(click on the Build Number) and then clicked on Expire Build and voila buy recent Build was immediately available under the current Version.
I have not found any Apple Document which explains this anomaly.
Hope it Helps! Cheers
Well, in my case I uploaded a build with updated version. like 1.1.0 Build 1.1.0, then I reverted back to 1.0.0 build 1.0.5 and the same build was visible under the 1.0.0 header dropdown.
Hope it helps someone.
This was My Mistake:
I had a minor update in a Push Notification content part and I did not even touch my code.
But I thought I might have to re-upload it in order to reflect that change in the latest version.
And I did.
Tried to upload 3 Builds One by One.
But Not a single build has shown in the Test Flight Version.(Shocked)
Later I realized my mistake that just by updating APNS content part without even touching my code, I was trying to upload a new build and was expecting to reflect it in the Test Flight. (So stupid of me)
InFeb 2020, Apple has changed the TestFlight upload policy. When you do the same old steps to upload your app to TestFlight, even though you provided the export compliance information and the iOS Buildpage shows your build is ready to test, it just doesn’t show up on the TestFlight app. That’s very weird right?
After googling and browsing the StackOverflow threads, it turns out you need to add an extra row in info.plist to make it work.
App Uses Non-Exempt Encryption = NO
info.plist
This way it’ll magically work.
And you don’t even need to provide the export compliance information every-time you upload a new build too!
I has the same issue. Issue was resolved for me by trying to distribute the archive again through Xcode. At the final stage it showed the error that an app with the same version number had already been uploaded (my initial upload an hour ago). As soon as that error message showed I got the email that the original build was available in App Store connect. There must be a workflow issue in the upload process.