Error while sending track to Google Fusion Tables with Version 23 - Authentication Issue?

[GoogleCodeExporter]

What steps will reproduce the problem?

Start phone
Launch My Tracks
Send Track to Tables

What is the expected output? What do you see instead?

Expect to see success message instead see dialog box titled "Success" with the 
text: There was an error while sending your track to Google Fusion Tables.  
Please try again Later. (OK button below)

What version of MyTracks are you using? On what version of Android? On what
phone?

MyTracks version 23 (from Application Info in settings)
2.1-update1
Motorola CLIQ (MB200)

More detail on phone:

MB200
Blur_Version.2.2.5
2.1-update1
2.6.29
ERD79 

If possible please provide a log.  

I will email it, here are some highlights:

MyTracks: com.google.wireless.gdata.client.HttpException: Received 403 status 
code: Maps Data api is now deprecated.

MyTracks: java.lang.NoSuchMethodError: 
android.net.http.AndroidHttpClient.newInstance

MyTracks: com.google.wireless.gdata.client.HttpException: Received 403 status 
code: authentication required

Please provide any additional information here:

Trying again leads to same error.  I have uploaded some tables, so it does work 
sometimes.  Great application, thank you.  I updated the application today 
prior to these tests.  I think the problem might be related to the login 
process for my Google account, it appears the app thinks I am logged in but I 
might not be?  Also, the one time it worked it asked my permission to 
authenticate with Google, but when it doesn't work it doesn't ask.  Hope that 
helps.  I can provide more logs if that is useful.

Original issue reported on code.google.com by tantdy...@gmail.com on 11 Feb 2011 at 12:14

[GoogleCodeExporter]

I may have discovered the problem.  It appears I have internet connectivity but 
that my DNS is not working properly, this happens on this particular phone 
because I have hit the 247 system property limit (this is not a rooted phone, 
the filling up is just a motoblur peculiarity) and when connection switches 
from WiFi to Network or vice versa things go haywire because the DNS value can 
not be set (no more headroom for properties).  It does appear your error 
dialogs could be more specific like "Error" "Could not authenticate due to 
network failure" instead of the "Success" message I see now.  If you see 
anything in the logs that validate this please say so.

Original comment by tantdy...@gmail.com on 11 Feb 2011 at 12:27

[GoogleCodeExporter]

We got the service restored.

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

• Changed state: Fixed