Search Issue Tracker
Active
Under Consideration for 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X
Votes
0
Found in
2022.3.62f1
6000.0.50f1
6000.1.4f1
6000.2.0b3
Issue ID
UUM-109747
Regression
No
MacOS persistentDataPath uses old path when built compared to Editor Play mode
How to reproduce:
1. Open the attached “IN-101863” project
2. Enter Play mode
3. Observe the path in Game View
4. Exit out of Play mode
5. Delete the folder “IN-101863“ observed in the path
6. Build And Run the project
7. Observe the path in the Player
Expected result: The path in the built project Player is the same as the one in the Editor’s Play mode
Actual result: The built project Player displays a different path than the path in the Editor’s Play mode
Reproducible with: 2022.1.0a4, 2022.3.62f1, 6000.0.50f1, 6000.1.4f1, 6000.2.0b3
Reproducible on: MacOS 15.5 Silicon
Not reproducible on: Win10
Note: On Windows 10, the path (_%userprofile%/AppData/LocalLow/<companyname>/<productname>_) remains the same in Editor Play mode and when in the built Player. As per the documentation [https://docs.unity3d.com/6000.1/Documentation/ScriptReference/Application-persistentDataPath.html|https://docs.unity3d.com/6000.1/Documentation/ScriptReference/Application-persistentDataPath.html|smart-link]
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Multiple errors occur when setting the Render Object Event to AfterRenderingPostProcessing while using STP for Upscaling
- UnityYamlMerge.exe doesn't correctly handle merge conflicts in modified properties on a prefab variant
- Inconsistent color scheme in "Details" section of "Select Presets" inspector window
- Crash on __pthread_kill when launching Editor via command-line with "-disableManagedDebugger" argument
- [VFX] Deleting “New Group Node” name doesn’t allow to type or add new name
Add comment