Wrong Dirs.MusicDir after upgrade from joltup

[halaei]

The Android directory constants are changed in #2. I think the change is wrong. Apps are still allowed to save files in root directories. For example, we let our app save their audio files in /storage/emulated/0/Musics. After migration to this package, the constants are changed and files are stored in private directories, which is wrong, at least for the purpose of our application.
I wonder if you can rollback the change, or introduce new constants for the legacy paths.
Thanks.

[RonRadtke]

Fixed in https://github.com/RonRadtke/react-native-blob-util/releases/tag/0.16.2

[omidshafai]

This issue still exists in version 0.16.2.
The value of Dirs.MusicDir in this package is "/storage/emulated/0/Android/data/com.test.app/files/Music".
While in the joltup/rn-fetch-blob package, its value is "/storage/emulated/0/Music".

[feraswfares]

@omidshafai
did you fix this problem ??

[feraswfares]

hello @RonRadtke
fist thank you very much for maintaining this library, I really appreciate your work.

This issue still exists in version "react-native-blob-util": "^0.16.2",
"react": "17.0.1",
"react-native": "0.64.1",
android :v9 and v11

can you please fix this

[RonRadtke]

@feraswfares witch directory did you use?
Did you use the legacy paths as mentioned in the release notes?
@omidshafai please read the release notes directly above you comment, this should fix your problem :)

[feraswfares]

@RonRadtke

this is how i use the path

  RNFetchBlob.config({
    fileCache:true,
    path: `${RNFetchBlob.fs.dirs.DownloadDir}/${name}`,
  })
    .fetch(
      'POST',
      url,
      {
        // Headers...
        Authorization: `Bearer ${accessToken}`,
        'Content-Type': 'application/json',
      },
      body,
    )
    .progress((received, total) => {
      Console.log('progress', received / total);
    })
    .then((res) => {
  
    })
    .catch((err) => {
   
    });

if i try to use this

RNFetchBlob.fs.dirs.LegacyDownloadDir

i will got this error
File Error: [Error: Unexpected FileStorage response file: null]

[feraswfares]

@RonRadtke
same problem here
https://stackoverflow.com/questions/73962988/how-to-get-the-legacy-paths-in-react-native-blob-util

[RonRadtke]

I'll take a look later at it.
Wich device and Android are you using? On newer Android versions this path might very well be emtpy since the API is deprecated

[feraswfares]

Thank you @RonRadtke

it is not working on both

samsung galaxy edge with android version 9.0
samsung galaxy A03 with android version 11.0

[RonRadtke]

@feraswfares I changed it now back to the old implementation (not live yet).
But this will lead to an "undefined" for API >= 29 for the legacy values.
And besides the current joltup lib version is using the same methods I'm currently using so should return the same "bad" path

[feraswfares]

@RonRadtke Thank you

i use this workaround
react-native-fs for android and calling RNFS.DownloadDirectoryPath

and its work like a charm for both android 9 and android 11