Search Issue Tracker
Fixed in 2.2.2
Votes
0
Found in [Package]
2019.2.7f2
2019.4
2020.1
2020.2
2021.1
Issue ID
1293859
Regression
No
[IAP] logs are incorrectly formatted when "m_Logger.Log("purchase({0})", product.definition.id);" is called
How to reproduce:
1. Open the user's attached project
2. Load the Scene "MainMenu"
3. Click on the "Store" button
4. Click on the "In-App Purchase" button
5. Purchase any of the options by clicking one of the square icons (for ex. "BOOST! x1 0:01:00")
6. Open the Console window and look at its logs
Expected result: "purchase(rollaball_1x1_boost):"
Actual result: "purchase({0}): rollaball_1x1_boost"
Reproducible with: 2019.4.17f1, 2020.1.17f1, 2020.2.2f1, 2021.1.0b1
Could not test with: 2018.4.30f1 (multiple Console errors after downgrading)
Notes:
- IAP 2.2.1 and 3.0.0-pre.4 was used when testing
- "m_Logger.Log("purchase({0})", product.definition.id);" can be found in the "PurchasingManager.cs" line 61
Comments (1)
-
Tankzo
Jan 05, 2021 22:18
I reported this issue and this is NOT a critical bug. (The bug does NOT impact IAP or application work-flow.)
If this is a "quick fix," great, then put time into it. If this is NOT a "quick fix" then please make this a low priority bug because it does NOT impact application or IAP work-flows, it is a cosmetic logging issue.
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
- Editor UI Text is displayed incorrectly or blank, and "Unable to load font face for [System Normal]." and other warnings are spammed when Editor Font is set to System Font and TMP Package is imported
- TabView with icons is smaller in height then other tabs with text
- [iOS] Error shows and "Microphone.GetPosition" logged as zero when "Microphone.Start()" is called the first time while a microphone is busy in another app and the second time when the microphone is released
- "Check for Updates" Fails to Connect to Update Server
- "Validation: Write range..." errors when creating and destroying GraphicsBuffer rapidly in WebGPU
Resolution Note (fix version 2.2.2):
Fixed in: 2.2.2 (2019.4.31f1)