We submitted our app update (1.01) to the App Store on Wednesday of last week. The app included a few major bug and authentication fixes. We submitted our working/bug-free app to the App Store via the normal procedure. Sunday night at 8:31PM EST we saw that the status of our app went to "In Review". Then at 9:17PM EST the app was approved and the status changed to "Processing for App Store".
All users who now go into the App Store and download the 1.01 update are seeing the app open the immediately crash at the splash screen. We've tested this on multiple devices and all 1.01 updates crash immediately. We submitted our distribution-ready app in a working state, there were no crashes or bugs on our end.
Knowing that the app was under review for nearly and hour reiterates that the app was in a working/crash-free state upon submission. We've read of a few cases where other apps were submitted, approved and the app would crash upon opening the. We're looking to you for a quick resolution to this App Store issue.
Are there ways to revert to 1.0? Any assistance would be helpful?
There is no way of reverting to previous versions :( You can only remove app from store but as I understand this is not the case. From my own experience I can say that the review team doesn't always find bugs in apps under review and this is how it actually ends with not working app and irritated customers.
You cannot revert. However you can fix the issue and request an expedited review cycle. https://developer.apple.com/appstore/contact/?topic=expedite
Sidenote - do you use Core Data? Maybe a migration failed? This is pretty common if you changed the data model. If the reviewers just installed the new version without upgrading, they wouldn't have seen the crash. Could explain that... I have a hard time believing they would have passed a launch crash that they observed.
Related
I don´t see any problems like crashes or that the DAU number has changed, but App Store Connect shows 3 times more deletions since the release date of iOS 13. Now I don't know if there is any problem in the App or if Apple has made an upgrade of the "App-Offloading" mechanism? So it would be good to have some feedback, if the app deletion numbers have changed for somebody else as well.
Low-memory phones are prompted to delete all apps before the upgrade.
One of my colleagues has a 6S that is chock-full of photos. When she upgraded she was told that all of her apps would stored in the cloud but deleted on the phone, to make room. After the upgrade, she still had all the app icons, but those were really just shortcuts to re-download each app anew.
Apparently this also kills notifications, because without the app on the device there's nothing to execute the notification.
I have that message in App Store Connect:
App deletions data was reported incorrectly for iOS and tvOS as of
August 2019. This data has been removed from the dashboard for
reprocessing and will be re-enabled once reprocessing is done.
See attached screenshot:
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.
We are ready to start the development of an using trigger.io, however some last minute external feedback pretends that trigger.io apps are systematically being rejected by Apple since the launch of their new Reload system (which pushes updated HTML/CSS/JS code without having to re-sublit to Apple for app updates).
The only reply regarding this topic on stackoverflow (Apple App Store ok with Trigger Reload?) was issued by one of the founders of Trigger.io, so I'm really looking for some totally independent feedback on this.
Can anyone provide any real-life feedback on this ? Has anyone ever succesfully submitted an app to the store ?
Trigger.io's page https://trigger.io/examples/ provides very few examples of submitted apps, so it isn't very convincing either...
Any feedback greatly appreciated !
At Hojoki, we're successfully submitting an app built on Trigger.io to the App Store for over a year now. We're actively using Reload (e.g. pushed reloads to all our iOS users three times in April) and never experienced any issues regarding approval and Reload.
There were two times that the app has been rejected (related to meta data stuff..), however this had nothing to do with Reload or Trigger.io at all.
The only Reload-related app store rejection we know of happened on May 9th (six days ago). This was due to Reload files not being marked as exempt from iCloud and iTunes backups.
There are loads of apps using Reload live in the app store, so it's not a general problem - it's just that this particular app was using Reload to distribute >100MB files.
Nevertheless, v1.4.46 of the Trigger.io platform contains a fix which sets the no-backup flag, to be extra safe.
Currently an update to my iPhone application has been in review for over 10 days!!!
In that period of time I've been able to work out a few bugs and even add some small new features to my application. I know that it is possible to reject your binary, but I would rather go a head a publish my application then send apple a better version 1.1.1...
So basically my question would be if I rejected my apps binary and submitted one right after would my app get pushed to the bottom of the review pile or would I keep my spot in line (since I've already been waiting for 10 days)?
No, rejecting a binary and immediately resubmitting a new one will not maintain your place in line: you would be knocked back to the start of the queue. I base this on my own experience, having rejected and resubmitted binaries a few times in the past.
Now, you might be thinking: "OK, what about the expedited review process?"
I can share some experience with that: With my latest app, I was in the same position you were in but I decided to go ahead and release 1.0 and then submit 1.0.1 soon afterwards. When 1.0 was approved and released, Apple chose it for the "New & Noteworthy" section. All of a sudden the app was getting a lot of exposure—and complaints about a bug that I had fixed in 1.0.1. I submitted 1.0.1—and as well as a request for expedited review—which was approved. 1.0.1 was released about 24 hours later.
So, you'll have to weigh the pros and cons for your own app, but I hope this info helps. :)
Yes it would, rejecting and resubmitting the binary will place you at the bottom of the review queue. It's unfortunate, but there is no work around.
If Apple allowed that then many devs would start uploading their beta version while trying to fix those last few bugs.
I had the same issue. I had submitted my app and it was in review. I was asked to change some metadata and resubmit the app. While doing that, I discovered a UI issue and fixed it. I was in a dilemma as to keep the current binary and release a version 1.01 or upload the new version. I did not want to send my first app with an issue so, I went ahead and rejected the binary and uploaded the new one. I immediately contacted Apple developer technical support. They claim that "The review time will not be affected and that our internal systems do have process your build before it can be reviewed (verifying it’s general correctness and resigning your app for the store), which can add some delay. However, that delay is fairly small and is only a minor factor in review time. More to that point, any delay here is much smaller than the delay of a new submission." I hope that is true and hope my app is not stuck in the "waiting for review or in review" limbo :(.
I built a in-app payment for one of my iPhone apps. It worked in sandbox mode.
I submitted my app to the app store and it got accepted. I even submit my in app payment. It got accepted and it's status is 'ready for sale'.
However, when I go get my app in the app store, it still says it's in sandbox?
Is there something in MKStoreKit that you have to transfer environments, or does it take some time for it to change?
I currently pulled it from the store because of it. Please help! Thanks.
Hmmm. Are you using your Test User ID or a real Apple ID?
When this happens, it's usually because you previously used the same device for testing IAP in sandbox mode. To fix, just go into "Settings", then go to "Store", then log out and back in again. That should clear that up, assuming that you are actually using the archived app that you downloaded from iTunes, rather than your dev copy.
Re-released my app today so I could get it and see if the in app payment would work. Surprisingly, it worked and it wasn't in sandbox mode! So I guess it just takes time for apple's servers to make the change.
If anyone else had this problem, don't fret like I did! Just wait and be patient. Hold for developer release and wait around 24 hours and you should be good!
Here's the real solution (edit):
Set your availability date to the future so it will be removed from the app store
Set your availability date to the day it is so it will re appear