Wednesday, April 29, 2009

Traces do not appear on the OSM Server issue

As you may have heard, on April 21st the OpenStreetMap server has migrated to the new version of the API. Together with switching on the new API version, the old API version was switched off. This has brocken the application. Unfortunately, the issue was not really predictable nor testable in advance: in a normal production evironment if you have multiple applications working with your API, migration is normally stepwise, and the old API is not switched off immediately. For the OSMTrack it was not possible to test the new API before the switch was made: though it was online for some time already, before April 21 the new API was in a read only mode - not really useful for an application that only writes data. Furthermore, the switched-off API has returned error as text inside an HTML document - it's ok if you have the function integrated in a web application running in a browser, but pretty difficult to parse for other types of applications. That's why you didn't get any error messages but the tracks have never appeared on the server. The fix was simple, I incremented the API number and everything works again. However, before you get the update it has to go through the Apple review process, it may take a couple of days. I'm sorry for the issue and thank you for your patience.

6 comments:

Ciaran said...

No worries, thanks for posting the update, hopefully it will come through the apple review process soon!

Anders Rasmussen said...

has apple reviewed it yet?

dtbow said...

No, I have no response yet. I will inform you as soon as I get the confirmation.

Brian said...

Thanks for posting this -- I'd just downloaded the app, but couldn't figure out why it wasn't working. I'm looking forward to the fix!

Anonymous said...

still not working!!

dtbow said...

Hi Anonymous, the issue I described in the post is fixed. I suppose, you have a different one. Please contact me per email: how exactly it doesn't work in your case?

I'm aware that there are issues with jailbroken iPhones, if you have one please wait for the next major release (should come very soon) - in it I implemented an application-wide error handling to better find origins of problems. At the moment it is difficult to debug the app on systems that I don't own.