Browser extension cannot log in (new!) #33

New Issue

fergalmoran · 2025-08-09T16:55:44Z

fergalmoran commented

2025-08-09 16:55:44 +00:00

Originally created by @GoogleCodeExporter on 1/3/2016

While this results in the same outcome as issue 319, it appears to be a very 
different issue, with different symptoms and to which the same workaround does 
not apply.

What steps will reproduce the problem?
1.Install the extension succesfully (No problems)
2.Click the Extension icon and select log in.
3.Click "Allow access"
4.Get redirected to about:blank, and the extension is still not logged in.

What is the expected output? What do you see instead?
The extension should have logged in, it has not.
The OAuth authorization page has a warning on the top: "We are unable to verify 
the name associated with this application because it runs on your computer, as 
opposed to on a website. We recommend you do not allow access unless you trust 
the application". 
Fixing the system time (as is suggested in issue 319) does not help. It's sad 
to notice that the unofficial FoxToPhone extension for Firefox, which uses the 
same service back end, works flawlessly instead.

I am using extension version 2.3.2 on Chrome 31 beta on Windows 7 x64.

Original issue reported on code.google.com by andreazz...@gmail.com on 3 Nov 2013 at 3:12

*Originally created by @GoogleCodeExporter on 1/3/2016* ``` While this results in the same outcome as issue 319, it appears to be a very different issue, with different symptoms and to which the same workaround does not apply. What steps will reproduce the problem? 1.Install the extension succesfully (No problems) 2.Click the Extension icon and select log in. 3.Click "Allow access" 4.Get redirected to about:blank, and the extension is still not logged in. What is the expected output? What do you see instead? The extension should have logged in, it has not. The OAuth authorization page has a warning on the top: "We are unable to verify the name associated with this application because it runs on your computer, as opposed to on a website. We recommend you do not allow access unless you trust the application". Fixing the system time (as is suggested in issue 319) does not help. It's sad to notice that the unofficial FoxToPhone extension for Firefox, which uses the same service back end, works flawlessly instead. I am using extension version 2.3.2 on Chrome 31 beta on Windows 7 x64. ``` Original issue reported on code.google.com by `andreazz...@gmail.com` on 3 Nov 2013 at 3:12

fergalmoran closed this issue

2025-08-09 16:55:44 +00:00

Sign in to join this conversation.

No Label auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: fergalmoran/chrometophone#33