First a "Sorry" for asking a question which isn't related to actual test version.
My issue is highly developer specific and very technical and I don't know another place to ask for.
Fell free to point me to a better place.
I import a kmz file to Locus to add points to the map. My technique worked in the past but not longer. Maybe because of the point/track database changes.
The issue is that the point itself is imported but it doesn't contain the media files specified in doc.kml.
I see that the media files are copied to media/menion... /data/import/<name of the point>/ during the import.
I tried many many ways to specify the files in doc.kml but found no one to make it work.
Fun fact:
Export a point with media files in Locus. Delete the point in Locus and import the kmz seems to work. The media files are there.
BUT (!) when changing the media file name and adapting the kmz written by Locus to the new file name has the same issue.
I guess with the original filename it just works bcs the file is somewhere else in a Locus database and it doesn't use the one in data/imported folder. This means importing the original kmz on another device shouldn't work, too.
I know the priority of such a bug is low but maybe I have luck and a Locus developer already knows where to look and the fix takes just a minute.
Way to reproduce:
Click on the appended kmz with a data manager. Android will ask for an App to use.
Select Locus.
It might do nothing the first time.
In this case just close Locus and do it again. Might need two or three retries.
Then Locus will ask for a folder to import.
Press import and check the new point. It will not contain the files "Audio......" and "description".
That the import often doesn't work is also a "new" bug. But easy to workaround so it's not an issue.
My issue is highly developer specific and very technical and I don't know another place to ask for.
Fell free to point me to a better place.
I import a kmz file to Locus to add points to the map. My technique worked in the past but not longer. Maybe because of the point/track database changes.
The issue is that the point itself is imported but it doesn't contain the media files specified in doc.kml.
I see that the media files are copied to media/menion... /data/import/<name of the point>/ during the import.
I tried many many ways to specify the files in doc.kml but found no one to make it work.
Fun fact:
Export a point with media files in Locus. Delete the point in Locus and import the kmz seems to work. The media files are there.
BUT (!) when changing the media file name and adapting the kmz written by Locus to the new file name has the same issue.
I guess with the original filename it just works bcs the file is somewhere else in a Locus database and it doesn't use the one in data/imported folder. This means importing the original kmz on another device shouldn't work, too.
I know the priority of such a bug is low but maybe I have luck and a Locus developer already knows where to look and the fix takes just a minute.

Way to reproduce:
Click on the appended kmz with a data manager. Android will ask for an App to use.
Select Locus.
It might do nothing the first time.
In this case just close Locus and do it again. Might need two or three retries.
Then Locus will ask for a folder to import.
Press import and check the new point. It will not contain the files "Audio......" and "description".
That the import often doesn't work is also a "new" bug. But easy to workaround so it's not an issue.