Is still possible to use auto-generated Firebase domains as OAuth Consent Screen Authorized Domains?

[robbi73]

I submit the OAuth consent screen verification for an extension of mine that use calendar.readonly scope.

It is an unlisted extension since it is only used by co-workers within the organization and all endpoints are related to an intranet that is not accessible from the world outside.

I also want to point out that the extension doesn't profit me a cent.

Unfortunately I don't have a registered personal domain, but I only use free web space provided by one of the many providers, so I get "Comply with domain verification requirements. Ensure your application's domains have completed the Search Console verification process"

I read this thread and I'm here to ask you if it is (still) possible to use a domain generated by Firebase.

If the answer is yes, is there a video or documentation that explains the procedure in detail?

I would like to save the money needed to register (and keep registered) a personal TLD domain.

Do I have any chance?

Thank you

[Marramirez]

Hi @robbi73,

Welcome to the Google Cloud Community!

Using a domain generated by Firebase means that you will be utilizing Firebase Hosting. By default, every Firebase project has subdomains at no cost on the web.app and firebaseapp.com domains. These two sites serve the same deployed content and configuration.

To get started with Firebase Hosting, take a look at this documentation.

Let me know if it helped, thanks!