Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.4.2p3
Issue ID
854214
Regression
No
[Android] Wrong behavior with external/internal Application.persistentDataPath
Steps to reproduce:
1) Download attached project "FilePermissions.zip" and open in Unity
2) In Player settings, make sure Write Permission is set to "External(SD Card)"
3) Build and run project on a device
Expected result: /storage/sdcard0/Android/data/com.ea.gp.fp/files/
Actual result: /storage/emulated/0/Android/data/com.ea.gp.fp/files/
Note: Looks like Application.persistentDataPath returns wrong path
Reproduced with: 5.3.7p2, 5.4.3p1, 5.5.0f3
Resolution: These both paths are symlinks and are the same. They point to the same place in the internal storage, so it does not matter which of them is returned.
Comments (2)
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 CollectAllSceneManagerAndObjectIDs when opening a specific Scene
- GPU device suspended error when replaying a video in the Video Player with NVIDIA Vertical Sync set to Fast
- GPU device suspended error when replaying a video in the Video Player with NVIDIA Vertical Sync set to Fast
- SetComponentEnabled uses class instead of struct when constraining Enableable Component type
- [iOS] Application.deepLinkActivated does not get invoked while app is running when UIApplicationSceneManifest is added in Info.plist
rmonteiro
Mar 22, 2018 15:32
Able to recreate on 2017.2.1for Samsung GT device
Actual
/storage/emulated/0/Android/data/
Expected
/storage/emulated/legacy/Android/data/
The screencapture.capturescreenshot does store the image in the correct path.
dora-gt
Feb 08, 2018 16:00
reproduced on 5.6.4...
please...