search

anongit / mytracks

Automatically exported from code.google.com/p/mytracks
0 stars 0 forks source link

unable to upload maps. stuck at authentication when hl = ZH-cn #255

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.using the send option within "send to google" in the main menu
2.
3.

What is the expected output? What do you see instead?
Stuck at "Authenticating to Google Maps" window. Can still return to the main 
menu using back button though.

What version of MyTracks are you using? On what version of Android? On what
phone?
MyTracks:1.0.21
Android Version 2.2
Htc Desire

If possible please provide a log.  Either upload here or send to mytracks-
support@google.com.
Detailed instructions can be found here:
http://code.google.com/p/mytracks/wiki/HowToReportErrors

Please provide any additional information here:
Log sent via mail

Original issue reported on code.google.com by angeli...@gmail.com on 2 Jan 2011 at 2:41

GoogleCodeExporter commented 8 years ago 
same problem for me.
Galaxy S and Android 2.2

Original comment by Damien.T...@gmail.com on 22 Jan 2011 at 10:53

GoogleCodeExporter commented 8 years ago 
Looks like Google is changing the map api making upload not functioning. 
Something about fusion table...

Original comment by angeli...@gmail.com on 22 Jan 2011 at 2:36

GoogleCodeExporter commented 8 years ago 
I looked through the log but I could not find anything of use.

Original comment by sandordo...@google.com on 25 Feb 2011 at 2:43

GoogleCodeExporter commented 8 years ago 
Turns out it's a language/locale issue. The default language of my HTC Desire 
is Chinese. Upload feature works once I switch the language to English.

Original comment by angeli...@gmail.com on 25 Feb 2011 at 5:05

GoogleCodeExporter commented 8 years ago 
Odd. So this reliably fails with zh-cn?

Original comment by sandordo...@google.com on 25 Feb 2011 at 5:56

GoogleCodeExporter commented 8 years ago 
Looks like it. My friend with his new HTC desire HD suffers the same issue. 
Switching to English works for him too.

Original comment by angeli...@gmail.com on 25 Feb 2011 at 6:00

GoogleCodeExporter commented 8 years ago 
Very odd but that should be resolvable.

Original comment by sandordo...@google.com on 25 Feb 2011 at 6:14

GoogleCodeExporter commented 8 years ago

Original comment by rdama...@google.com on 30 Apr 2011 at 6:12

GoogleCodeExporter commented 8 years ago 
I'm having the same problem.  Everything is set to English though (I'm in 
Australia).  This is on a Galaxy S2.

Original comment by simon...@gmail.com on 6 May 2011 at 10:19

GoogleCodeExporter commented 8 years ago 
Same problem here. When language=Finnish, upload doesn't work. When it's 
English, it works.

Android 2.2 Froyo on Samsung Galaxy Mini GT-S5570, MyTracks ver. 1.1.4

I've attached a log if it's any use.

Original comment by okram1...@gmail.com on 7 May 2011 at 9:14

Attachments:

GoogleCodeExporter commented 8 years ago 
Same issue here, brand new Galaxy S II from the UK (I am in Australia). 
Everything is set to English to the best of my knowledge.

Original comment by Chester....@gmail.com on 10 May 2011 at 8:55

GoogleCodeExporter commented 8 years ago 
The reason for it seems to be this (taken from the above logcat):

05-07 23:43:27.736 D/MyTracks(16393): Logging in to local...
05-07 23:43:27.746 E/JavaBinder(  176): *** Uncaught remote exception!  
(Exceptions are not yet supported across processes.)
05-07 23:43:27.746 E/JavaBinder(  176): 
java.lang.StringIndexOutOfBoundsException
05-07 23:43:27.746 E/JavaBinder(  176):         at 
java.lang.String.substring(String.java:1579)
05-07 23:43:27.746 E/JavaBinder(  176):         at 
android.accounts.AccountManagerService.createNoCredentialsPermissionNotification
(AccountManagerService.java:906)
05-07 23:43:27.746 E/JavaBinder(  176):         at 
android.accounts.AccountManagerService.doNotification(AccountManagerService.java
:1759)
05-07 23:43:27.746 E/JavaBinder(  176):         at 
android.accounts.AccountManagerService.access$300(AccountManagerService.java:79)
05-07 23:43:27.746 E/JavaBinder(  176):         at 
android.accounts.AccountManagerService$1.onResult(AccountManagerService.java:879
)
05-07 23:43:27.746 E/JavaBinder(  176):         at 
android.accounts.AccountManagerService$1.onResult(AccountManagerService.java:861
)
05-07 23:43:27.746 E/JavaBinder(  176):         at 
android.accounts.IAccountAuthenticatorResponse$Stub.onTransact(IAccountAuthentic
atorResponse.java:59)
05-07 23:43:27.746 E/JavaBinder(  176):         at 
android.os.Binder.execTransact(Binder.java:288)
05-07 23:43:27.746 E/JavaBinder(  176):         at 
dalvik.system.NativeStart.run(Native Method)

