Bug 2186 - InApp purchases: SKPaymentTransactionState.Restored is never used
Summary: InApp purchases: SKPaymentTransactionState.Restored is never used
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 5.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2011-11-23 15:47 UTC by Costas Economopoulos
Modified: 2013-12-05 18:34 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Costas Economopoulos 2011-11-23 15:47:43 UTC
I am writing an app with InApp purchases, and I use the:

public override void UpdatedTransactions (SKPaymentQueue queue, SKPaymentTransaction[] transactions)

method to process the end of an InApp transaction. Everything works fine except when a user buys an item already bought. The AppStore message is correct (i.e.. You have already purchased... Press Ok to download again), but transaction.TransactionState has the value SKPaymentTransactionState.Purchased instead of SKPaymentTransactionState.Restored, as if the user buys the item for the first time.
Comment 1 Miguel de Icaza [MSFT] 2012-03-12 23:09:19 UTC
I do not believe this is a bug in MonoTouch, but a problem with Apple's APIs.

Could you provide a self-contained test case?
Comment 2 PJ 2013-11-19 17:04:26 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 3 PJ 2013-12-05 18:34:29 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.