I'm testing my in app purchase code for an update to my app. The in app purchase works great when I do an install from xcode to my phone. The issue arises when I have the currently released version installed on my phone then I install the dev version over the top of the release version. When I install in this way my product ID comes back as invalid even though I've tested it many times and it works as long as I didn't have the release version installed previous to installing the dev version.
We did alter our Bundle ID in this update but everything has worked except when we install in the way I described above.
Has anybody encountered this behavior before?
Also the currently released version does not have in app purchases.
This happens all the time.
If you install your development version over the App Store version - new In App Purchases IDs are returned as invalid.
This will work perfectly when you upload the new version to the App Store.
Related
I already have an app on app store with version 1.0.0.
Now I submitted the new version of app 2.0.0. This new version is also approved by apple.
It has been more than 5 days since my app is approved and in state 'Ready for sale'.
Now when I download the app from app store on my iphone device it still downloads the previous version (1.0.0) and asks me to update to latest version (2.0.0).
Why app store is not downloading the latest version (2.0.0) of app directly on my device?
My device previously had the app with version 1.0.0 installed from app store but I deleted it and then installed the fresh app from app store.
When I download the same app on my friend's iphone it downloads the latest version (2.0.0). This device never had any version of the app installed.
I had the same problem and have now realised that it is related to iCloud. If you have previously downloaded your app on any device then when you download it on a new device, it will download the same version as you previously downloaded. You then get the option to update to the latest version.
Confused me to start with!
Your iPhone could be outdated / not meeting your defined requirements of the application itself. For example, if you have an iPhone 3G running IOS 6, you can not run an app that only accepts iOS7. Take a look in your xCode and inspect the properties of your application.
I'm testing a Trigger.IO app built with Forge v1.4 on an iPod running iOS 6. I've been installing the .ipa through a distribution provision profile.
Occasionally, after installing an updated version, the app would launch but not run correctly. I traced this behaviour to the window.forge being absent, presumably due to a bad initialization. I would then make sure to kill the app process before installing updates and my recollection is that this seemed to make the problem go away.
Now, I've added the Facebook and Splash modules and my app now consistently won't go past the splash screen after I install an upgraded version unless I forcibly uninstall the old version first. Presumably, it dies before creating the webview. Any idea why I would need to uninstall my app first before upgrading? Is this a known behaviour?
I want to make sure that my users don't experience this when upgrading.
My app runs happily without Forge, and doesn't have any particular dependencies on localStorage data. I don't have a Mac and have been installing via iTunes in Windows, so I don't think I can access logging information.
You should have a look at this post:
How application get update from apple store?
The quick answer is when you update an app, you install the new bundle but you keep the user data stored previously such as a local DB. If you changed the local DB in the new app (or anything else) your app can crash when updated but is fine when downloaded from scratch.
I am trying to simulate an upgrade from version 2.0 to 2.1. I have version 2.0 hosted in testflight, so I did install it in my device. Then I tried running the app from xcode. However what happened is that the app did not get overlapped, instead it created two apps with the same name. How can I make it such that when I run the app from xcode it overlays the old version?
I've made sure that the bundle identifier is the same.
Well the info you can get while updating can be found # this link here.
when user updates an app, Documents folder is stored as is, including
NSUserDefaults (but, sometimes user download app via iTunes and
replace the whole application, crying 'OMG! update killed all my
levels progress!'); Application bundle is erased and replaced by new
one (anyway, it is readonly for user); Re-deployment of new build
version will be enough;
You can't access the appstore inside the simulator because: # link here
It's a simulator not an emulator. Even if there was an App Store in
the Simulator, none of the apps in the store would work since they are
compiled for ARM CPUs while the Simulator runs x86 code.
Another stack overflow # link here states:
Build and install your old version, generate some data, and then
install the new version on top of it.
For testing before submitting to the Appstore I generally download
from the AppStore again the old version, and then install with Xcode
the newer version - for your next update... ;-)
And another stack overflow (that I lost the link for) states:
No, the simulator runs i386 binaries and iPhone appstore apps are ARM
binaries apps.
iOS apps are compiled to machine code, Android apps are run in a
Virtual Machine using byte code and are translated to machine code at
the time they are run.
So no, I don't believe you can run it in the simulator, how ever you can have older projects saved on the iPhone and test both out. And the apple documentation is # this link here.
Read this: https://developer.apple.com/library/ios/technotes/tn2285/_index.html
You cannot simulate update in XCode (neither in simulator or connected device). You have to create IPA file and simulate update process via iTunes.
We have an app in the store right now that was shipped with a wildcard app ID.
The update that is now pending approval was created with an explicit app ID, to enable push notifications.
We've noticed the following issue during ad hoc testing of the update: if we delete the app-store version from our iPhones, and then install the ad-hoc update, everything is fine. If, however, we leave the app-store version running in the background, and install the ad-hoc update over it, the updated version installs but fails to start up. We suspect that this has to do with the ID change.
If this problem is specific to ad hoc installs, then it is not a worry for us, but we are concerned that existing users will encounter this problem when doing the real upgrade from the app store.
Has anyone seen installation issues after upgrading from a wildcard-ID app to an explicit-ID version?
As the the Question asks,
I currently sport xcode 3.2.3 with iOS 4.0.1 but I want to test on my iPhone which is stuck on 4.0.2
Thus I cannot do so until the SDK for 4.0.2 is accessible from xcode.
Where can I download a patch update from 4.0.1 to 4.0.2 because the iPhone members page seems to only link me to the package including xcode 3.2.3 with iOS4.0.2 SDK
I don't want to download the whole thing because it's > 2.5 gigs and my New Zealand internet Connection is shizenhouzen.
I can't restore to a previous version, because for some reason I only have a previous back up of the iPhone on my now defunct windows PC.
I'm afraid you have to download the entire SDK - Apple do not provide 'patches' (4.0.1 to 4.02, for example) AFAIK, and I'd be nervous about downloading anything that claims it is a patch.
It's a common grumble, twitter is a fun place when apple push these .1 SDK updates out :)
You do have to download the whole thing to upgrade. It really sucks. :-(
I wish I could remember to download the SDK before upgrading my devices.
You can still build adhoc releases of your app and install them using itunes if you're in a real bind - it's just the debugger, console viewing and automatic installation of builds that won't work at all.