Closed kaidatavis closed 6 years ago
This is happening because the URL from the Client where the Login appears mismatches with the URL left in the Google+ API 0Auth credidentials page.
For users that have this Issue :
What I have done for now:
What I require:
Why this is happening:
Will this happen when the Extension is on the web store ?
I logged into the google api console and added a new redirect url https://leidmgckldmkjgonkcmpdcpmkmkapbal.chromiumapp.org/src/background/background.html (the one shown by 'redirectURI'), but the same error message remains. Is this because google api takes some time to update?
Is this because google api takes some time to update?
It took some hours for me once.
Did any of you moved or renamed Background.HTML or HistoryMap.HTML ?
Just tried again and still have the same error message.
I just came home from work, working on this now
I have created a new 'historymap' extension in the chrome web store: https://chrome.google.com/webstore/detail/historymap/jjgdemkolpjjdkgmfgolldlnoghhodlj I tried to add the redirect uri with the new extension ID in the api console, but still have the same error: https://lajblbdkejaddpihfeeihnicfkmiojem.chromiumapp.org/src/background/backgroud.html
What account did you use for the extension ? can you give me access so I can try setting up Oauth credentials ?
I am working on this right now
Just got it to work, committing now.
I updated Hello.js and I also fixed the issue with the login.
For anyone else reading this and working on the login heres a handy wiki page I made :)
https://github.com/Vis4Sense/HistoryMap/wiki/SenseMap-Login-on-a-Local-Environment
I also made a video tutorial https://www.youtube.com/watch?v=CU4TIDmKJgk&feature=youtu.be
This could be related to the permission that Reday has to set in his google developer console for each new machine because the extension is not registered in chrome app store.