We developed an extension and published like a private app for the testing purposes before publishing to the webstore by choosing the option Private.
We followed the steps under this link
https://support.google.com/chrome/a/answer/2663860?hl=en
Now I log into webstore with my account and can't see that under "Your apps" section. Is there anyway we can trouble shoot?
How long does it take to show up under users accounts?
Related
I can't find my Google Chrome extension in the Chrome Web Store. I have publish them 2 Weeks ago in private mode. The extension issn't for public.
I can't really make sense of the Google documents. In those it sounds like you can find the extension in the webstore as a trusted tester or member of an added google group.
But I can't find it. Only the direkt Link works.
I’m developing a chrome extension and would like to make it a paid extension with a free trial. I uploaded my item onto the Developer dashboard and saved it as a draft, not submitting it yet. But on my Developer dashboard I don’t see an option to set the type of payment (free trial) or to set a price. Under Pricing & Distribution it says ‘Pricing and payment information can only be added in the old dashboard’ but there’s no option there either. My goal is to set a price and check if a user has paid when the trial has expired.
Steps I have taken:
I have paid $5 in Google payments center and under Account in my
Developer dashboard it says fee has been paid
I added at the long key in my manifest.json, taken from the .pem I
created by packing the extension (not using the crx in any way,
just to get a key). I can upload a new item without any errors so
the key seems to be working.
On Google Cloud Platform I created a project with the exact same name
and enabled the Chrome Web Store API. I generated a OAuth 2.0
Client id - using my app name and 32 digit id generated by the
developer dashboard - which I’ve added in my manifest.json
My manifest key and oauth2 now looks like:
"key": "MIIBIjANB…...",
"oauth2": {
"client_id": "19…...apps.googleusercontent.com",
"scopes": [
"https://www.googleapis.com/auth/chromewebstore.readonly"
]
}
I added this in my background.ts:
chrome.identity.getAuthToken({ 'interactive': true }, (token) => {
console.log('token: ', token);
});
It already seems to be working showing me a Google window prompting to ‘Choose an account to continue to ’ and that my extension ‘wants to access your Google Account’ and can ‘View your Chrome Web Store apps and extensions’, and returning a token.
My questions are:
Why don’t I see an option to select Free trial and set a price?
In Google payments center I have two id’s, should my id here be the same as the first 12 digits of my client id by any chance (cos it isn’t)?
Do I need to go through the process of creating an OAuth consent screen? In my project in Google Cloud Platform I now have that client id but it also says ‘To protect you and your users, your consent screen and application need to be verified by Google’ and creating the screen it requires ‘Authorized domains’, ‘Application Homepage link’ and ‘Application Privacy Policy link’. Is this really necessary for an extension, which doesn’t have a homepage?
Turns out this feature has been disabled due to Covid-19.
"Chrome Web Store payments - We are disabling the ability to create new paid items or add payments to existing items. This includes extensions, themes, apps, and in-app purchases."
https://groups.google.com/a/chromium.org/g/chromium-extensions/c/r5EKL-McE3A/m/epeWeh-wAQAJ
I'm working with actions on google and dialogflow, and recently they proposed google signin to make account linking fast without writing own oauth server.
Today I implemented their google signin in my dialogflow app it is working quite fine but unfortunately I am unable to delete that account to check all development aspects, I tried my other google accounts and my friends account but soon ended up out of accounts
Un other methods when i enable and disable testing it forget about linking but in google signin it is tightly stick with the account, and i have tried almost everything i can try like restarting my phone and clearing cache of chrome browser but it looks like it is saving account somewhere in cloud.
What i need to do is, when i sign in first time it ask for name permission, i need that screen again and again for testing something
Google calls this Removing a Website or App that has access to your account. It is done using the myaccount.google.com console.
If you want to do this using Android, the easiest way is to:
Open your device's Settings app Settings app and then Google and then Google Account.
At the top, tap Security.
Under "Signing in to other sites," tap Signing in with Google.
Tap the name of your project.
Choose Remove access.
Through the web, you can go to Apps With Access to your Accounts:
Scroll down to the "Signing in with Google" section
Locate your project.
Select it, and choose "Remove access"
The name that is shown should be the name you've given to your project as part of the OAuth screen. If you haven't set that up (and if you're just playing around, you probably haven't), it will use the Project ID for your project. You can find this on the Cloud Console home screen attached to the same project name that you used in Dialogflow and the Action Console.
While you're in there, you will probably want to configure the OAuth screen to have a name for the app as it will be visible to users on the OAuth screen. From the menu, select "APIs & Services" and then "Credentials"
Select the "OAuth consent screen" tab, and fill in the "Application name".
This name should then be in the list of applications you have installed, and can remove.
Trying to follow this intro to user authentication using OAuth 2.0 in a Chrome Extension I am developing. https://developer.chrome.com/apps/app_identity
But I can't follow it (missing information).
Add permissions and upload app
You need to make sure the identity permission is in your manifest. You can
then upload your app to the apps and extensions management page (see Publish).
This step is fine. I have uploaded my project and it is in the developer dashboard.
Copy key to your manifest
When you register your application in the Google OAuth console, you'll provide your application's ID, which will be checked during token requests. Therefore it's important to have a consistent application ID during development.
To keep your application ID constant, you need to copy the key in the installed manifest.json to your source manifest. It's not the most graceful task, but here's how it goes:
1.Go to your user data directory. Example on MacOs: ~/Library/Application\ Support/Google/Chrome/Default/Extensions
2.List the installed apps and extensions and match your app ID on the apps and extensions management page to the same ID here.
3.Go to the installed app directory (this will be a version within the app ID).
4.Open the installed manifest.json (pico is a quick way to open the file).
5.Copy the "key" in the installed manifest.json and paste it into your app's source manifest file.
Except, straight away, at step 1, I cannot progress. My app is not installed and therefore its ID does not appear in the user data directory.
Will installing the unpacked extension work? Well it doesn't appear in Default/Extensions directory so I guess not. Besides, it has been given a different ID than my dashboard instance.
Therefore, where do I get the key? There is a key associated with my app on the developer dashboard. But this "tutorial" doesn't mention that.
Is somebody able to explain what I should be doing such as pointing me to another resource to learn how to set up a basic user authentication for a Chrome App?
After uploading, from the developer dashboard you can click on the "More Info" on the right of your extension in the dashboard.
You will see several pieces of useful data:
item id - this is the extension id
public key - this is the "key" you want. Copy everything between (not including) the "BEGIN PUBLIC KEY" and "END PUBLIC KEY" markers, and paste it into a "key" property in your manifest.json
Here's one way to solve this:
In the Chrome Developer Dashboard, edit your current project.
Scroll down and click Preview Changes
Click the Share icon button next to Add To Chrome which is grayed out.
E-mail the link to yourself.
Follow the link to your app's store page and now you should be able to click Add To Chrome. It will then be installed on your system under [profile]/Extensions.
I've done plenty of searching and I can't find ANY information about having multiple developers working on a Chrome extension.
Basically, I just want to grant another developer access to manage my Chrome extension in the Chrome Developers Dashboard. (ie so that it is listed in their Chrome developer Dashboard and they can publish it/change the logo etc).
EDIT 6 Aug 2013 - The Group Publishing feature allows organisations to create a group such that the extensions can be managed by multiple developers. For more info, see Group Publishing.
Old answer
An extension in the Chrome Web Store can be managed by only one Google account.
If you want to have multiple developers manage the extension, create a Google account for your company, pay 5$ to get the right to publish and share the credentials within the company.
If you want to transfer ownership of an extension to another account, fill in this form.
Assets (screenshots) are usually not updated very often. On the other hand, it's common to update the extension's source code and description, so letting the main developer manage the extension listing makes sense.