Same thing happens to me (Samsung Galaxy S II)

Original comment by diesg...@gmail.com on 15 May 2011 at 12:53

GoogleCodeExporter commented 8 years ago 
Same issue here. Samsung Galaxy S II with android 2.3.3 and my tracks version 
1.1.4

Set the language to English (UK or American) doesn't matter, still stuck at 
this bloody authenticating screen. 

Any advice?

Original comment by olofmola...@gmail.com on 18 May 2011 at 6:54

GoogleCodeExporter commented 8 years ago 
http://forum.xda-developers.com/showthread.php?t=1075971

I have posted about this issue on XDA forums. It affects many different apps 
with the Samsung Galaxy S 2.

Original comment by jamesmgi...@gmail.com on 19 May 2011 at 8:19

GoogleCodeExporter commented 8 years ago 
For anyone wondering, at this stage this issue appears to be a Samsung issue - 
see http://groups.google.com/group/mytracks/msg/7d4cf52faf61a473 and discussion 
at http://groups.google.com/group/mytracks/browse_thread/thread/3d01a1b9f2223fb0

Original comment by Chester....@gmail.com on 30 May 2011 at 12:59

GoogleCodeExporter commented 8 years ago 
Issue 482 has been merged into this issue.

Original comment by sandordo...@google.com on 10 Jun 2011 at 3:37

GoogleCodeExporter commented 8 years ago 
I had this issue too (Samsung Galaxy S2, running 2.3.3, XWKE7)

Settings > Language and Keyboard > Select Language

Had been set to English (United Kingdom), after changing to English (United 
States) it worked (I got asked a series of questions about permissions). 

Unfortunately New Zealand English is based on UK, not US, so I imagine this is 
going to cause spell checker frustration.

Actually, having changed it back, it looks like the "Send to Google" 
functionality still works.

Perhaps you only need to choose English US the first time?

Original comment by j.cou...@gmail.com on 10 Jun 2011 at 5:01

GoogleCodeExporter commented 8 years ago 
I have a fresh install of my tracks on this Samsung Galaxy Mini. 'Send to 
Google' started working after I changed language to US English. After the first 
upload, I changed the language back to Finnish; lo and behold: I could upload a 
a second track to Google.

Original comment by kon...@gmail.com on 15 Jun 2011 at 5:36

GoogleCodeExporter commented 8 years ago 
Unable to upload even with US English language. Samsung Galaxy S2 - XXKDJ.

Original comment by covaxi on 15 Jun 2011 at 9:06

GoogleCodeExporter commented 8 years ago 
I can't upload with Samsung S2. I use English (UK), changed it to English (USA) 
but still no luck. I tried GPS on and off and made no difference.

Original comment by fortress...@gmail.com on 19 Jun 2011 at 5:04

GoogleCodeExporter commented 8 years ago 
The upload wasn't working for me.  I changed to US English, got past 
authentication, but fail to upload.  I repeated 2 time and finally worked ok.  
I then changed back to UK English and it still works.

Original comment by ian.bart...@gmail.com on 20 Jun 2011 at 11:24

GoogleCodeExporter commented 8 years ago 
Galaxy SII and same issue.  Tried switching to US english but that did not 
resolve the issue.  It did work for the first track that I uploaded.  Then a 
week later recorded another track and this time it is also stuck at the 
authentication and this goes all the other tracks as well (imported gpx files).

Original comment by sven.br...@gmail.com on 23 Jun 2011 at 12:18

GoogleCodeExporter commented 8 years ago 
The same here : Galaxy s2 changing  from italian to english  but doesn't work

Original comment by principe...@gmail.com on 28 Jun 2011 at 9:48

GoogleCodeExporter commented 8 years ago 
Same issue - Galaxy S2

Original comment by simon.hu...@gmail.com on 8 Jul 2011 at 8:38

