Doesn't work with 3G internet

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install with Wifi on
2. use the app
3. Turn off Wifi
4. Use the app

What is the expected output? What do you see instead?
Link sent to the cloud over 3G

What version of the product are you using? On what operating system?
Chrome dev under Win7

What handset are you using? What version of Android is it running?
Last release under Android 2.2

Have you rooted or installed a variation or mod of Android on your phone?
No

If you don't mind sharing, what username are you using? What server?
username = email, server = default one

Please provide any additional information below.

Original issue reported on code.google.com by regis.ca...@gmail.com on 16 Aug 2010 at 5:10

[GoogleCodeExporter]

This is interesting. I rarely have wifi on on my test phone, and seem to be 
able to send over 3G just fine. Are you sure your 3G has coverage? Are other 
internet apps loading correctly?

Are you getting any kind of error message?

Original comment by foran.pa...@gmail.com on 17 Aug 2010 at 10:39

• Changed state: Investigating

[GoogleCodeExporter]

Hello, 

Yes I'm sure my phone is connected. Just retested for the exact error and I get 
a "Please report this: Expectation failed". My test protocol is: 
- open a link in browser (Dolphin HD)
- Menu > Plus > Share page > android2cloud
=> small notification showing the error.

Original comment by regis.ca...@gmail.com on 18 Aug 2010 at 4:43

[GoogleCodeExporter]

Hmm. And you say that the app works for you, as expected, under WiFi? Could you 
remove and add your account again? Long press the account in the account list 
to delete, and choose "New Account" to add an account.

The "Expectation failed" error message occurs when the server's expectations 
for authentication aren't met. The app doesn't differentiate between WiFi and 
EDGE/3G data at all.

Original comment by foran.pa...@gmail.com on 23 Aug 2010 at 6:35

[GoogleCodeExporter]

Original comment by foran.pa...@gmail.com on 23 Aug 2010 at 6:35

• Added labels: Component-OAuth, OS-Android

[GoogleCodeExporter]

I just tried removing my account and then adding it back again and still got 
the "Expectation failed".

Original comment by regis.ca...@gmail.com on 23 Aug 2010 at 6:13

[GoogleCodeExporter]

Would you mind sharing the username you're using, and the server you're using? 
I'm sorry, this is extremely odd.

Original comment by foran.pa...@gmail.com on 24 Aug 2010 at 1:34

[GoogleCodeExporter]

No, I'm using regis DOT caspar AT gmail DOT com and the default server.

Original comment by regis.ca...@gmail.com on 24 Aug 2010 at 5:01

[GoogleCodeExporter]

Do you know how to retrieve the logcat debugging information? I'm sorry, I'm 
looking all over on this end, and can't seem to figure out what's causing the 
problem.

Original comment by foran.pa...@gmail.com on 24 Aug 2010 at 5:40

[GoogleCodeExporter]

No, I don't but if you provide me some directions, I can provide debug info.

Original comment by regis.ca...@gmail.com on 24 Aug 2010 at 5:41

[GoogleCodeExporter]

If you search the Market for "Bug Reporter", by Robot Media, it should do the 
trick. Just download it (it's free), and run android2cloud until it gives you 
the error. After, immediately run Bug Reporter, check the box to include system 
logs, and hit OK. Choose "GMail", and send it to paddy at android2cloud dot org.

Thanks. Sorry for the rigamarole.

Original comment by foran.pa...@gmail.com on 24 Aug 2010 at 5:55

[GoogleCodeExporter]

You should have it. Thanks for the directions and for taking care of this bug.

Original comment by regis.ca...@gmail.com on 24 Aug 2010 at 6:07

[GoogleCodeExporter]

I got it, but there wasn't a single log entry from android2cloud in there. 
Which is extremely suspicious.

I'm really sorry to do this to you, but would you be willing to download a 
special version of the 0.3.1 beta build that will record some useful 
information (the server you're using, the oauth parameters being passed, and 
other non-identifying information), and then sending the report after trying 
it? I'm really sorry this is such an issue- I have no idea whatsoever how 
you're running into these errors. I can clearly see you have used the app 
successfully before, which means you aren't just setting up an account wrong or 
something.

Original comment by foran.pa...@gmail.com on 24 Aug 2010 at 6:18

[GoogleCodeExporter]

OK, I will try that during the day (I have to go right now) and keep you posted 
with the result.

Original comment by regis.ca...@gmail.com on 24 Aug 2010 at 6:21

[GoogleCodeExporter]

Can you send me the special beta by mail (or a link to it) ?

Original comment by regis.ca...@gmail.com on 24 Aug 2010 at 6:22

[GoogleCodeExporter]

I'll make myself a note and send you to it in the morning. Unfortunately, it's 
2:23 a.m. here, and I have work in the morning. So I need to call it a night, 
and can't make and test the modifications needed before sleeping. If you can 
hang tight, I'll have them for you tomorrow. I apologise. I really appreciate 
how much help you're offering in tracking down this bug.

Original comment by foran.pa...@gmail.com on 24 Aug 2010 at 6:24

[GoogleCodeExporter]

Thanks, I also appreciate the effort you put in this bug.
Have a good night and see you tomorrow (your) for the next part.

Original comment by regis.ca...@gmail.com on 24 Aug 2010 at 6:44

[GoogleCodeExporter]

http://dl.dropbox.com/u/6777769/android2cloud.apk

There's the newest beta, with the logging code included. You'll notice some new 
features, and maybe it will make your problem go away. :) If it doesn't, I'd 
love the Bug Reporter feedback from it.

