Error 500: Internal Server Error when upload GPX data to OSM

[adisadit]

Hi OSMTracker Developer,

I got some issue when I tried to upload GPX data to OSM. It said that "Unable to authenticate to OSM.......internal server error".

Not sure why this happen but I think it related to OSM change their http into https. Because I got same error like this in our local tasking manager version 2.

Hopefully this screenshot will help you guys:

My colleagues also got this error since a week ago.

Thank you..

[Inyaheyukan]

Me too.

[openbrian]

I have this issue too. I need to upload tracks for the San Diego Zoo.

Indeeed, OSMTracker calls http not https. (https://github.com/labexp/osmtracker-android/blob/master/app/src/main/java/org/osmtracker/osm/OpenStreetMapConstants.java#L8)

[hikaruAi]

Same issue here

[cstackpole]

I'm relieved to know that it wasn't just me that this started happening too. I took a BUNCH of tracks yesterday. I can still export and manually upload, but that is really quite annoying and takes a lot of time. Please fix.
[Edit: I use the f-droid version if that matters at all]
Thank you!

[jidanni]

For me the app just totally crashes when I try to upload a track these days. The only workaround is to export to GPX and upload the track manually on the website form. Android 8.0.

[cstackpole]

@jidanni I think that if you go into settings and "Reset OSM authentication" then when you try to upload you will get this error message. Mine did the same thing where it just crashed the first two times and I thought it was due to bad wifi connection. After I did the reset is when I got this message.

[cstackpole]

Bump please? I've got a lot of tracks to uploaded fixes into OSM and doing them one by one via export is draining me. :-) Thanks!

[EmmanuelAB]

Thanks for reporting the issue, we're already working to fix it.

[mkyral]

Hi,
I'm lost a bit. Will be this bugfix published in https://play.google.com/store/apps/details?id=me.guillaumin.android.osmtracker ?

[jidanni]

So the project is unmaintained. Anybody have suggestions for an alternate?

[jamescr]

Our team is assuming the maintenance of the project and this bug unfortunately happened in the midst of the transition.

The original osmtracker developer transferred us the repo only after changing the application package name and the signing key for the play store. Both decisions are completely understandable on his behalf. The problem is that in order to post a bug fix we need to publish a new app rather than an update. This means that users' unpublished traces could be lost.

The bug fix is in progress and it'll be published as v0.6.12 as soon as possible. To get it, it'll be necessary to install the app again. You'll need to export the traces on your current install and push them manually into OSM.

There will be no need to uninstall your current version to install the new one.

[cstackpole]

Thank you for the update @jamescr and the work to get this app updated. It is one of my fav tools for OSM data collection. I will continue to export and upload manually all of my traces and I eagerly await the new version. :-)

[aton1698]

We have created a beta version that solves this issue and it's available on Google play. We'll keep working on some new functionalities for osmtracker.
If anyone finds some issue, please let us know.