This object is in archive!
Samsung Chromebook connecting to Google Drive Error
Answered
Anybody have an idea why I can't connect to my google drive through Locus on a Samsung Chromebook? I can connect to drobpbox without any issues and I can connect to google drive on my phone app. But when I try to connect on the Chromebook I get a Verizon search page pops up with a "Sorry, We could not find oauth.callback.com" error.
The same question
Good day Stephen,
in case you see this "oauth.callback.com" error, this should mean that your browser that Locus Map use for login, is not able to correctly process whole login procedure.
What I may suggest to try is to install for example Chrome web browser and try to login over this browser.
Let me know if this helped.
Good day Stephen,
in case you see this "oauth.callback.com" error, this should mean that your browser that Locus Map use for login, is not able to correctly process whole login procedure.
What I may suggest to try is to install for example Chrome web browser and try to login over this browser.
Let me know if this helped.
Considering that this is a Chromebook, I was under the impression that I was using Chrome as a browser, but I will check and report back. Thanks for the response.
Considering that this is a Chromebook, I was under the impression that I was using Chrome as a browser, but I will check and report back. Thanks for the response.
Perhaps I don't understand, but I just reviewed all the installed apps and all I have is Chrome. I also checked my settings and confirmed that google is set as the default search engine.
So here is what is happening:
> Open the locus app on the Chromebook
> Import data
> Select google drive as the source, which shows a log in is required. I click the log in button
> That opens a new tab in Chrome and the message reads "choose and account to continue to callback.com"
> I select my google account, which opens a new page asking for permission for "callback.com to view and manage my files in google drive". I select "allow".
> that launches a page at this address (but the page never loads):
http://oauth.callback.com/callback/googleEx?code=4/KJZ9pAakLOn6VHTiaVqr7lVfi-CXF_I2jPtuddNRc1c#
Then I get a new page with an error: "Sorry, We could not find oauth.callback.com"
http://searchassist.verizon.com/main?ParticipantID=euekiz39ksg8nwp7iqj2fp5wzfwi5q76&FailedURI=http%3A%2F%2Foauth.callback.com%2Fcallback%2FgoogleEx%3Fcode%3D4%252FKJZ9pAakLOn6VHTiaVqr7lVfi-CXF_I2jPtuddNRc1c&FailureMode=1&Implementation=&AddInType=4&Version=pywr1.0&ClientLocation=us
Make any sense?
Perhaps I don't understand, but I just reviewed all the installed apps and all I have is Chrome. I also checked my settings and confirmed that google is set as the default search engine.
So here is what is happening:
> Open the locus app on the Chromebook
> Import data
> Select google drive as the source, which shows a log in is required. I click the log in button
> That opens a new tab in Chrome and the message reads "choose and account to continue to callback.com"
> I select my google account, which opens a new page asking for permission for "callback.com to view and manage my files in google drive". I select "allow".
> that launches a page at this address (but the page never loads):
http://oauth.callback.com/callback/googleEx?code=4/KJZ9pAakLOn6VHTiaVqr7lVfi-CXF_I2jPtuddNRc1c#
Then I get a new page with an error: "Sorry, We could not find oauth.callback.com"
http://searchassist.verizon.com/main?ParticipantID=euekiz39ksg8nwp7iqj2fp5wzfwi5q76&FailedURI=http%3A%2F%2Foauth.callback.com%2Fcallback%2FgoogleEx%3Fcode%3D4%252FKJZ9pAakLOn6VHTiaVqr7lVfi-CXF_I2jPtuddNRc1c&FailureMode=1&Implementation=&AddInType=4&Version=pywr1.0&ClientLocation=us
Make any sense?
Good day Stephen,
steps you describe are perfectly correct. What happen in your device are correct except last step. In this case, your web browser should redirect this url to Locus Map application. Instead it tries to open it in own window, which is a problem.
Anyway we were just working on it with a colleague and I think we have a solution. Please check this functionality in next Locus Map version and let us know. Thank you.
Good day Stephen,
steps you describe are perfectly correct. What happen in your device are correct except last step. In this case, your web browser should redirect this url to Locus Map application. Instead it tries to open it in own window, which is a problem.
Anyway we were just working on it with a colleague and I think we have a solution. Please check this functionality in next Locus Map version and let us know. Thank you.
In case anyone has the same problem, the latest update corrected the issue. Thanks!
In case anyone has the same problem, the latest update corrected the issue. Thanks!
Thanks Stephen for a confirmation. Glad to read it!
Thanks Stephen for a confirmation. Glad to read it!
Replies have been locked on this page!