"Export to file" failing with SecurityException about osmand

[gerardlt]

As an aside, I'd note that I agree with the raiser of #12264 - it would be preferable to save the backup directly - although I understand the argument for implementing the export as a "share" instead.

[gerardlt]

I should also add that I finally resolved my migration issue by using adb to access the file system and copy the generated export osf directly. This was also the method I ended up using to copy my resource files to the new device.
While this was a workaround for me, and perhaps also for many of the kinds of user attracted to OsmAnd, it wouldn't be an advisable option for most users. I'm just lucky that I've done a spot of app development so had the tools available.

[Vucumpra]

Note that for me, sharing never work when I share to a computer using KDEconnect. I need to save it locally first

[EssBee59]

have run into the file access problems created by the Android API changes,

the new access policy in android 11 or 12 is very strong!
So I moved the storage location of Osmand from storage/XXXX-XXXX/Android/data/net.osmand/files/ to storage/XXXX-XXXX/Android/media/net.osmand/files
(using: settings ==> Osmand Settings ==> Data storage folder ==> Manually specified)
the "media" directory is readable by every app!
And the export is running by me!

An other advantage, you can see all the osmand-files using your FX file manager

hope it helps

[zipav]

OsmAnd Nightly 4.7.0#1402m, released: 2024-01-21

On the latest version of OsmAnd Nightly is not reproduced, it exports successfully to the file manager ( I selected the internal drive in the file manager).