Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.6f1
Issue ID
1082903
Regression
No
ApplicationIdentifier not used when building the first time via script from command line for the first time
Steps to reproduce:
1. Download the attached project
2. Build from command line with the following arguments:
<path to editor> -quit -batchmode -nographics -logFile "build.log" -projectPath <path to project>-executeMethod unitybase.BuildScript.LuminBuild
Expected result: Application Identifier is com.mycompany.myname,
Actual result: Application Identifier is reset to default
Notes:
- Application Identifier should be normal on a second build
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note (2018.3.X):
Build pipeline has evaluated this issue and determined that it does not meet our current bug severity threshold. If you would like your issue to be reviewed again, please re-submit your bug.