CODEWITHSUNDEEP
google-chromegoogle-chrome-extensionoauthgoogle-developers-console
Soham Kumbhar
Soham Kumbhar

Reputation: 1

Created a Chrome extension, but I am unable to publish my OAuth

Recently, I created and published my Chrome extension, but to make OAuth work for everyone, I need to change its status from "Test" to "Public." However, it is asking for an Application Home Page and an Application Privacy Policy Link.

I tried using GitHub Pages for the links, but it is not accepting them. Additionally, I cannot use the chrome://extensions link.

The verification error I am receiving states: "Your homepage and privacy policy should not be hosted on a third-party platform where you cannot verify ownership of your subdomain. Examples include Google Sites, Facebook, Instagram, Twitter, GitHub, etc."

How can I resolve this issue?

Attaching images for reference: What should I input in this fields? Getting this issue

I tried using GitHub Pages for the links, but it is not accepting them. Additionally, I cannot use the chrome://extensions link as this are considered as third party domains.

Upvotes: 0

Views: 19

Answers (1)

Lukas
Lukas

Reputation: 335

You should buy a domain that matches your company, your publisher name, or albeit your own personal site as long as it matches the publisher details on the extension page.

Then you will need to create and host both Terms of Service and Privacy Policy on those pages. This will get you approved.

I am not sure but you could be able to get by with something like Netlify Pages where you get a subdomain under their domain. However that is a pure guess.

A good rule of thumb is to verify the domain using Google Search Console (this is a prerequisite) and then pick as the official domain for the extension. This will get you there. This will also speed up your reviews down the road by a margin.

Upvotes: 0

Related Questions