Can't upload gps trace - stuck in cycle of "Authorize access to your account"

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Long-press a track and Select "upload to openstreetmap"
2. "save and upload"
3. enter username and password (perhaps on oauth screen for openstreetmap or 
something?)
4. get screen saying "authorize access to your account"
5. check to allow "upload gps traces"
6. hit "save changes"
go back to step 4, never getting an upload.

What is the expected output? What do you see instead?
I expect to be authorized and the trace to be uploaded.

What version of the product are you using (See "About" screen)?
OSMTracker for Android v0.6.4

Make/model of your device, and Android version?
Mytouch 4g slide, android 2.3.4

Please provide any additional information below.
I can log in to my openstreetmap account fine, which I established long ago.

At "http://www.openstreetmap.org/user/nealmcb/oauth_clients" I see multiple 
tokens that have been issued to this application, as well as to other apps.

Original issue reported on code.google.com by neal...@gmail.com on 17 Jul 2013 at 7:22

[GoogleCodeExporter]

I have the same issue.
The app is registered on the site, but cannot read the response correctly.
Attached is a screenshot.

Original comment by mkuzmin on 7 Sep 2013 at 12:46

Attachments:

• [2013-09-07 16.42.08.png](https://storage.googleapis.com/google-code-attachments/osmtracker-android/issue-219/comment-1/2013-09-07 16.42.08.png)

[GoogleCodeExporter]

The browser interface doesn't look like the stock Android browser, which 
browser is it?

That might be due to the fact this this browser doesn't support the special URL 
scheme that's used to redirect the user to the application once it has been 
authorized on the OSM website.

Would you be able to try to revert to the stock Android web browser as a 
default and try again?

Original comment by nicolas@guillaumin.me on 8 Sep 2013 at 1:25

[GoogleCodeExporter]

I was using the stock google browser, on Android 2.3.4 (mytouch).

Original comment by neal...@gmail.com on 8 Sep 2013 at 5:09

[GoogleCodeExporter]

Hi,

I just tried with the Android emulator with version 2.3.3 (Same as 2.3.4 as far 
as the SDK is concerned) and it works for me. The browser looks different 
though, so I suspect that your browser is in fact a different one provided by 
the HTC UI, rather than the stock Android.

What's supposed to happen is that the app. should have "registered" this 
special URL osmtracker://... so when the authentication is successful, the 
browser should cause Android to open the app. again on the upload screen. 
That's not working on your device, probably due to HTC customs either in the 
browser, or in the way the registration of the URL happens.

I'm afraid there's not much I can do, especially without having access to this 
device model. This is a well known problem of Android fragmentation 
unfortunately, especially with phone makers and carriers adding their own 
software layer on top of Android. I already had a similar problem with the 
camera app. (See issue #11), already with HTC devices...

Original comment by nicolas@guillaumin.me on 8 Sep 2013 at 8:16

• Changed state: WontFix

[GoogleCodeExporter]

Yes, HTC Sense has a known issue with app association changins. That's probably 
why you cannot register custom protocol handler.

But can you suggest us any workarounds?
Can this token be added to the app settings manually?

Original comment by mkuzmin on 28 Sep 2013 at 6:56