rolinger commented on issue #560: URL: https://github.com/apache/cordova-plugin-file/issues/560#issuecomment-1454779591
@breautek - a follow up on this. Could use your input. For Android, I cannot write directly to: `cordova.file.externalRootDirectory` anymore. I guess it changed in API 29/30. However, targeting API 32, I can write to `cordova.file.externalRootDirectory + "MyNewFolder"` and download my file there. Ok, so I got all that working again. However for iOS, I am continually perplexed. For iOS I have now used both `cordova.file.externalDataDirectory` and `cordova.file.dataDirectory` - in BOTH cases, my app can read the root directories and create the `MyNewFolder` in both and then write files to that new folder. In subsequent passes, my app can then read the contents of `MyNewFolder` (in both locations) and see the downloaded file there....ALL via console.log messages. However, on the device itself, the `MyNewFolder` and its file are not accessible in any place that I can find. The folder and new file now exists, but how does the user access them? In the device app `Files`, then in the `On my iPhone` option, it takes me to an empty folder. But if I manually download a file from Safari, a new folder `Downloads` appears in the `On My iPhone` section and the manually downloaded file is now in that folder. Safari must be creating that `Downloads` folder on the first manual download. In my app, I then try to find this new `Downloads` folder (printing the contents of every `cordova.file.PATH` to read its contents (and maybe use it as the future directory to create `MyNewFolder` and write my files there) but I can't find the `Downloads` folder anywhere. Please help me resolve this. I have spent days on this and am pulling out what little hair I have left. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
