Android APP - Chrome API: can't save any file (also blackbox) - console error

[limonspb]

Current Master 10.8.
Current Commit:

commit dd183f041200b2b095f9a3eefe0a8fbff786acbc (HEAD -> master, upstream/master)
Merge: 41747c65 4c9fbc6a
Author: J Blackman <blckmn@users.noreply.github.com>
Date:   Tue Nov 9 18:17:18 2021 +1100

    Auto merged - #2634 at Tue, 09 Nov 2021 07:17:18 GMT

    Split header and fix i18n message

Can't save a BlackBox file from the Android app and basically any file if using chrome API - probably a permission issue, but the app did not ask me about anything after installation. Same problem occurs when saving a backup from presets tab
Console says the following:

Chrome API Error: FILESYSTEM (adapted from Cordova): [object Object].
 Traced Error
    at checkChromeRuntimeError (http://localhost/js/utils/common.js:1537:90)
    at http://localhost/js/tabs/onboard_logging.js:612:17
    at chromeCallbackWithError (http://localhost/js/cordova_chromeapi.js:20:18)
    at http://localhost/js/cordova_chromeapi.js:341:25
    at fail (http://localhost/plugins/cordova-plugin-file/www/DirectoryEntry.js:77:9)
    at Object.callbackFromNative (http://localhost/cordova.js:289:52)
    at <anonymous>:1:9
checkChromeRuntimeError @ common.js:1537

Samsung galaxy S21 Ultra 5G

[limonspb]

@WalcoFPV, @asizon any ideas? Thanks!

[asizon]

Yes, this save file system is outdated, i think apk is ready to put the flight controller in masive storage to then save your logs.

[limonspb]

Yes, this save file system is outdated, i think apk is ready to put the flight controller in masive storage to then save your logs.

@asizon
So there is no way to save ANYTHING to a local file? Because i am having the same problem with saving txt file. (presets tab, save backup config)

git bisect showed that the issue started happening after
#2577
by @mikeller

[WalcoFPV]

Looks like, as @asizon said, the save file system is outdated. With #2577, the android-targetSdkVersion was set to 30 and before we juste defined android-minSdkVersion to 19. So it's possible that the SDK version used has changed. The cordova plugin used for filesystem could not be compatible with this new SDK version

[limonspb]

Looks like, as @asizon said, the save file system is outdated. With #2577, the android-targetSdkVersion was set to 30 and before we juste defined android-minSdkVersion to 19. So it's possible that the SDK version used has changed. The cordova plugin used for filesystem could not be compatible with this new SDK version

I am a little confused now. Is there a way to save/load any (TXT) file into Android phone internal storage now from the Configurator?
I am using
chrome.fileSystem.chooseEntry
works good on Desktop, just not on Android anymore

[WalcoFPV]

chrome.fileSystem doesn't exist on Android. I had to defined it in src/js/cordova_chromeapi.js using Cordova FileSystem. The issue is probably in this file. I will take a look to this issue

[haslinghuis]

@limonspb Can you test saving on external storage (SD Card)?

[limonspb]

@limonspb Can you test saving on external storage (SD Card)?

Not sure how this is done. The path for saving is picked automatically

[WalcoFPV]

The issue seems to be related to the new Android 11 storage rules. Apps can no longer create their own directory in the root directory of the device. /Android/data/betaflight-configurator is still writable : instead of saving files in /Betaflight configurator., we can save files in it as a workaround

[limonspb]

The issue seems to be related to the new Android 11 storage rules. Apps can no longer create their own directory in the root directory of the device. /Android/data/betaflight-configurator is still writable : instead of saving files in /Betaflight configurator., we can save files in it as a workaround

Interesting. Why I was able to still use old version of the app to save files on the roof directory/betaflight? On Android 11

[WalcoFPV]

@limonspb Because of the targetSdkVersion set to 30 in #2577. The app is now targetting devices with Android 11. Before, the targetSdkVersion was lower and the new Android 11 rules were not applied if I understand correctly