merlos/iOS-Open-GPX-Tracker

app crashes, can't get a file out

Opened this issue · 9 comments

Hello,
I've used this app to track a road trip in the Outback, but I wasn't careful with file size / number of points and the app crashed. It now cannot load up the file, it gets stuck in that loading stage and I can't do anything with it. Is there any way, please, to get the file out, to somehow locate and get it out of the ipad? I really would like to save it as it was once in a lifetime trip. Thank you.

has the file been saved or is it attempting to 'recover' the file?

if the file was saved but can't be presented on the app's map, you should be able to get the file via iTunes File Sharing

If the GPX Tracker folder in Files app's On my iPad section shows nothing there, it could be possible that the file is not saved yet, rather, it's only cached in the app's database (which is used for the crash recovery purpose)

I guess a way to get a file out could be to modify the code in a way that directly writes the database contents on to a file.
Probably a modified app submitted as a TestFlight

Since you are somewhat certain that the file was indeed saved, I think you can try the 'old-school' way of iTunes File Sharing, as I've mentioned earlier.

Basically, connect your iPad to your Mac or PC.

For Mac, you will use the Finder app, locate your device, tap on the 'Files' column and select 'GPX Tracker'. Ideally, a list of GPX files should be presented, which you can basically drag and drop to a preferred destination. From there on, you could view the GPX file with any viewer.

For Windows, I know that in the past, you could use the iTunes app to do basically the same thing, but I am unsure if the iTunes app has been replaced with something newer or not. Regardless of iTunes or the newer alternative, it should still be possible to reach a similar outcome.

In the event where you did retrieve the file but it is corrupt in some way, feel free to let me know, if necessary I might be able to manually fix it for you.

In that case, I think the best way forward would be to push some version of a specially edited app to TestFlight, which the sole purpose is to extract the relevant data out in some way or form.

Would need @merlos help in that case, for that the TestFlight build will need to be of the same bundle identifier for this to work.

(Of course, all this is presuming that the data is actually still in the database somewhere, rather than it being some obscure edge case where the app just got stuck in a indefinite state for whatever reason)