Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2019.4.36f1
2020.3
Issue ID
1404629
Regression
No
[Android] Mapping.txt file does not provide any data when Custom Base Gradle Template is selected in Publishing Settings
Reproduction steps:
1. Open the attached user's Unity project "normal.zip"
2. Go to Assets > Scenes folder and open "SampleScene.unity" Scene
3. Go to Build Settings and make sure that Android Platform is select
4. Navigate to Edit > Project Settings > Player > Publishing Settings
5. In the Build section makes sure that "Custom Base Gradle Template" is checked
6. Go to Build Settings and Build the project
7. Navigate to the project folder > Temp > gradleOut > launcher > build > outputs > mapping > release
8. Open "mapping.txt" and observe the file
Expected result: The "mapping.txt" file provides data
Actual result: The "mapping.txt" file is empty
Reproducible with: 2019.4.36f1, 2020.3.30f1
Could not test with: 2021.2.14f1, 2022.1.0b10, 2022.2.0a7 (Folders inside Temp folder are not generated)
Notes:
- If "Custom Base Gradle Template" is unchecked in the 2019.4.36f1 Unity version the "mapping.txt" file provides data
- If "Custom Base Gradle Template" is unchecked or checked in the 2020.3.30f1 Unity version the "mapping.txt" file does not provide any data
- The "seeds.txt" and "usage.txt" always provide data if "Custom Base Gradle Template" is checked or unchecked
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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
Resolution Note (2022.2.X):
I could see your “proguard-user.txt” contains -dontobfuscate options, which disables obfuscation. So if you remove the option you can have mapping information in the mapping.txt.
If you are considering using proguard, I guess you want to remove “-dontoptimize”, too.
I googled here and there. And I assume if there is no mapping information, it seems that there is no mapping.txt, or there is a mapping.txt file with empty content or comment with empty depending on the version. Please note this.
Please refer to the link below for the options.
https://www.guardsquare.com/manual/configuration/usage#dontoptimize
https://www.guardsquare.com/manual/configuration/usage#dontobfuscate