GoogleCodeExporter commented 8 years ago 
Same issue - Samsung Galaxy S2

Original comment by egm...@maringka.net on 9 Jul 2011 at 10:16

GoogleCodeExporter commented 8 years ago 
Same issue.

MyTracks:1.1.7
Android Version 2.3.3
Samsung Galaxy S2

Original comment by egm...@maringka.net on 9 Jul 2011 at 10:19

GoogleCodeExporter commented 8 years ago 
Still the same problem!  
Why can't this been fixed....  it's a problem for serveral months now....???

Are there any other apps that i can use??

Also SGS II.

Original comment by verke...@gmail.com on 11 Jul 2011 at 11:18

GoogleCodeExporter commented 8 years ago 
I have the same problem with Samsung Galaxy Ace, language RU_ru.

Original comment by Ruslan.L...@gmail.com on 11 Jul 2011 at 3:00

GoogleCodeExporter commented 8 years ago 
Same problem, also i have an Samsung Galaxy S 2...

Original comment by elandu...@gmail.com on 12 Jul 2011 at 9:04

GoogleCodeExporter commented 8 years ago 
Same error here. I had this error from time to time... but It always worked 
after trying.

Right now, after an update to Android 2.3.3 (HTC Desire Z), there is NO way I 
can upload a track to maps/docs...

adg logcat shows...:

W/GoogleLoginService( 1610): Status 200, but response didn't include auth token
E/MyTracks(18989): IOException
E/MyTracks(18989): java.io.IOException
E/MyTracks(18989):  at 
android.accounts.AccountManager.convertErrorToException(AccountManager.java:1422
)
E/MyTracks(18989):  at 
android.accounts.AccountManager.access$400(AccountManager.java:138)
E/MyTracks(18989):  at 
android.accounts.AccountManager$AmsTask$Response.onError(AccountManager.java:128
3)
E/MyTracks(18989):  at 
android.accounts.IAccountManagerResponse$Stub.onTransact(IAccountManagerResponse
.java:69)
E/MyTracks(18989):  at android.os.Binder.execTransact(Binder.java:320)
E/MyTracks(18989):  at dalvik.system.NativeStart.run(Native Method)

Original comment by ivanicl...@gmail.com on 15 Jul 2011 at 7:34

GoogleCodeExporter commented 8 years ago 
Same issue with Samsung Galaxy S2; changed langauge to English (United States); 
uploaded successfully; changed language back to English (United Kingdom) and it 
still uploads without a problem.

Original comment by seanchen...@gmail.com on 17 Jul 2011 at 7:42

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
SG S2 - switched to English (US) didn't help... stopt while autentification to 
google 0% (0/100)

Original comment by t.kirst...@googlemail.com on 18 Jul 2011 at 7:33

GoogleCodeExporter commented 8 years ago 
Well it's been just the same issue here - stopping at 0/100

Original comment by fab...@gebert-hh.de on 18 Jul 2011 at 8:56

GoogleCodeExporter commented 8 years ago 
Same here. SGSII

Original comment by mar...@badanka.com on 20 Jul 2011 at 3:58

GoogleCodeExporter commented 8 years ago 
I'm hoping this has been fixed in the latest (yet unreleased) version - can 
someone test the attached APK and report whether the issue is still there? If 
not I'll try to work on it before the next release.
(notice this version has other unrelated bugs which we still need to fix before 
releasing)

Original comment by rdama...@google.com on 20 Jul 2011 at 8:50

GoogleCodeExporter commented 8 years ago 
And "Back" button do not remove progress bar now.

Original comment by covaxi on 21 Jul 2011 at 2:01

Attachments:

