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?
Related
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 have a bunch of apps I've made already installed on my iPad Air 1 & 2 and all of them work fine. However, I recently upgraded to iOS 9.1 and now the app crashes when my splash screen appears.
I've tried to reset my device both by doing a factory reset and by trying to reinstall 8.4 by using an ipsw file. However, apple have stopped signing anything for iOS 8 meaning I am unable to reset my version of ios to an earlier version.
In my searches, I've not been able to find any fixes for the apps I already have installed on my ipad. With my experience, when I upgrade my iOS, everything already installed should work just as they did before. However, all of my own applications now crash after being opened for 2 seconds.
Has anyone else experienced this (I've read 9.1 has broken a lot of applications) but more importantly, has anyone found a solution?
The comment below says I've not provided enough information, but I'm unsure how I can add more as my issue is not related to any of my code. I only upgraded a couple of days ago. I was happily using and testing my applications on the device just fine last week. After the upgrade, none of them are working anymore.
We have a couple test iPhones in the office. The one I use for development hasn't been updated in the last couple months, the one used by our QA team has been recently updated, however. I'm also still using Xcode version 6.3, and my compilations run fine in the simulator or the dev iPhone.
However, now that the QA iPhone has been updated, my Xcode refuses to build for it, claiming that the verison of iOS on it (8.4) is not supported. This is a common occurrence and I've just been dealing with it. While I'm waiting for my Xcode to finish updating (which is taking its sweet time), I'm realizing that this limitation is arbitrary (or at least it seems that way). I've already compiled my app for the QA phone earlier this month, that version obviously wasn't built for 8.4, yet it runs fine on it. Likewise, other apps on the phone don't need to be redownloaded after each update, nor does the app store require recompilation for each iOS update. Clearly the newer version of iOS can support the app built by older version of Xcode, then why does Xcode refuse to deploy to a device that has been updated? Is there a checkbox I'm missing somewhere in build settings that says "deploy even if you don't recognize the iOS version"?
I can build and debug on an iOS 9 iPhone with Xcode 6.4
Also you need to understand (but I'm not an expert either) that when there's an OS update, to really support debugging Xcode needs to be familiar with that OS' debugging symbols (which may change at every software update). This is why, when you plug in an older version of iOS (or any version it is encountering for the first time) Xcode will take a few seconds to load and process the device's symbols. That's my understanding of it.
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.
Ive uploaded an update for my App two days ago, it should be 9.0 MG, but after submitting it it shows 1.11 MG, so I've called Apple Developer Support, they told me to do the following:
Reject the current build and upload a new one - Didn't work
Upload using Xcode 5.1 instead of Xcode 6 GM seed - Didn't work
Upload more than one build, and switch between them - Didn't work
So nothing worked with Apple, so they told that if I'm sure that I've uploaded the correct build to not worry, it might be a bug from the system.
Now ive uploaded an update for another app, and faced the same issue, the app size is 2.1 instead of 16.5, so I've decided to use TestFlight Beta Testing, its requires iOS 8, so I've updated my iPhone to iOS 8 beta, and once I've sent the link to the mobile, I've found that the app size is 2.1 !!, And every time i try to install the app, it says EXPIRED, so i didn't see the app working on the phone from the AppStore new build testing.
At the end, I've decided search on Google again for more results, "Ive tried to search about this issue 3-4 days ago but no results came", and found that some people got Invalid Binary after submitting the app "1-3 days", you can check these links: Link 1, Link 2.
Nothing from what i found gave an accurate answer to this case.
Anyone faced same issue?? what should i do??
My first app was approved by Apple and everything seems to be ok, the app size is now changed to the correct one "9.0" MB, and the app is working as expected on the device.
So its seems that the size issue is related to Apple, they have a bug on the itunesconnect.
So don't worry about the size issue anymore.