I have launched my app on AppStore which includes In-App purchase feature. In-App was working fine in iOS5,iOS6 and iOS7 in sandbox mode. But after App Store approval, In-App is not working in iOS7 devices sometimes. Sometimes In-App is not working first time, When second time when user click on buys it works. What is the issue? Its working fine in iOS5 and iOS6 devices. Can anyone explains and share any solution.
this is also happening for past few days on all iOS's. Most of the time it gives same message on device as well. Though I have I know the code I have does not any issue and when I submitted to app and it is approved, it works perfectly. It looks like some issue with sandbox env.
Related
I recently finished the first version of an iOS application. I have several in-app purchases within it. When testing these, I always used a physical iPhone. Apple just approved the build for release and the app is now in "Pending Developer Release." As one last sanity check, I generated a promo code for myself on app store connect and downloaded the app onto my phone through the app store. I quickly noticed that the SKProductsRequestDelegate method is never fired and the list of in-app purchases is never downloaded from Apple's IAP server. This is similar behavior to when the app is run within a simulator: the IAP data is never loaded.
I am unfamiliar with how the "Pending Developer Release" stage impacts in-app purchases. Will they work as expected when I release the app to the public? Is there some change I need to make and resubmit?
Any help would be greatly appreciated.
As far as I know, it should work seamlessly except for the charging (You won't be charged if your app is downloaded from outside AppStore). So trying to gather logs may help you in this case.
Turns out this was an issue on Apple's end. I contacted support and something on their end had been messed up when they approved the in-app purchases.
I recently started using RevenueCat for all of my InApp purchases; today my app was approved in the App Store so, I went ahead and downloaded it to try the new version directly from the App Store and I noticed that the In-App purchases are not loading. What is funny is that if I connect my phone to my computer and compile the app directly from Xcode it does show the In-App purchases.
So my question is, is there any setting in RevenueCat that we need to turn on when the app goes into production?
If such of setting does not exist, what would be a good way to troubleshoot the issue to determine where the problem is, if it's RevenueCat, the App Store or my code?
FYI - When I install the app directly from Xcode I can make purchases with a send-box account and everything functions as it should.
There aren't any RevenueCat settings to update when your app goes live. This sounds like a propagation issues with the App Store if these are new products - sometimes they can take ~24hrs to be available in production to all users after being approved.
Unfortunately, doing nothing and waiting is probably the answer here. In the future if you can not show new products to users until >24hrs after they're approved it should prevent this from happening again.
My purchases won't reset.
I have done everything that can be found online. I've made multiple (sandbox and testflight) accounts, uninstalled apps, logged in and out tenths of times. Whatever I do, whenever I return into an app in which I have made purchases previously, those items are still purchased. It seems like the device is remembered for the purchases, instead of the user.
Before, if I re-installed an application with Testflight, everything would be reset. This way I could test if in-app purchases kept working. Now, I have to ask my developer to create a weird workaround to reset purchases.
Does anybody have any clue what can be done about this, or has experienced the same problem? I'm working with an iPad Air 2, the problem has started since updating to iOS 10.0...
I've recently released an iPad app which has a non-consumable "pro upgrade"-style In-App-Purchase.
It works for most users, and it worked when testing. However, I do get daily reports of the IAP crapping out for some customers of the app.
It is the worst kind of bug:
For most people, it seems to work fine.
For some people, it works after a reboot of the device or logging out from the App Store.
For
some other people, nothing seems to help and they can't make the
purchase.
And I do not have any remote logging implemented...
This seems to happen across various locales / different iPad models / OS versions.
For those which can't make the purchase, usually an error pops up which says that their Apple ID password is incorrect, after confirming the purchase.
The purchase button in the app only appears after the IAP product was received from Apple's server successfully.
I am not sure how to track down what's going on there. I was initially thinking it's on Apple's side, but the number of people reporting it tells me it must be something with my app.
Any best practices on how to debug this?
thanks!
I have created an iOS sample app implementing the In-App Purchase. The functionality is to display the retina images if the user purchases the HD Subscription. Here, I am getting some issue as follow:
I launch the app and purchase the HD Subscription
It asks for signing in, I sign in using the test account created for testing
Purchase successful
View updated to retina images with all the parameters set inside the code
Now, I go to settings and sign out from the iTunes and App Store
At this point i am getting the issue. The issue is that I get the alert saying "Sign-In Required","Tap continue and sign in to check for downloads. [Environment: Sandbox]". Every time I cancel, I immediately get the alert back and not able to proceed with the app.
Kindly suggest what can be the issue or where can i get the detailed description about the issue and it's solution.
Thanks in advance.
Don't worry, its a issue in iOS 7/8. I also have faced this irritating illogical issue but this alert will not appear in live app. My app is in appstore now and earning well.
The reason behind this is, conflict between live app installed in your device with sandbox mode apps. To get rid of the issue you need to reset your device then run your app. Issue will not appear again until you again install apps from app store.
Here you can read more about this:
Tap continue and sign in to check for downloads. [Sandbox]