Original comment by foran.pa...@gmail.com on 25 Aug 2010 at 5:56

[GoogleCodeExporter]

Same exception but much more info in the bug report. I sent it to you as 
yesterday.

Original comment by regis.ca...@gmail.com on 25 Aug 2010 at 6:20

[GoogleCodeExporter]

This is beyond annoying. I'm looking at your log, and it all looks good to me. 
The URLs are right, the data is all there...

With your permission, I'd like to try and spoof your account, using the token 
and secret from your log, to see if I can replicate the error. If I can send 
links using your token and secret, then I don't know what I'll do.

Please, let me know if this is an acceptable solution for you. If it is, I 
would suggest you disable the extension, so you don't see a bunch of test links 
popping up at random times.

Original comment by foran.pa...@gmail.com on 25 Aug 2010 at 11:15

[GoogleCodeExporter]

Ok, extension disabled, you can do your tests.

Original comment by regis.ca...@gmail.com on 26 Aug 2010 at 4:42

[GoogleCodeExporter]

I must admit I'm stumped on this one. I've spoofed your account exactly-- I 
used your exact login credentials, used the same software, the same server, and 
it worked fine for me from my Nexus One, the only test device I have. I tried 
on WiFi and on 3G, and was able to send a link from both without any issues 
whatsoever. I even tried using and not using Silent Sending, to see if that 
could be the issue. No dice.

I'm going to have to defer to a higher authority on this one. I'll ask on both 
the Signpost (the OAuth library android2cloud utilises) mailing list and on the 
App Engine mailing lists, and see if I can't figure out what the issue is.

I'm really sorry. Thank you for being so awesome about this.

Original comment by foran.pa...@gmail.com on 6 Sep 2010 at 4:41

[GoogleCodeExporter]

Hi, thanks for taking time to look what's wrong. Maybe this is some kind of 
filtering from my phone provider. Let's see what the higher authority thinks. 
Regards, 

Régis

Original comment by regis.ca...@gmail.com on 6 Sep 2010 at 4:50

[GoogleCodeExporter]

If I may ask, what phone provider are you using? I'll take a look around and 
see if I can find anyone else having these issues.

Original comment by foran.pa...@gmail.com on 6 Sep 2010 at 5:05

[GoogleCodeExporter]

I'm using Orange in France.

Original comment by regis.ca...@gmail.com on 6 Sep 2010 at 5:06

[GoogleCodeExporter]

Alright, thanks a lot. :)

Original comment by foran.pa...@gmail.com on 6 Sep 2010 at 5:08

[GoogleCodeExporter]

Got it! I used android SDK debugger to find out if some patch I saw here 
(http://groups.google.com/group/signpost-users/browse_thread/thread/f6b1d753c90c
fd90/8013dde67d31c624?lnk=gst&q=Expectation#8013dde67d31c624) was working and 
it does. Enclosed you will find a patch against current sources.

Regards, 

Régis.

Original comment by regis.ca...@gmail.com on 6 Sep 2010 at 6:53

Attachments:

• patch

[GoogleCodeExporter]

You win the award for Most Awesome User Of The Week. I've added the patch to 
the source repository, and will submit it to beta testers in the next iteration 
of the app, which should be coming out in the next week or two, pending any 
disasters.

I've also listed you in the Project Contributors section of the site. Thanks so 
much for your time, patience, and ultimately skill in resolving this issue. I'm 
sure plenty of users down the line will be thankful for your efforts.

Original comment by foran.pa...@gmail.com on 6 Sep 2010 at 7:08

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by foran.pa...@gmail.com on 6 Sep 2010 at 7:08

• Changed state: InBeta

[GoogleCodeExporter]

Thanks (you indeed show me the way when mentioning Signpost)

Régis.

Original comment by regis.ca...@gmail.com on 6 Sep 2010 at 7:15

[GoogleCodeExporter]

Just cleaning up issues and labels.

Original comment by foran.pa...@gmail.com on 7 Sep 2010 at 7:07

• Removed labels: Priority-Medium

[GoogleCodeExporter]

Fixed in version 2.0

Original comment by foran.pa...@gmail.com on 2 Jan 2011 at 7:42

[GoogleCodeExporter]

Original comment by foran.pa...@gmail.com on 2 Jan 2011 at 7:42

• Changed state: Fixed