Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.2.0f3
Issue ID
964566
Regression
No
[MacOS] EditorPrefs.SetString fails to set value if used in batchmode
To reproduce:
1. Download project
2. Run from command line:
/Applications/Unity/Unity.app/Contents/MacOS/Unity -batchmode -quit -projectPath [PATH_TO_PROJECT] -executeMethod SetPrefs.SetData -logFile
3. 'Set: CustomData' message is thrown to console log, which means EditorPrefs.SetString was called
4. Run: /Applications/Unity/Unity.app/Contents/MacOS/Unity -batchmode -quit -projectPath [PATH_TO_PROJECT] -executeMethod SetPrefs.GetData -logFile
Expected: 'Get: CustomData' message to console log will be thrown
Actual: 'Get: Nothing' message to console log is thrown
Reproduced on: 5.6.3p4, 2017.1.2p1, 2017.2.0p1, 2017.3.0b6, 2018.1.0a2
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
Any fix to this will be risky. Given the existence of a workaround, this is not something that we should fix.