can't sign-in with stock browser on android

[tracywalker]

With Android 2.2 stock browser at beta.myfavoritebeer.org, click sign-in

a cert message comes up, click continue.

then I get "We are very sorry, there has been an error" "to retry...

[jrgm]

After the cert message, Tracy, is there also a link the "there has been an error" with See more info?

Does that, when you reveal it, say "action: establishing relay. Relay frame could not be found".

What is the exact URL that you are hitting at diresworb.org (if you are in the popup).

[tonychung]

I can reproduce this error on the following devices:

• Iphone iOS5 , safari
• Samsung Galaxy S 2, Android 2.3.3, Stock browser

bumping priority up to 5. this is a shipblocker for mobile devices using stock browser.

Error mentions: "Relay frame could not be found"

screenshot: http://i.imgur.com/i6z7F.png

Logcat from Android phone:
12-05 15:34:13.880: DEBUG/FastDormancy(2842): before ======= ENTER DORMANCY =======
12-05 15:34:13.880: DEBUG/FastDormancy(2842): [FD] ON default: true
12-05 15:34:13.880: DEBUG/FastDormancy(2842): Before mDormFlag: false in getCapaDormancy()
12-05 15:34:13.880: DEBUG/FastDormancy(2842): After mDormFlag: false in getCapaDormancy()
12-05 15:34:13.980: VERBOSE/browser(17100): BrowserActivity.onPageFinished: url = https://diresworb.org/sign_in#9KT4nK2vwebview = android.webkit.WebView@40559318
12-05 15:34:13.985: VERBOSE/browser(17100): BrowserActivity.onProgressChanged: progress == 100 truefalsetruefalse
12-05 15:34:14.485: DEBUG/BookmarkAppWidgetProvider(17100): getBitmap query count=1
12-05 15:34:14.650: DEBUG/BookmarkAppWidgetProvider(17100): setBookmark success=true
12-05 15:34:14.650: DEBUG/BookmarkAppWidgetProvider(17100): getBitmap query count=1
12-05 15:34:14.660: DEBUG/BookmarkAppWidgetProvider(17100): getBitmap query count=1

[jbonacci]

I could not duplicate this on an Android 2.3.4 with stock browser. But, in this case, the "default" browser was set to the stock browser.

I could not duplicate this with iOS5.

So, let's use this Issue to focus on "older" Android devices running stock browser with and without the default browser set to stock browser (if that makes sense).

[jbonacci]

For the above, go to Settings > Manage Applications > Web (or whatever name they give the Stock browser).
Clear data
Clear cache
Clear defaults

Go to beta.myfavoritebeer.org
You will see a security warning - hit "Continue"
Try to sign in
Should see the Relay Frame error.

Now, try again, but select Stock browser as the default browser.
Clear Cache
Clear Data
Go to beta.myfavoritebeer.org
Select stock browser as the default browser
You will see a security warning - hit "Continue"
Try to sign in
Select stock browser as the default browser (if prompt comes up again)
Error comes up again.

Now repeat the steps in Production:
First case fails for me
Second case passes

So, the original bug has changed a bit, but it looks like the workaround still "works" in Production:
if Stock browser, is the default browser, everything seems to work OK.

[jbonacci]

And to go a bit further...

1. After setting Stock browser to my default browser
2. After getting this working on Prod
3. I go back to Stage and everything seems OK

[shane-tomlinson]

@tonychung - this appears to be a duplicate of #596 which we said (which I confirmed yesterday with @benadida - see #596 (comment)) we are not going to resolve yet. There is a workaround - setting a default browser as @jbonacci has pointed out.

[jbonacci]

Yea, this is almost exactly 596, with some edge cases thrown in for various Android device/firmware version peculiarities.
I think in most cases the setting of the default browser will cover this issue (preferably to FF!).
I think most Android users will long ago have set their default browser to Stock, or FF, or Opera, etc.
This can be a SUMO doc for now until we have a long-term fix.
I don't think this is more than a 3 star.

[jbonacci]

Leaving this Issue open since 1. it has more current information and 2. #596 is already closed.

[jbonacci]

Adding comments that could be broken out into two more Issues:

I am finding now that if I sign in then logout, I can no longer sign in again.
The Sign In "pop-up" just flashes then disappears.
This is stock browser on Android 2.2 phone using Stage.
Duplicated as well using stock browser on Android 3.2 tablet.
In both cases, this is stock browser as the default browser.
Duplicated in Prod with Android + stock browser.
I can not duplicate this using FF or Opera on the same devices.
Workaround: Instead of hitting SignIn after logout, refresh the page first, then hit SignIn.

Click SignIn
Enter an email and password
Either cancel out or click This is not me
Again, I can no longer Sign In
The "pop-up" appears then disappears with a flash.
Can duplicate on two Android devices against Stage and Prod.
Can not duplicate this with FF or Opera.

This issue (or these 3 issues) probably needs to be a 5-star because it is getting to be "too much work" for the user to use BrowserID on Android.

[lloyd]

please re-test this issue on dev.diresworb.org or dev.myfavoritebeer.org. I don't think this one is solved with the new window communication implementation that landed tonight, but it's worth a test.

[jbonacci]

Well, COOL!
Something sure fixed the problems in my comment above!
(#708 (comment))

Whatever you did, let's get it moved over to Stage because this is basically a blocker for using the stock browser + older firmware with BrowserID.

[martinrevert]

Working smoothly in Android 2.3.7 with stock browser, but having the exact problems of description trying to use this implementation of BrowserID:

https://github.com/jrburke/idme

I don't know what to expect: Could be an implementation problem of that solution or you guys think that I have to wait for this changes to get that solution productive?

thanks!

[jrburke]

@martinrevert the idme experiment does use a fork of the browserid code, and so the flow is a bit different. I'll follow up with you in this idme issue

[jbonacci]

OK. So needs to be retested on Stage for the next train.

[jbonacci]

So, trying again on an Android 2.2 device with NO default browser set (which gets us back to the original issue):
So, I cleared out the stock browser settings so it was no longer the default browser.
I was able to bring up and Sign In to diresworb.org.

Moving over to beta.myfavoritebeer.org:
This is still a fail

I get the same error message:
"We are very sorry, ...etc...."

The "See more info" link shows the following:
Action: Establishing Relay
Relay frame could not be found.

So the workaround for older Android devices is to either

1. Set the stock browser to the default browser
2. Use a different browser, like FireFox, for doing anything related to BrowserID

Long-term, we need to fix the "older" Android issue.

[jbonacci]

In my previous comment, I said I got this to work on Dev, but my guess was I forgot to clear out the browser settings first.

REF: #708 (comment)

[jbonacci]

FYI: 20110124 maintenance window
Includes the following fixes:
Bug 720478 - add "cross root" intermediate to production *.s.m.c, *.browserid.org certificates
Bug 710338 - Upgrade browserid.org SSL cert to EV or crazypants good level

Once this is deployed, we should be able to use Android 2.2 for signing into BID w/o setting default browser.
And, we should no longer see the Cert warning.

[jbonacci]

OK, we are getting close on the Cert Warning part, but...
https://bugzilla.mozilla.org/show_bug.cgi?id=720860

But still Frame Relay errors all around...

[jbonacci]

This seems to have regressed. More work tomorrow...

[jbonacci]

Closing now that this works for the base case of 3 or less emails in an account, stock browser set as default browser.
Bug 720860 is tracking the cert warning issue separately...

[jbonacci]

I am now able to select from 3+ emails on beta.myfavoritebeer.org using stock browser (not as default) on Android 2.2.