Search Issue Tracker
Fixed
Fixed in 2021.3.49f1, 2022.3.60f1, 6000.0.41f1, 6000.1.0b9, 6000.2.0a6
Votes
0
Found in
2021.3.49f1
2022.3.60f1
6000.0.41f1
6000.1.0b9
6000.2.0a6
Issue ID
UUM-99408
Regression
No
"In-App Purchases" name mismatch in Project Settings window and Package Manager Window
Steps to reproduce:
1. Create new Unity project
2. Open PM window
3. Find In-App Purchasing package and observe the name “In App Purchasing” (make sure the In App Purchases package is installed)
4. Open Project Settings window and select Services > In-App Purchasing
5. Observe the name in Project Settings > “In-App Purchases”
Actual results: There is a mismatch in naming IAP package (“In App Purchasing” > in PM, “In-App Purchases” > in Project Settings”)
Expected results: Package name should be similar
Reproducible with versions: 2021.3.49f1, 2022.3.60f1, 6000.0.41f1, 6000.1.0b9, 6000.2.0a6
Tested on (OS): Apple M1 Max, Sequoia 15.2
Notes:
- 2021.3 > Project settings naming is set to “In-App Purchasing Settings”
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
Fixed in com.unity.purchasing 5.0.0
Resolution Note (fix version 6000.2.0a6):
Fixed in IAP 5.0.0
Resolution Note (fix version 6000.1.0b9):
Fixed in IAP 5.0.0
Resolution Note (fix version 6000.0.41f1):
Fixed in IAP 5.0.0
Resolution Note (fix version 2022.3.60f1):
Fixed in IAP 5.0.0
Resolution Note (fix version 2021.3.49f1):
Fixed in IAP 5.0.0