yesterday i saw on my iPhone that was an update of one of my apps without nothing updated, so i checked in iTunesConnect and nothing, no updated released.
Is it possibile? Also to my friends is happened at same day.
Thanks a lot!
It has happened again in the past when a bug with bitcode was discovered. When you submit your app to Apple with Bitcode enabled, Apple can (and will) build and optimise your app for each processor architecture. So it is possible that for some reason Apple triggered a rebuild of your app and that is the reason that you saw an update.
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:
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 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'm new to iOS development, and my problem is that the latest iOS update (8.0.2 at the time of writing this) causes my app not to work properly. My app is already for sale in the app store, so any user who has already upgraded to the newest iOS version is downloading a broken app. I have a plan for fixing the bug, but the turnaround time for new releases is quite slow, and I don't want to screw over all the new users while I wait for the updated app to get approved.
What should I do?
I know I can set the "Deployment Target" in Xcode, but this does not seem to prevent users with the newer iOS from still buying it.
Today:
Fix your app as quickly as possible (that turnaround is only about
you)
Submit it to Apple
Request an expedited review request review to Apple, explaining why you need a quick turnaround (critical bug fix is a valid reason). You can't abuse of expedited reviews, so use them carefully.
In the future:
Before Apple releases a newer iOS version, they release developer previews. You need to use these to make sure your app will run smoothly when the newer iOS is released to the public.
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.