GoogleCodeExporter commented 8 years ago 
Here's error log from ddms, don't know, if it helps:
07-21 18:03:47.515: ERROR/JavaBinder(2691): *** Uncaught remote exception!  
(Exceptions are not yet supported across processes.)
07-21 18:03:47.515: ERROR/JavaBinder(2691): 
java.lang.StringIndexOutOfBoundsException
07-21 18:03:47.515: ERROR/JavaBinder(2691):     at 
java.lang.String.substring(String.java:1651)
07-21 18:03:47.515: ERROR/JavaBinder(2691):     at 
android.accounts.AccountManagerService.createNoCredentialsPermissionNotification
(AccountManagerService.java:944)
07-21 18:03:47.515: ERROR/JavaBinder(2691):     at 
android.accounts.AccountManagerService.doNotification(AccountManagerService.java
:1803)
07-21 18:03:47.515: ERROR/JavaBinder(2691):     at 
android.accounts.AccountManagerService.access$300(AccountManagerService.java:79)
07-21 18:03:47.515: ERROR/JavaBinder(2691):     at 
android.accounts.AccountManagerService$2.onResult(AccountManagerService.java:917
)
07-21 18:03:47.515: ERROR/JavaBinder(2691):     at 
android.accounts.AccountManagerService$2.onResult(AccountManagerService.java:899
)
07-21 18:03:47.515: ERROR/JavaBinder(2691):     at 
android.accounts.IAccountAuthenticatorResponse$Stub.onTransact(IAccountAuthentic
atorResponse.java:59)
07-21 18:03:47.515: ERROR/JavaBinder(2691):     at 
android.os.Binder.execTransact(Binder.java:320)
07-21 18:03:47.515: ERROR/JavaBinder(2691):     at 
dalvik.system.NativeStart.run(Native Method) 

P.S. Samsung Galaxy SII

Original comment by covaxi on 21 Jul 2011 at 2:08

GoogleCodeExporter commented 8 years ago 
The back button didn't work before either - it'd remove the UI, but would keep 
sending in the background (however in a non-safe way, meaning it could get 
killed by Android in the middle of the sending). I disabled the back button to 
make the UI consistent with the fact that we never had cancellation implemented.

Thanks for the log, however that's still a bug/translation mistake by Samsung, 
which we can't do much about. I found a suggested workaround which I'm going to 
try, but since i don't have one of the affected phones, it's hard to test 
directly. I'll post a new APK soon. In the mean time please check that your 
phones have the latest updates from the manufacturer.

For my own reference:
http://forum.xda-developers.com/showthread.php?p=15155487

Original comment by rdama...@google.com on 22 Jul 2011 at 10:33

GoogleCodeExporter commented 8 years ago 
Users: please try this new APK.

Sandor, please review:
http://code.google.com/r/rdamazio-mytracks-staging2/source/detail?r=0a27d37e5be3
f334394182d0846bd6b968d71e52

http://code.google.com/r/rdamazio-mytracks-staging2/source/detail?r=3751e9dcf7c0
2408d7a4ccd30d70986c7218b177

Original comment by rdama...@google.com on 23 Jul 2011 at 12:17

GoogleCodeExporter commented 8 years ago 
Oops, forgot to attach the APK.

Original comment by rdama...@google.com on 23 Jul 2011 at 12:20

Attachments:

GoogleCodeExporter commented 8 years ago 
Woo-hoo! This one works for me. Asked for maps/fusion/docs permissions and 
uploaded ok.

Original comment by covaxi on 23 Jul 2011 at 10:01

GoogleCodeExporter commented 8 years ago 
It works online my SGS2 too. Great Work.

Original comment by ch.mitte...@gmail.com on 23 Jul 2011 at 10:12

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Issue solved on my Galaxy S2 with this new APK, thx !

Original comment by sankar.g...@gmail.com on 25 Jul 2011 at 11:49

GoogleCodeExporter commented 8 years ago 
Thanks for the new app,  after installing this app it works fine!

Original comment by verke...@gmail.com on 25 Jul 2011 at 1:07

GoogleCodeExporter commented 8 years ago 
Glad to hear :) I'm trying to finish a few more bug fixes and then we'll make 
an official release. Also doing some more testing of these changes on 1.5 and 
1.6.

Original comment by rdama...@google.com on 26 Jul 2011 at 12:56

GoogleCodeExporter commented 8 years ago 
Just a tiny fix for cupcake/donut, please review:
http://code.google.com/r/rdamazio-mytracks-staging2/source/detail?r=ccfa7c7024be
82c7627dc6dc62130f4b9219e95c

And while you're doing that, please also take a look at this smaller unrelated 
change which I found while testing on cupcake:
http://code.google.com/r/rdamazio-mytracks-staging2/source/detail?r=dd449a36ac4c
e1ba9eb8583b5385797daea4c20d

Original comment by rdama...@google.com on 1 Aug 2011 at 5:52

GoogleCodeExporter commented 8 years ago

Original comment by rdama...@google.com on 1 Aug 2011 at 7:54

GoogleCodeExporter commented 8 years ago 
I had same problem. Now Its fix by APK up there ;) Thankx!

Original comment by hectoram...@gmail.com on 14 Aug 2011 at 12:43