I can reproduce this with 4.30 at any time but downgrading to 4.29 (or alternatively using another file manager as I mentioned) is working for me (at my phones). Sorry, I haven't blamed Garmin, but pointed out, that after updating to Connect 4.30 the *.gpx import on my device didn't worked as before. 4.29 is definitely handling the 'Open with' command different compared to 4.30 So it's not so easy to find the reason, you must look at the source code for deeper investigation. If that's the case the 'selected' app is called and it's this app, who must handle an intend -> that means it must get the 'intent' message, extract the file name and doing the handling for this file.Īn Intent is a sort of interface for communication between different apps. Technically spoken, a file manager is asking the Android system if there is an app that is able to handle a *.gpx file while the Android system is looking if an app that is able to handle gpx files is registered. First I assumed there could be a problem with the decimal separator, but that isn't obviously the case.

So for me it seems they have changed the internal (intent) handling or something like that in vers. I have rebooted the devices several times, cleared the caches of file managers and Garmin Connect app, etc., but 4.30 always throws an error message after it's has been opened by the 'Open with' command. I have double checked this with several *.gpx files on three different smartphones/tablets and I'm always able to reproduce this 'error' with 4.30.

4.29 does not make any trouble at all on my phones. Some file managers are working with 4.30 and some not. For me at the moment this is the only working alternative (or downgrade to vers. Maybe the Garmin developers will investigate or not.Īs far as I know you can use the mentioned file manager for free (but you will see some ads).

Total commander dateimanager