MapsforgeV3 Permissions Fix (Offline Map Fix!)#405
Conversation
na7q
changed the title
|
I've tried the code, but it attempts to map a MSF URI to /storage/msf/1234567, which then fails. |
|
There's apparently a couple devices that have this issue, and nobody is willing to take a few minutes to give me any info. So I've been unable to fix it. However, 99% of devices seem to work fine. |
|
This test was on a Samsung S24 device running Android 16. I've lost track of the ways that Google has mutliated SD card access over its major releases, and Samsung implementing additional quirks that often break installations. Do you have a link to the relevant MSF documentation for what you tried to achieve, or maybe an alternative approach? What are you trying to do with this PR, and how is it supposed to work out? I would assume that you need to query the MSF content provider to obtain a real file path, which is required by mapsforge v3. I thought about using a specific location where both the app and the file manager are allowed without additional permissions. Unfortunately, the app-specific folder on the SD card Maybe the better approach would be to just kick mapsforge v3 altogether. In fact, I already have a very rough implementation using VTM which can show the map, but doesn't render stations or paths yet. |
|
This PR very specifically allowed the mapsforge to work again on the newer OS version where it require the external storage access to get the map files. So you could select a map, and it would work fine. However this method doesn't play well when you have to abide by Google's nonsense rules for the play store. |
|
I understood the intention of the PR, but not the mechanism that you tried to implement. Could you please elaborate on that? I can also test and provide debug info from my phones that fail to process the functionality as designed. |
2 participants
This PR fixes the problem with offline maps using the MapsforgeV3 offline maps. It adds needed permissions, as well as fixes the URI storage path.