You cannot switch to an Apps Script-created Cloud Platform project.

[Alan Wells]

I recognize the error:

"You cannot switch to an Apps Script-created Cloud Platform project."

I've spent a lot of time on this problem.

You got the Project ID of the Cloud Platform project, and tried to associate the Apps Script project with a Cloud Platform project.

But the Cloud Platform project was originally created as a default Apps Script created Cloud Project.

Somewhere in the documentation I think that it states that you can't see Apps Script created Cloud Projects,

but you can.  It depends on the circumstances.

There is no "built-in" way to convert an Apps Script created Cloud Platform project to a "standard" default project.

This lack of capability prevented me from recovering from a catastrophe.

In my case I had originally published an add-on from a free/consumer account a long time ago in the Chrome Web Store.

So, I could manage the add-on and see and manage the Apps Script created Cloud Platform project, but it was still a default project.

I don't know what your situation is, or what you ultimately want to do.

I have spent a lot of time trying investigating some possible way to convert a default Cloud Platform Project to a standard project.

There is no way to do it.

Someone at Google would need to specially go into their database and covert it for you.

If the Cloud Platform project is the basis for a GSuite Marketplace listing, then you can't delete the Cloud Platform project or you'd loose your GSuite Marketplace listing and all the users and rating associated with it.

So, it's a bad situation to be in.

[Steve Webster]

Hi Alan.

This reminds me of this documentation:

https://developers.google.com/apps-script/guides/cloud-platform-projects#switch_to_a_different_standard_gcp_project

Google Cloud Platform Projects

Every Apps Script project uses the Google Cloud Platform to manage authorization, Advanced services, and other details. To configure and manage these settings, every Apps Script project has an associated Google Cloud Platform project (a GCP project). Your script project can use a default GCP project that is created automatically by Apps Script, or the script project can use a standard GCP project that you create yourself. In general, default GCP projects are good for everyday or simple scripts, but you should use a standard GCP project for any application that is complex, commercial quality, or is intended for publication.

You can switch a script project to use a standard GCP project at any time, but you can't switch back to use a default project. It's best to select the GCP project your script uses early in development, as switching later can cause complications, such as requiring your users to re-authorize.

Kind Regards,

Steve Webster

SW gApps LLC, President 

GDE (Google Developer Expert)

Google Product Expert in: Google Apps Script, Drive, and Docs 

Google Vendor (2012-2013) || Google Apps Developer Blog Guest Blogger 

Add-ons: Text gBlaster 

--
You received this message because you are subscribed to the Google Groups "Google Apps Script Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-script-c...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/ab8cdb27-9682-4a53-9559-398e35b024f5n%40googlegroups.com.

[Alan Wells]

That documentation and that advice didn't exist when I first published my add-on.

By the time that documentation was published, my add-on already had users and reputation.

And there was/is no way to convert to a standard GCP project for an add-on published with a default GCP project.

Of course, now it is not possible to publish an add-on without it being associated with a standard GCP project.

The predicament that I was in can't happen anymore, because it's not allowed.

That documentation is telling us to not do something that (for add-ons) isn't allowed anymore.

So, the message is, "Don't do something that you now can't do, and if you did it before, then you're screwed.  So sorry.  It's not our fault."