![]() Once saved you can now add the associated client_id value to the manifest. You can then configure a project in the Google Cloud Console with a new OAuth Client ID (Chrome App) and link to the web store URL with the Item ID. You will also find the public key in the Package section of the uploaded item this will be the key value in the manifest. Once it is uploaded (it can remain a draft), it will create an Item ID within the web store. But I want to save this file not on my personal Drive account, but in the Drive of the current user, the user who uses the chrome extension (if this user has a Drive account, of course). Here is a more in depth walkthrough in order to get OAuth working within a Chrome Extension:Įssentially you need to upload your extension as a draft in the Chrome Developer Dashboard. Now, I want to send this 'file' (I will/would build a 'file' with the dictionary entries) to Google Drive and use this file in my Android app. As long as you use your Google account in the extension you shouldn't need to go through the verification process. I would also make sure to configure your consent screen to add Google Drive which will be a sensitive permission. This can then be added to the manifest.json. ![]() The article then states you need to remove the packed extension and load your unpacked dev extension.įor the client_id you need to create a new OAuth Client ID (Web Application) and add a redirect URI in the following structure:
0 Comments
Leave a Reply. |