search

brtrbr / gtm-oauth2

Automatically exported from code.google.com/p/gtm-oauth2
0 stars 0 forks source link

When hitting "Allow access" too fast, iOS gives "Javascript is disabled" error messsage #11

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
--
After entering your username & password, Google gives you the standard "Blah 
blah app is requesting permission to..." screen. If you hit the "Allow access" 
button before that page has enough time to load all of its JS assets, you will 
invariably get the following error:

"You've reached this page because we have detected that Javascript is disabled 
in your browser. The page you attempted to load cannot display properly if 
scripts are disabled."
(This screen is black & white and has no Google branding on it.)

You can time this event by hitting "Allow access" before the application's icon 
(just above the button) loads. If you wait until the icon loads (that is, 
presumably, when the JS files loads), you won't get this error message and 
everything will work just fine.

What is the expected output? What do you see instead?
--
User should not have to wait for JS files to load before completing auth. 

What version of the product are you using? On what operating system?
--
svn commit #96 via gdata-objective-client on both iOS 5.1 and IOS 6. I've seen 
it with apps currently available in the App Store (Asana, for example) as well 
as on the simulator (Xcode 4.5.1 on Mountain Lion).

Please provide any additional information below.
-- 
It's probably not something in the gtm-oauth2 library so much as it is the web 
backend where gtm-oauth points to, but I wasn't sure where else to report it. 
If someone points me in the right direction I can re-post this issue.

Original issue reported on code.google.com by arthur.n...@gmail.com on 25 Oct 2012 at 11:52

GoogleCodeExporter commented 9 years ago 
Looks like it has been fixed. It seems the server team has made the "Allow 
access" button disabled until all JS assets load. This effectively resolves the 
problem.

Original comment by arthur.n...@gmail.com on 12 Nov 2012 at 10:38

GoogleCodeExporter commented 9 years ago

Original comment by grobb...@google.com on 9 Apr 2013 at 9:16