ayoola-solomon / mytracks

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

Cannot upload to Fusion Tables #646

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Long-click on track > select "Send to Google..." > check "Google Fusion 
Tables"
2. Click Send now

What is the expected output? What do you see instead?
I expect the progress bar to go to 100% and the track to appear as a new Fusion 
Tables.  Instead, progress goes to 5%, pauses briefly, and a Success dialog is 
shown saying the track was uploaded to google.com/fusiontables.  But it wasnt.

What version of MyTracks are you using? On what version of Android? On what 
phone?
1.1.11
Android: 2.3.4 on HTC Sensation

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

11-21 23:06:04.301: E/MyTracks(15935): Exception
11-21 23:06:04.301: E/MyTracks(15935): java.io.IOException: Received 
authentication challenge is null
11-21 23:06:04.301: E/MyTracks(15935):  at 
org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.pro
cessAuthHeader(HttpURLConnectionImpl.java:1153)
11-21 23:06:04.301: E/MyTracks(15935):  at 
org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.pro
cessResponseHeaders(HttpURLConnectionImpl.java:1095)
11-21 23:06:04.301: E/MyTracks(15935):  at 
org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.ret
rieveResponse(HttpURLConnectionImpl.java:1048)
11-21 23:06:04.301: E/MyTracks(15935):  at 
org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.get
ResponseCode(HttpURLConnectionImpl.java:726)
11-21 23:06:04.301: E/MyTracks(15935):  at 
org.apache.harmony.luni.internal.net.www.protocol.https.HttpsURLConnectionImpl.g
etResponseCode(HttpsURLConnectionImpl.java:121)
11-21 23:06:04.301: E/MyTracks(15935):  at com.google.a.a.a.b.c.<init>(MT:37)
11-21 23:06:04.301: E/MyTracks(15935):  at com.google.a.a.a.b.b.a(MT:83)
11-21 23:06:04.301: E/MyTracks(15935):  at com.google.a.a.a.u.a(MT:689)
11-21 23:06:04.301: E/MyTracks(15935):  at 
com.google.android.apps.mytracks.io.e.a(MT:1)
11-21 23:06:04.301: E/MyTracks(15935):  at 
com.google.android.apps.mytracks.io.b.c.a(MT:164)
11-21 23:06:04.301: E/MyTracks(15935):  at 
com.google.android.apps.mytracks.io.s.b(MT:669)
11-21 23:06:04.301: E/MyTracks(15935):  at 
com.google.android.apps.mytracks.io.s.run(MT:149)
11-21 23:06:04.301: E/MyTracks(15935):  at 
java.lang.Thread.run(Thread.java:1027)

Please provide any additional information here:

Original issue reported on code.google.com by johnwi...@gmail.com on 22 Nov 2011 at 7:18

GoogleCodeExporter commented 9 years ago
Here is an unobfuscated stack trace:

12-07 12:56:37.985: E/MyTracks(22553): java.io.IOException: Received 
authentication challenge is null
12-07 12:56:37.985: E/MyTracks(22553):  at 
org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.pro
cessAuthHeader(HttpURLConnectionImpl.java:1153)
12-07 12:56:37.985: E/MyTracks(22553):  at 
org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.pro
cessResponseHeaders(HttpURLConnectionImpl.java:1095)
12-07 12:56:37.985: E/MyTracks(22553):  at 
org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.ret
rieveResponse(HttpURLConnectionImpl.java:1048)
12-07 12:56:37.985: E/MyTracks(22553):  at 
org.apache.harmony.luni.internal.net.www.protocol.http.HttpURLConnectionImpl.get
ResponseCode(HttpURLConnectionImpl.java:726)
12-07 12:56:37.985: E/MyTracks(22553):  at 
org.apache.harmony.luni.internal.net.www.protocol.https.HttpsURLConnectionImpl.g
etResponseCode(HttpsURLConnectionImpl.java:121)
12-07 12:56:37.985: E/MyTracks(22553):  at 
com.google.api.client.http.javanet.NetHttpResponse.<init>(NetHttpResponse.java:3
7)
12-07 12:56:37.985: E/MyTracks(22553):  at 
com.google.api.client.http.javanet.NetHttpRequest.execute(NetHttpRequest.java:83
)
12-07 12:56:37.985: E/MyTracks(22553):  at 
com.google.api.client.http.HttpRequest.execute(HttpRequest.java:689)
12-07 12:56:37.985: E/MyTracks(22553):  at 
com.google.android.apps.mytracks.io.SendToFusionTables$2.query(SendToFusionTable
s.java:688)
12-07 12:56:37.985: E/MyTracks(22553):  at 
com.google.android.apps.mytracks.io.SendToFusionTables$2.query(SendToFusionTable
s.java:1)
12-07 12:56:37.985: E/MyTracks(22553):  at 
com.google.android.apps.mytracks.io.gdata.GDataWrapper.runOne(GDataWrapper.java:
200)
12-07 12:56:37.985: E/MyTracks(22553):  at 
com.google.android.apps.mytracks.io.gdata.GDataWrapper.runCommon(GDataWrapper.ja
va:173)
12-07 12:56:37.985: E/MyTracks(22553):  at 
com.google.android.apps.mytracks.io.gdata.GDataWrapper.runQuery(GDataWrapper.jav
a:164)
12-07 12:56:37.985: E/MyTracks(22553):  at 
com.google.android.apps.mytracks.io.SendToFusionTables.runUpdate(SendToFusionTab
les.java:665)
12-07 12:56:37.985: E/MyTracks(22553):  at 
com.google.android.apps.mytracks.io.SendToFusionTables.createNewTable(SendToFusi
onTables.java:237)
12-07 12:56:37.985: E/MyTracks(22553):  at 
com.google.android.apps.mytracks.io.SendToFusionTables.doUpload(SendToFusionTabl
es.java:193)
12-07 12:56:37.985: E/MyTracks(22553):  at 
com.google.android.apps.mytracks.io.SendToFusionTables.run(SendToFusionTables.ja
va:150)
12-07 12:56:37.985: E/MyTracks(22553):  at 
java.lang.Thread.run(Thread.java:1019)

Original comment by jshih@google.com on 7 Dec 2011 at 9:09

GoogleCodeExporter commented 9 years ago
Rodrigo, I will assign this issue to you for now. Please also check why when 
sending to Fusion Tables fails, the callback still returns success=true.

Original comment by jshih@google.com on 9 Dec 2011 at 11:51

GoogleCodeExporter commented 9 years ago
Investigating.

Original comment by rdama...@google.com on 13 Dec 2011 at 11:35

GoogleCodeExporter commented 9 years ago
With the same gmail account, I am able to upload to Fusion Tables on one phone, 
but not on another. As discussed, the most likely cause is that we are not 
refreshing the auth token once it has expired.

Original comment by jshih@google.com on 16 Dec 2011 at 2:32

GoogleCodeExporter commented 9 years ago
Merging with issue 312 - the stack traces are not the exact same, but the 
problems look very similar.

Original comment by rdama...@google.com on 2 Jan 2012 at 7:28