We are using Unibill in Unity to make In-App purchases for iOS
this have been working for more than one month , we were testing and everything works fine on iOS (we have android as well and it's working)
the items we added were on waiting for app submission , because we haven't submitted any new version of the app to itunes connect
after we submitted a new version for review it was accepted and the in app items status changed to accepted as well .
at this point we stopped being able to purchase the items from either sandbox or testflight , StoreKit is returning no items at all
I'am 99% sure the error is not related to the code because we haven't changed anything for more than a month and we were able to purchase perfectly
the only 2 changes are:
* the app was accepted , the consumable items status changed to accepted as well
* not sure if this is related but we renewed our developer account in the member center 2 days ago , not sure if this is related to the problem in anyway
any ideas about this problem?? can you really not test the purchase after it's accepted anymore?
thanks in advance
I have no Idea what solved the problem , it seems that it was something from apple's side
it wasn't working for 3 days, and it started working the fourth day without changing anything in the project!
I did add a new item for purchase in the itunesconnect , could it be the reason? it might have refreshed something? I don't know
Related
I have 3 IAP already approved in AppStore Connect.
I want to edit one, to add a limited into period.
When I tap on the IAP, the "Subscription Prices" section is indefinitely buffering.
I tried Safari, Chrome, incognito, Windows, Safari on iPhone, everything.
I also checked my Agreements and both Free/Paid apps are Active and the default currency is USD.
I submitted a ticket to Apple, but from experience, they don't really help.
Help?
I don't know how much this helps, but I think there's a problem server-side for Apple.
I'm experiencing the same problem and have equally not been able to get any support from Apple around this.
My reasoning here is that 2/3 days ago I couldn't log into my portal as it kept declaring that there was no AppleID attached to that email address. Eventually, as I knew there was, I just left it and hoped it would work itself out. I came back the next day and was able to log into AppStore Connect fine with no issues.
I've seen quite a few comments that Apple have kind of f'ed up their migration over to AppStore Connect, and this fits with the weird login problems I faced. I can definitely replicate your issue and have also reported it to Apple, so I assume that this is one of those things which will magically fix itself in a day or two. (Particularly given user:elbib says it's working for them)
It worked fine for me as of this writing. I’ve used my iPad 8th gen.
Issue got solved after raising it to apple via a support ticket.
It took them 2 weeks.
For who that may face this issue.
The title, prices and details that is used to show the product coming from the In-App Purchase have to come from the store. If it comes null is because you didn't agreed or assigned the accept from Apple Developer Program and paid apps contract on the App Store Connect. So, do that and try again.
Hope it helps others.
Having issues for the past days trying to make the IAP work on TestFlight for my 1st game app.
IAP works fine in Unity Editor (fake store) and also on Google Play (internal test track).
I don't receive any product prices from the apple store and the buy buttons have no effect (no callbacks on ProcessPurchase or OnPurchaseFailed since I show popup windows for both scenarios).
Below is the status of my app and IAP :
From other similar threads everything should be ok and working as TestFlight doesn't require the IAPs to be submitted nor it requires for sandbox users to be manually created.
Any hints on what to further test or how could I check logs/warnings/errors are much appreciated, thanks.
Tools used : Unity 2019.3.0 (IAP 2.0.6) and XCode 11.3.1
Update 1: OnInitializeFailed() is called with NoProductsAvailable err
The reason why the initialization failed with NoProductsAvailable was because I didn't have an active agreement for paid apps, although it is testflight and there are no real money involved, you still need to have this setup.
Here is how it should look like :
Once this was solved the IAPs worked fine.
I posted this question to Apple Development forum, but got no answer. Maybe I can get help here.
I'm trying to make in-app purchase work in my app. This is first app I developed and published for iOS, and I struggle to make in-app purchasing work. Here is timeline.
January 21 - I successfully published app to App Store on Sunday, January 21. The app is "Tennis Umpire App", written in Xamarin. I used component https://github.com/jamesmontemagno/InAppBillingPlugin so support purchasing. There is Android version with the same code where in-app purchasing works. This is just port to iOS.
January 22 - Discovered that In-App purchase doesn't work. No popup for the user, in the logs I see just "General Error". Tried on different devices, different accounts (on my friends phones). Then I realized that my contract for paid apps wasn't finished in iTunes connect, so I finished the contract. Tried again and it didn't help.
Created new sandbox user to try in development version of the app, and it worked!
January 23 - I found another post that it may take 24-48 hours to get things through, so I waited. Checked it from time to time - didn't work. In monitoring tools I can see that other people tried with same error.
January 25 - at this point 48 hours passed since I completed the contract. But it still doesn't work.
Any ideas in how to troubleshoot it further are appreciated.
Looks what helped me is resetting "Clear for sale
flag. I cleared check box, saved, and then marked it as "Clear for sale" and save again.
I released a new version of an app yesterday which added in app purchases. We did testing with a test account in sandboxed mode and everything worked correctly, however once we download the app from the app store the SKProductsRequestDelegate method:
(void)productsRequest:(SKProductsRequest *)request didReceiveResponse:(SKProductsResponse *)response
returns invalid product id's instead of valid ones. I'm baffled because I've had these types of problems before but only when trying to get them to work in debug mode, never after the app has been released from the app store. I've double checked everything on the list here http://troybrant.net/blog/2010/01/invalid-product-ids/ and none of those are the problem.
Here's another thread which is exactly my problem but no solution here: iOS In App Purchase - "Invalid Product ID" in release, NOT development version
I also encounter this problem and after 22 hours the problem be fixed automated. So I think this is the app store's problem that apple need some time to add your iap ID in their server.
It turns out in app purchases are magic. At around 8 pm we noticed that things started working normally. We had previously filed a request for help from Apple but never received a response so I'm not sure if that's what kicked off the fix or if it was just one of those things we needed to wait on.
I am also suffering with this issue and I went to Apple Developer Forum to get the solution. The problem is might be with Review team's device or environment.
Here is the link of full thread: https://devforums.apple.com/thread/233371
Here is the history of my app.
In v1.0 I didn't have IAP.
In v2.0 I had IAP code, and it worked while I was developing. When v2.0 was released, I checked and run a non-testing device (an iPhone under my itunesconnect user name, but does not have provision file installed, so I take it as a non-relevant device) and I got error message, which of course was set up by myself. The error is for situation that the app could not connect to Apple or could not find IAP for the app. The error shows up quickly right after clicking buy IAP. This is as expected since no product ID is available. It doesn't need wait payment queue at all.
Then I checked itunesconnect and found the IAP probably not linked to the app, so I updated to v2.1 and added the IAP to my app in itunesconnect (no real code change, at least no IAP-related code changed), and IAP works fine finally in development stage in my testing iPad. Now v2.1 came out, but I still have the same problem as v2.0, that means IAP encounters error, most likely no IAP product ID found. At the time I'm typing, v2.1 has been released for 2 hours, and I still have quick error --- the product ID problem, most likely.
[edit]
BTW, there was a glitch between v2.0 and v2.1. When I noticed the IAP was not linked to my app, I did something too quick so that I cannot remember exactly. Basically the IAP was hung over there, I could modify it or submit it. After talking to Apple, I was told I need reject my binary of v2.1 and resubmit v2.1 along with the IAP. I don't know if this is related, but anyway I can buy IAP in development stage with my sandbox testing iPad.
[edit]
Any idea? Thanks.
BTW, the app is set to English default, but with Chinese/Spanish localization.
[edit]
One more thing, don't know if it's related. All v1.0, v2.0, and v2.1 versions are deployed to iOS 6 or later. When I was developing v2.1, I was trying to back to iOS 5 (via adopting so deprecated methods or constants). My app could run on iOS 5, but IAP wouldn't work iOS 5. Since IAP doesn't work, there's no point for me to go compatible with iOS 5, so I removed all deprecated methods and constants and went back to original v2.0 version and resubmitted with linked IAP to become v2.1.
For those who cares, here is my app. You're welcome to try. long press first page would get you to options page where you can try buy IAP --- no worry, there is supposed to be a confirmation dialog where you can cancel, even if my IAP works.
https://itunes.apple.com/us/app/icalc24!/id566916783?mt=8
[edit]
One more edit:
OH yeah, it works now. I don't which step of the following make it work:
1, I delete my app and restart my iPhone again (and again, yes) and re-download
2, it's 4 hours now after v2.1 is approved.