Post not yet marked as solved
That's very clear, thank you.
Post not yet marked as solved
Hello,
Thanks a lot for this answer. I'm using the Application Lifecycle. This answers clearly how to fix this. However, I would like to clarify a point to make sure I understand properly:
The key window just returns the window that receives keyboard events,
which may or may not be your app's main window depending on the state of
the app.
Could you point to states where the main window isn't the key window on iOS (I only have a single window defined by myself in my app).
Thanks!
Bruno
Post not yet marked as solved
Hi @Cameron2019,
Have you been able to solve this issue? It's still present in Xcode 12 Beta 3.
Thanks!
Sorry for bumping up this old thread: Do you know what is the impact of the Settings > [Apple ID] > iCloud > Keychain [On/Off] entry on this?
Post not yet marked as solved
Same issue here, but we are unable to reproduce it on the local machine. Could it have something to do with having multiple versions of Xcode installed (which is the case on CircleCI)?
Post not yet marked as solved
> >what can we use out of the receipt to determine if we should or not attempt to refresh the receipt?> if your latest receipt (expired_date) indicates the subscription has expired then refresh the receipt once and accept the response.I don't this is is correct because you can have a response as follow:- expiration date is in the past (a couple days ago)- expiration_intent is not present- autorenew_status is 1- is_billing_retry_period is 1In this case, you don't want to accept the response but you want to refresh again.
Post not yet marked as solved
Thanks for the details, Rich! So if I understand correctly, we should remove any error display for the purchases, and we should act on users telling us "I tap on 'Buy in-app purchase' but nothing is happening!".I think that ideally either:- We should have a way to distinguish real errors from "cancellations" or "redirect outside of the app"- StoreKit should take care of displaying all error messages (such as "Unable to connect to App Store").What do you think?
Post not yet marked as solved
Hi Rich,I have a question about receiving SKPaymentTransactionStateFailed followed by SKPaymentTransactionStatePurchased.As recommended, when receiving SKPaymentTransactionStateFailed, we finish the transaction. We also display an error to the user because the transaction failed and they should know there was an error (and we have no way to know that this "failed" will be followed by a "success"). However, the transaction then switches to SKPaymentTransactionStatePurchased and is purchased. But in the meantime, the user has seen as "Failed" alert error and will attempt to buy the item again, since they believe the first purchase didn't go through.How are we supposed to handle the following:- display a proper error message if there was an actual error- not display an error message if the transaction fails and is then followed by a "StatePurchased" notification ?
