Search Issue Tracker
Won't Fix
Votes
1
Found in
2020.3.46f1
Issue ID
UUM-35573
Regression
No
Unity IAP fails to recover purchases after relogging into a Google Account
How to reproduce:
1. Install Unity IAP example app and make sure it's upgraded to Unity IAP v2.6.0 in the Package Manager. You may need to revise callbacks due to new string parameter.
2. Make sure there are Google Play registered non-consumable products to purchase.
3. Run the app on Android and then purchase a non-consumable item.
4. Quit and terminate the app using the Android System square button.
5. Remove all Google Accounts via Android Settings > Google > Accounts.
6. Clear the storage+cache for the UnityIAP app from Android settings.
7. Run the app. Unity IAP should fail to initialize with an error PurchasingUnavailable.
8. Leave the app but don't terminate it. Go to Android Settings > Google > Accounts and add a new Google Account via login process.
9. Once the account is logged in, return to the Unity app.
Expected result: The SDK client should receive an initialize callback and then Unity IAP should attempt to refresh the product list, having registered the products given to it by the client's previous call to UnityPurchasing.Initialize().
Actual result: Unity IAP will attempt to refresh purchased products and generate an error about the previously-purchased non-consumable. Then right after this, the app will receive an IStoreListener.OnInitialized() callback (now that the user has logged in).
Reproducible with: 2020.3.46f1 (User reported)
Could not test with: 2020.3.47f1, 2021.3.24f1, 2022.2.17f1, 2023.1.0b14, 2023.2.0a12 - Project was not provided
Built with: macOS 12.6.1 (M1 Max)
Error format:
"Unity IAP: Unable to process purchase with order id: GPA.AAAA-BBBB-CCCC-DDDDD and purchase token: abcdefghijklmnop because the product details associated with the purchased products were not found."
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Input from the "Backslash" key is not detected in the Web Player when using the Japanese 106/109 key keyboard
- High "Total" value of the "TerrainManager.CullAllTerrains" when generating terrain
- UI Layout rebuild triggered by a rounding error when using TextMesh Pro
- Sprite Shape Corners and Edges are invisible when a closed Sprite Shape is used
- Script icon Gizmos cause lag/performance issues in Scene view even when the Scene Camera is not pointed at Gizmos
Resolution Note:
There are no fixes planned for this Bug