I recently (October 2nd, 2014) submitted a new version of our app for IOS8. Previously it launched and ran on IOS8, but had some bugs, which I fixed before resubmission:
Upgraded Stripe's Pod, because I was using an older version which began to experience an SSL error with IOS8.
Updated my CLLocationManager code to use kCLAuthorizationStatusAuthorizedWhenInUse (because IOS8 isn't backwards compatible for requesting the kCLAuthorizationStatusAuthorized status).
Added a new, non-critical Swift view controller, to test using Swift in the same project/interoperability.
The app was granted expedited review, but when the new version finally appeared in the app store I was in for a nasty surprise.
The app crashes on launch when on IOS8 devices. Whether an upgrade, or fresh install (delete app + data & re-download), but it doesn't do this on IO7.
I've reached out to Apple for help resolving this, because the binary I sent them worked fine on my IO8 device, and my other IOS8 testers through Testflight—as well as on IOS7. The submitted binary should launch fine, but it won't.
Some research:
This post citing a similar problem was created today at 1:34am GTM, before being deleted. Thanks Google Cache.
Back in June of 2012 Marco Arment discovered that Apple was messing with his submitted binaries, causing them to "crash immediately". Not super useful, but it's interesting that this is potentially a problem.
Does anyone know what else could be causing this, or even how to go about debugging the issue? I'm perplexed because of how it runs perfectly over Testflight, etc.
This was a bug in the code signing process on the App Store, and has been fixed. The affected apps have had their code signatures fixed and are being pushed out as updates.
Related
I am trying to make my first application to submit to the App Store using Xcode, but when I was going through validation, it said that I had the wrong SDK version. How can I fix this?
I tried archiving my app 19 more times, but it didn't work.
I tried looking all over the web, but it didn't help.
I also tried updating
the Xcode app, but it said that it was temporarily unavailable.
When I would try to validate it sent me an error message saying that I had the wrong SDK version.
I thought that I did everything correct, but when I was at the last bit of validating it, it said:
"SDK Version Issue. This app was built with the iOS 11.4 SDK. All iOS apps submitted to the App Store must be built with the iOS 11 SDK or later, included in Xcode 9 or later. Further, starting March 2019, all iOS apps submitted to the App Store must be built with the iOS 12.1 SDK or later, included in Xcode 10.1 or later.
Click here to see the image of the error message.
I think what I need to do is just put my app in a certain file and update my Xcode, and validate it again because on the error message it said that I had the wrong version of Xcode. When I said that I got another error message on the App Store
Thanks to everyone who helped me in the comments above - #manishsharma93 -. :D :)
I have seen a few similar questions but nothing to help me resolve my issue.
My app works when built in debug mode. It works via testflight on devices running iOS 11+. We support iOS 9 and above, so when i get the app via testflight on an app running iOS 9 the app instantly crashes. I find it unusual that this would run fine on a newer version of the OS but fail on the older version.
I understand that this is a pretty broad question. I presumed it would be an issue with certificates but if that was the case i would expect to see the same issue on each OS version. I have compiled the app for release and ran it on a device to replicate the issue which it does. In the device logs i can see the error.
Attempt to add an app with insufficient id, info
Again i understand i haven't been able to give much information on this error, but i am hoping someone has been in a similar situation and can give me some pointers.
I have an app which works perfectly on the simulators. This app also worked perfectly on an iPhone* for a couple of months. After a few weeks of this app not being opened, the app crashes when I attempt to open it. It looks like its about to open but it quits.
If I double tap the Home button to display my cached apps I can see it there amongst the other cached apps and it looks fine, displaying on-screen elements and images(which are saved and retrieved from the filesystem) correctly. If I tap it, it again quits before running.
I was hoping to release this app asap as it is finished. I've searched the net for solutions but have not found any. I don't know what particular information may be needed to figure out the problem but please ask and I'll respond with it. I am relatively new to ios development.
*iPhone 5s running latest ios9 update
The latest version of Xcode is 7.3. You need to update your Xcode to the latest version to be able to upload to the latest version of iOS.
EDIT: I forgot to mention this earlier. The latest version of Xcode requires El Capitan (OS X 10.11).
EDIT 2: OP has now revealed that a provisioning profile is being used. These only last about a month. After they expire, the app is no longer trusted and will show the described behavior. This can only be solved by re-signing the code, which requires either a new provisioning profile or a Developer ID. In any case, after the code is re-signed, it has to be reinstalled, and installing onto the latest iOS requires the latest Xcode.
Sources coming soon.
OK, so I seem to be having some trouble finding the site where I found this information in the first place...
However, from the App Store:
Xcode 7.3.1 includes [...] SDKs for iOS 9.3 [...].
I'm updating my existing app to include support for Apple Watch (at this stage just handling of notifications), however when I archive my app and try to submit it to the app store for review I continually get this error.
I've tried playing around with the build settings and I've also tried googling the error, however I can't figure out what the issue is.
Does anyone have any ideas or has anyone come across this issue too?
You cannot submit an app for review using a beta version of Xcode.
Following today's Apple Watch official release, Apple updated Xcode to version 6.2 which in theory should allow submitting apps that contain Watch extensions. However I just tried to submit my app that includes support for Watch using the new Xcode, and got the same error. I hope this will be fixed sometime soon on the ItunesConnect site.
I develop a single iOS app and noticed something last night that I'd never seen before. I had an adhoc development version of the app on my phone and wanted to show someone the version posted on the AppStore. I deleted my local version, went to the AppStore, which correctly showed 1.1.0, but then when I downloaded it an older version 1.0.9.9 was installed. I knew it right away because major UI revamps were missing.
I know there is often a lag right after releasing the app (I always use Developer Hold), but this was nearly 2 weeks after I had released the new version that suddenly the old version was downloaded. Has anyone seen this behavior and if so, is there any real recourse?