iOS calls handleRestore before restore is finished.

[Trurl101]

iOS: 26.4
gdx-pay: 1.3.10

Log:

2026-04-03 14:26:37.355 IOSLauncher[1030:116842] [GdxPay/AppleIOS] All transactions have been restored!
2026-04-03 14:26:37.415 IOSLauncher[1030:116842] [GdxPay/AppleIOS] Transaction has been restored: xxx
2026-04-03 14:26:37.415 IOSLauncher[1030:116842] [GdxPay/AppleIOS] Transaction has been restored: xxx

PurchaseManageriOSApple calls restoreCompletedTransactionsFinished before restoredTransactions is filled, so the call to observer.handleRestore always is empty.

As result restorePurchases does not work correctly, several users of my apps complained, sometimes it seems restore delivers a few transactions but not all. In my tests transactions was always empty when handleRestore was called. Even when the log shows that "Transaction has been restored".

Android restore works fine.

[Trurl101]

A "change" that works for me: copied the whole PurchaseManageriOSApple class and and added a timer in restoreCompletedTransactionsFinished. That is obviously only a hacky workaround not a good solution but I don't know where and why restoreCompletedTransactionsFinished is called prematurely.

@Override
public void restoreCompletedTransactionsFinished(SKPaymentQueue queue) {
	// All products have been restored.
	log(LOGTYPELOG, "All transactions have been restored!");

	//observer.handleRestore(restoredTransactions.toArray(new Transaction[restoredTransactions.size()]));
	//restoredTransactions.clear();
	Timer.schedule(new Timer.Task() {
		@Override
		public void run() {
			observer.handleRestore(restoredTransactions.toArray(
				new Transaction[restoredTransactions.size()]));
			restoredTransactions.clear();
		}
	}, 5);
}

[aberkowski]

I confirm the issue.
I think that the problem occurs only in the newest iOS version (26.4). I did not encounter any problems in 26.1 and older versions on my test devices. Only 26.4 iOS users reported this problem to me. The problem exists with real and test in-app purchases (sandbox). I use gdx-pay 1.3.9 version

[keesvandieren]

Ok, does it also happen with subscriptions?

If yes I will try to reproduce it. Also, PRs welcome

[aberkowski]

@keesvandieren I don't know if this also happen with subscriptions, because I don't have any. @Trurl101 have you tested this issue with subscriptions?

[Trurl101]

@keesvandieren I don't know if this also happen with subscriptions, because I don't have any. @Trurl101 have you tested this issue with subscriptions?

I don't know. I don't use subscriptions in iOS Apps.

[keesvandieren]

@Trurl101 / @aberkowski can you please try the latest version in your app?

Also, there is PurchaseManageriOSApple2. Difference between existing PurchaseManageriOSApple and new PurchaseManageriOSApple2 are documented in README.md (basically if you target ios 15+ you can switch to PurchaseManageriOSApple2)

Looking forward to your test results

[keesvandieren]

Hi @Trurl101 / @aberkowski have you been able to test the latest master-branch code?