Opening GPX file runs into error concerning "Content URI"
Hello,
I have downloaded an *.gpx file on my android phone (Samsung Galaxy S9). Now I want to open the downloaded file
Option 1) Directly in the notification message that file was downloaded I can select "open"=> Locus is not offered as application for opening this file
Option 2) Using FX Explorer I navigate to the directory where the *.gpx file was downloaded and select "Open with". There Locus app is displayed, but in deactivated manner (see screenshot "Screenshot_20190821-114038_FX.jpg"). When anyway selecting the Locus item, an error message occurs referencing the above mentioned "Content URI" (see screenshot "Screenshot_20190821-114049_FX.jpg")
As I'm using the feature of downloading *.gpx files and opening in Locus quite often, I would be very happy if there is any possibility to get this issue fixed.
Best regards,
Christoph
The same question 
Additional consideration:I did the same as described in Option 1), this time with Chrome web-browser (before it was done with Samsung web-browser). With Chrome I do receive the possibility to open gpx file in Locus - so maybe an issue of the Samsung web-browser, rather than an issue of Locus ?!
Moreover, I just now got aware that Option 2) potentially has been already addressed in the past within topic https://help.locusmap.eu/topic/support-for-content-uri ...
In any case would be good to receive your understanding on this issue.
Best regards, Christoph
Additional consideration:I did the same as described in Option 1), this time with Chrome web-browser (before it was done with Samsung web-browser). With Chrome I do receive the possibility to open gpx file in Locus - so maybe an issue of the Samsung web-browser, rather than an issue of Locus ?!
Moreover, I just now got aware that Option 2) potentially has been already addressed in the past within topic https://help.locusmap.eu/topic/support-for-content-uri ...
In any case would be good to receive your understanding on this issue.
Best regards, Christoph
Hello Christoph,
interesting problem(s). I've downloaded FX Explorer and together with my favorite "Intent intercept" application, it is easy to test it.
Tap on "Open with" may now be opened with mentioned Intent intercept, where is again visible missing "L" at the end of mime type. After the change to correct mime-type, Locus Map is offered. It seems that it does not handle the file. I'll look at it ...
Menion
Hello Christoph,
interesting problem(s). I've downloaded FX Explorer and together with my favorite "Intent intercept" application, it is easy to test it.
Tap on "Open with" may now be opened with mentioned Intent intercept, where is again visible missing "L" at the end of mime type. After the change to correct mime-type, Locus Map is offered. It seems that it does not handle the file. I'll look at it ...
Menion
Hello Christoph.
seems that using Intent intercept, permission (to open file) granted by FX Browser is no longer valid, so it is not possible to test functionality correctly by this method. Anyway, I've tried two more browsers and with both, Locus Map correctly handles the supplied file.
For me, it still looks like a problem in mime-type in FX browser. Once this will be fixed, we may try to start the search for issue in Locus Map (if there still be any).
Menion
Hello Christoph.
seems that using Intent intercept, permission (to open file) granted by FX Browser is no longer valid, so it is not possible to test functionality correctly by this method. Anyway, I've tried two more browsers and with both, Locus Map correctly handles the supplied file.
For me, it still looks like a problem in mime-type in FX browser. Once this will be fixed, we may try to start the search for issue in Locus Map (if there still be any).
Menion
Replies have been locked on this page!