Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
0
Found in
2021.2
2021.2.1f1
2022.1
Issue ID
1379270
Regression
No
The argument "-long-plt" is not present in the "tundra.log.json" log file when the project is built
Reproduction steps:
1. Download the attached Unity project "ArgumentIssue.zip" from Google Drive (link in the edit)
2. Go to File > Build Settings
3. Build the project for an Android
4. Wait for the project to build and go to [Project Folder] > Library folder > Bee folder
5. In the Bee folder find and open the "tundra.log.json" file
6. In the "tundra.log.json" file search for the "-long-plt" argument
Expected result: The argument "-long-plt" is present in the log file
Actual result: The argument "-long-plt" is not present in the log file
Reproducible with: 2021.2.3f1, 2022.1.0a15
Could not test with: 2019.4.32f1, 2020.3.23f1 (Bee folder is not created after building the project)
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
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 2022.1):
Fixed in: 2022.2.0a1
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0b15
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.19f1