nicklockwood
commented
9 years ago It's hard to prove a negative, but I don't see how iVersion can be to blame here. All it does is direct you to the App Store - after that the actual download process is entirely outside my control, and should be no different to just opening the store yourself.
The only possibility I can think of is that the URL is wrong, but if that were the case it seems like I'd be seeing more reports of this.
I started using iVersion in the 2.0 version of our app.
We wrote 3.x from the ground up for iOS7, and ever since, the actual upgrade via iVersion never seems to complete successfully.
To be clear, iVersion announces the new version correctly, but when you go to download the new version, it gets a good amount of the way there, and then quits.
I've seen this on two iPhone 5's, always on iOS7.
It's hard to test this in the real world and I don't believe there's a delegate method I can hook into to determine if the upgrade was successful or not, so I'm not sure how widespread this is. I just know that with the past 6 or so releases, I've never been able to complete the upgrade.
I'm running the latest version via Cocoapods, 1.10.6.
Any ideas?