I have a problem with iOS application, that I uploaded to Itunes for publishing in the store. Apple began the typical process of approval, but errors appeared.
The application worked in my test enviroment. No problems. When the Apple revision process began they told me that the application doesn't start.
When the application start the error is:
There is a new version of AppName
to download. Press OK button to
download it in the AppStore
But:
1) The application is the only version. Is a new app, never uploaded before to Apple Store.
2) When i push the OK, the app closes. So, no way to run the app even with that.
I search through forums and internet with no luck. I don't know where to search about this problem.
For more confusion, after the test from Apple, in my test enviroment i can reproduce the error. I don't know if i did anything wrong in the middle or something change on app version check from Apple.
I contact Apple in the previous days to give more info about the problem, but the only that they say is "the application does not work"
Can you give me an advice?... what info you need? (logs, etc)
Thanks to point me in the right direction.
Related
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.
All,
We have an app in Appstore which is functional, Now we have build the app for new Version with complete new architecture, Design. Every thing is changed. Now we have given a update for out existing app in the Appstore. App went live and we updated the current app in Phone, We got the new version as expected.
But the problem starts here. In the Updated app we are not able to login and some other services are not working.
But if we download as new app (I mean deleting the old app and download it again). Every thing is working as expected, like login, and all the services.
We are not understanding what went wrong. What may the issue, Can any one help us.
I'm trying to upload my application to connect itunes but I could not get. Valid from XCODE application without any problem, it also raises and spends the whole process normally. But over 1-2 minutes since connect receive an error, error that appears in iTunes do not understand.
ITC.apps.preReleaseBuild.errors.processingFailed
This message appears next to the binary version of iTunes Connect a red alert icon.
I'm working with this application IONIC, it had already risen above versions without any problem to store.
I cleaned the project, it has made new applications in my environment itunes but nothing works for me. I'm not receiving any specific error. As I said earlier binary is validated from xcode.
This problem is mainly due to a plugin in particular, it was the PushNotification plug, take it away and I could upload my application without any problem. Now, there was never notice from Apple, nor stand that there was a problem with this. It was a matter of luck remove this plugin and it work.
I have a serious issue which I cannot seem to solve.
Recently I have made an update to an IOS app, and when testing in XCODE as both Ad-Hoc, Debug, and installing via the .IPA on a device the issue cannot be replicated. However when I download the app from the App Store, it crashes.
Does anyone know how this could happen, and any potential solutions? I am getting lots of complaints from users, and not sure what to do?
Could part of the binary upload have got corrupted?
Probably you always compiled your app in debug mode. But when sent to App Store you made a release compile. click the arrow in the run button select scheme and chose "release mode" and run your app it will probably crash.
check if you used NSParameterAssert as they are not called in release mode
I cannot say why your live App Store application is crashing and the debug version is not. Two possible solutions:
Crash reports:
To find out why your application crashed, you might want to check if there are any crash reports available on iTunes Connect. Log in on iTunes Connect and click on your application. Scroll down to Crash Reports. You will find out more about why your application is crashing here.
More information about crash reports here at Apple's own iOS Developer Library.
Prerelease your app with TestFlight: For in the future: test your application by uploading it on iTunes Connect and testing it with TestFlight first before submitting the application to the iTunes Store. This will save you a lot of (review) time if you find a error.
I realize this is an old thread but I had the same issue with my App that I released. Meaning it worked fine in testing, but when I released it it would crash. The culprit ended up being the fact that I am using In App Purchases. I have two items that can be "bought" but I had only enabled one of them. In testing it was able to read both of them, but with the release version, it was only pulling the one that was enabled down, creating the crash. The fix was simply enabling the disabled item. I didn't even have to redistribute the app, though I had to wait for it to "percolate" through... Anyway this may help someone in the future.
Check if your app is looking for too many IAPs.
I just had this problem and my problem was I had deleted an IAP from the App Store, but didn't remove it from the app code.
For some reason it only crashed when downloaded; I used a promo code to do this before launching my app.
Thanks to Tornado for the inspiration to try this variation.
I've submitted and updated my app successfully several times. Now when I'm uploading my app via XCode Organizer (not application Loader) I receive the following warning (3 times):
"Creating a new Signiant Transfer Engine because the previous transfer had to be canceled. This session is at risk of running out of available system resources."
First I didn't think much about it, but today the App got rejected by the App Store reviewer because it crashes on launch on the iPad air they use to test on.
Any ideas how this can be solved?
I found this discussion here: Application Loader, new weird warning about Signiant Transfer Engine which suggests to change the preferences in Application loader. But because I have not uploaded my App via application loader from the beginning I cannot use application loader to update it (at least I couldn't figure out how), so it doesn't help me.
What else could be going wrong? Any ideas welcome!
update: the app validates without errors and warnings. when uploading it it takes much longer than usual before I get the warning mentioned above. I have tested the app on multiple devices. Also the app is actually not targeting iPads, it's mainly made for iPhone/iPodtouch.
It works fine on all. The link above suggests that not all files are uploaded correctly when the error message occurs. So that could be the problem. But the question is how to change it...
I'm not sure, but I don't think the warning has anything to do with the crash or your app being rejected.
You could file a TSI with Apple, but I would try to find the crashing bug first. https://developer.apple.com/support/technical/submit/