I just uploaded a new build to the App Store Connect. The build has finished "Processing" under the Activity tab, but it's still on "Processing" on the TestFlight tab.
The most bizarre thing is that not only the just uploaded Build is "Processing" but ALL OF THEM, builds that were uploaded and processed long ago.
Activity Tab
TestFlight Tab
This is the first time I experienced this, does anyone knows what is going on?
As it turns out, it was only a visual bug on the AppStore Connect. After a long time processing everything went back to normal.
Related
I have an expo build that I am running in order to submit it to the app store. It says that it is still building but when i go into the logs it shows that it is complete. I do not know why it got stuck on this step and how to fix it. What should I do.
it usually shows that i can download the build in order to submit it to app store but it just shows queued even though it completed the build.
This was a temporary issue with the website a couple hours ago. Specifically build job statuses weren't being synced with the website, causing completed builds to remain in a "Queued" state. This issue has been resolved and builds now show their correct statuses. Successfully completed builds will now show a "Finished" state and be downloadable.
have you had the following error in TestFlight? Basically, we have test versions in TestFlight that when we launch them to external testers work. But it has happened to us 2 times that after a week or two, that version stops working.
Basically, the app won't open, won't even show the splash, and crashes.
Last week the app stopped working for all testers, we updated to a new version and it started working fine for them again. But yesterday the version that already works previously began to fail them again.
Today, I just generated a new version with no code changes and it works. But I'm afraid it will eventually start to fail.
When I say that it fails, it is that the app icon is touched, it tries to open, but it does not open and it crashes.
For example, now the new version works fine for me, but if I go to TestFlight and install a previous version that worked fine on my phone 2 days ago, it no longer works for me.
Any idea what could be going on, guys?
Maybe some certificate expires or I don't know, any idea is welcome.
I'm using expo managed workflow and eas build to generate the iOS app.
Something that happens with the versions that start to fail is that when they are installed, the first time it does not fail. But if I completely close the app and reopen it again, it doesn't open anymore, and the crash occurs.
We're using Sentry, but we don't have any issues. But I have this crash in TestFlight errors.
Thank you in advance for all your comments or ideas.
So iv spent the last couple of weeks building my first app in Android Studio and all has gone well. Successfully launched on device through whole testing / Dev phase.
I got to a point where I was happy and proceeded to build a signed APK using Build->Generate Signed APK.
This was successful and now I have a published APK.
I have since noticed a spelling mistake (Rookie error!).
I have corrected the spelling but now when I click the "play" button to launch a test version it appears to be building the app on outputs a big stack trace ending with the following...
BUILD SUCCESSFUL
Total time: 1 mins 21.581 secs 13:15:46: External task execution
finished 'build'.
But then that is it, no offer to view on device like during the initial build stage. (no device popup)
What am I missing to get this to publish onto a test device again?
Any help or pointers are appreciated, I'm new to this Gradle thing, I have a feeling its something to do with that but I don't know where to start and Google doesn't seem to find anything useful to me :/
Although I can upload successfully new versions of my app to iTunes Connect, I can't see them nor the previous ones under the "Prerelease" section in the app's page. Instead, I get a message saying "Upload your builds with Xcode 5.1.1 or later, or with Application Loader 3.0 or later". In the "Versions" tab, under "Builds", when I press the "+" button, I get an error saying my request couldn't be processed. Am I missing some needed configuration?
It looks like this is an issue with iTunes Connect, not something you did. There are a bunch of tweets right now of others experiencing the same issue.
What you'll see right now if you look at the itunesconnect hastag on Twitter:
Our list of pre releases in #itunesconnect disappeared for no
reason... /cc #APPLEOFFIClAL 0 retweets 0 favorites 38m ago
Weird…all of my app builds have disappeared from iTunes Connect
itunesconnect 1h ago
itunesconnect: (slow / misbehavin') for everyone or just me (dot tumblr dot com) 2hours ago
itunesconnect - no earlier uploaded binaries are seen in any application. Seems like a bug. Fix it Apple, I have to deliver to customers.
Unfortunately, the official system status says everything is green. It's not clear how you're supposed to report an issue.
Indeed it was an apple bug. After two hours, the prerelease builds appeared again.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
I am trying to submit a new version of my existing app in itunes connect but I am having difficulties. So I uploaded my build like usual and upload done. I went into pre-release and saw the status processing. This was 12 hours ago, now though it has changed from processing to inactive. I ignored that and went and chose the build anyways and clicked on "Submit for Review"
I get an error saying You must submit your builds using Xcode 5.1.1 or later, or Application Loader 2.9.1 or later. After you’ve submitted a build, select it in the Builds section below.
But I did submit a build using Xcode 6 seed version. I also tried to upload the build again but I get an error saying that a buid already exists. I figured I will try to delete the build, from the pre-release tab and try to upload a new build but I cant find a way to do this.
Makes me think it has something to do with the inactive status of the build. Is anybody else having this issue?
Okay So I was able to submit my app for review. I guess you cannot wait for too long after you submit your build. I have no proof of this but I think if your build is inactive, you cannot use that build to submit an app. Here is what I did to solve my issue
In xcode I changed the build version, not the app version,
Archive and validate
Submit
While the build was still "Processing", I went back to my apps new version page on iTunes Connect
Choose the new build and submit for review.
Dont let the build become inactive.
Good luck
I was having the same issue. I followed the guy above's advice. Here's exactly what I did to get it to work:
In iTunes Connect, remove the current build.
In Xcode, change the build (not version) number to something else. I just picked "3".
In Xcode, go to Product -> Archive
Note: If this is greyed out, ensure that you select "iOS Device" instead of a different simulator or connected hardware for testing
In the Organizer - Archives window, click Validate, then click Distribute
In the Organizer - Archives window, delete your previously submitted archive
Go back to iTunes Connect, refresh, and select the new build with the updated version number