Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0a2
2018.1.0b2
Issue ID
987110
Regression
Yes
Application.PersistentDatapath resolve differently in editor and player
How to reproduce:
1. Open Unity
2. Load tester-submitted project(PersistentDataPathTest.zip)
3. Open 'Test.unity' scene
4. Play the scene and observe Application.PersistentDataPath directory
5. Build the scene
6. Run the application and observe Application.PersistentDataPath directory
Expected result: Both in Unity Editor and Player Application.PersistentDataPath directory is the same
Actual result: Unity Editor Application.PersistentDataPath directory differs from the one returned in Player
Reproducible with - 2018.1.0a2, 2018.1.0b2
Not reproducible with - 5.6.5f1, 2017.1.3f1, 2017.2.1p2, 2017.3.0p2, 2018.1.0a1
Fixed and verified in 2018.2.0a1
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 when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Add comment