Closed GoogleCodeExporter closed 9 years ago
Yes, I appear to be having the same issue. This essentially breaks the app for
me. I can create great data, but I can't do anything with it.
What steps will reproduce the problem?
1. Install osmtracker on Android 5
2. Get a track log
3. Choose "Export as GPX"
What is the expected output? What do you see instead?
Expect it to export to a GPX, instead it says, "Unfortunately, OSMTracker for
Android^TM has stopped." and crashes.
What version of the product are you using (See "About" screen)?
v0.6.6
Make/model of your device, and Android version?
Nexus 5, Android 5.0 (LRX21O)
Please provide any additional information below.
Also seems to crash on upload track to OSM server. I was able to get one to
export after an upload to OSM, but was unable to reproduce. Tracks are between
2000 and 5000 points, with up to 100 waypoints logged. Include photographs,
voice notes, and some of the standard icon based tags.
Unfortunately, I don't know how to provide logs like Marian did above.
Original comment by caseydi...@gmail.com
on 14 Dec 2014 at 3:28
I have the same exact problem. Nexus 5 with android 5 and OSM tracker v0.6.6.
I was able to upload one track to OSM, but I went to upload a second one and I
get the "Unfortunately, OSMTracker for Android has stopped." The track is 5682
trackpoints with 0 waypoints.
Original comment by reportin...@gmail.com
on 14 Dec 2014 at 9:50
I have the same issue. Nexus 5 after update to Android 5, OSMtracker 0.6.6.
Short tracks are sometimes able to export, but long one (20 000 pts) not.
Application crashes.
Is it possible to make a backup of tracks database (or file where tracks are
stored) before export?
Original comment by vaclav.k...@gmail.com
on 14 Dec 2014 at 10:41
Thanks for the reports. I can't reproduce it since I don't have an Android 5
device and the emulator is excruciatingly slow, but I may have found a problem
with the code. The Dialog is updated in the background task, which won't work
since it's not on the UI thread.
If I were to attach an fixed APK here, would you guys be able to test it for
me? It would save me from doing a release without making sure the issue is
fixed.
Original comment by nicolas@guillaumin.me
on 15 Dec 2014 at 9:19
Hi. I can test it. No problem.
Original comment by Marian.K...@gmail.com
on 15 Dec 2014 at 9:20
Thanks, APK attached. I'm not sure what will happen if you installed an
unsigned APK over a signed one, so I suggest exporting all your tracks to GPX
to make a backup before...
Original comment by nicolas@guillaumin.me
on 15 Dec 2014 at 9:34
Attachments:
I've uninstalled the Market version, enabled installation from unknown sources.
Installation says, that it was installed, but it is not true. I can't find the
program in the list. And when I try to start it directly from the installer I
only got an error message that it stopped working :-(
Original comment by Marian.K...@gmail.com
on 15 Dec 2014 at 12:49
I can't reinstall it over existing app. I have obtained message that package
with the same name and conflict signature is already installed.
Original comment by vaclav.k...@gmail.com
on 15 Dec 2014 at 1:15
That's why I uninstalled it.
Original comment by Marian.K...@gmail.com
on 15 Dec 2014 at 1:24
I was wrong. It is installed. But still crashing.
E/AndroidRuntime(13095): Process: me.guillaumin.android.osmtracker, PID: 13095
E/AndroidRuntime(13095): The import me.guillaumin.android.osmtracker.R cannot
be resolved
E/AndroidRuntime(13095): at
me.guillaumin.android.osmtracker.activity.TrackManager.<init>(TrackManager.java:
7)
Original comment by Marian.K...@gmail.com
on 15 Dec 2014 at 7:44
Thanks, seems to be a different reason, probably due to the debug build. I
think I'll just release it since my changes are good changes anyway.
Original comment by nguillau...@office.funnelback.com
on 16 Dec 2014 at 3:49
Ok. I'll check. And it reminds me, that I planned to update Czech translation
;-)
Original comment by Marian.K...@gmail.com
on 16 Dec 2014 at 4:45
Update has been pushed to the market, let me know if it fixes it!
Original comment by nicolas@guillaumin.me
on 16 Dec 2014 at 8:53
On my device works. Thank you.
Original comment by vaclav.k...@gmail.com
on 16 Dec 2014 at 9:45
Yes. I can confirm that it works now. Thanks a lot.
Original comment by Marian.K...@gmail.com
on 16 Dec 2014 at 11:27
Works well for me too. Thanks a lot!
Original comment by michel.k...@googlemail.com
on 16 Dec 2014 at 3:19
Cool :)
Original comment by nicolas@guillaumin.me
on 18 Dec 2014 at 8:50
Original comment by nicolas@guillaumin.me
on 18 Dec 2014 at 8:50
Original issue reported on code.google.com by
Marian.K...@gmail.com
on 12 Dec 2014 at 8:21Attachments: