When I implement a new project or update automatically the DataStudio settings in the manifest are deleted.
Does anyone know why this happens?
This seems to be an issue related to Apps Script's new editor.
I suggest you open an issue on Google's Issue Tracker here.
A workaround for this is to switch to the old editor.
+1 I've been having the exact same issue with new UI. I keep switching back to the legacy UI and reverting the Manifests version back.
I think some update must have happened on the backend to cause this but I'm not sure what. Will start using the legacy UI to deploy for now.
In the meantime I've opened this issue with the google issue tracker you linked above
https://issuetracker.google.com/issues/194244611
I have published an external Google Spreadsheets addon, and everything worked so far. Since a couple of days, within the "Google Cloud Platform > APIs & Services > G Suite Marketplace SDK > Configuration panel" the input field for "Sheets add-on script version" is empty and an error message "At least one extension must be enabled and selected extensions must be configured" is displayed.
I have already tried the following steps:
Insert the current published script version number and click "Save changes"
Insert a new script version number and click number and click "Save changes"
The response is the following:
Error Sorry, there’s a problem. If you entered information, check it
and try again. Otherwise, the problem might clear up on its own, so
check back later.
Tracking Number: 7178656512110690803
Send feedback
The problem did not clear up so far and also the Google Support team did not reply to my feedback/message so far.
Due to this behaviour I am not able to publish new versions.
It is a new bug. Please star the issue on Issue Tracker for updates.
I work in the G Suite Marketplace. This issue has been fixed and it will roll out to production between today and tomorrow.
I'm working through the quick-start for a Gmail Addon.
https://developers.google.com/gmail/add-ons/guides/quickstart
When I try to Install my developer addon I
Open the Gmail add-on settings tab
In the Add-ons tab, make sure that you have selected the Enable developer add-ons for my account checkbox
However there is no checkbox...
Is this edition limited? Do we need to do something else to enable this?
Thanks for your help,
Paul C
Apparently there is a bug for GSuite admins and they cannot see that button or add addons right now.
Try your personal gmail for now.
There is an issue open with Gmail https://issuetracker.google.com/issues/68234732
I have contacted the Gsuite team, will update the answer once I have something solid.
Update (Dec 19, 2018)
Looks like this issue has been fixed, I could get it working on Corporate and Personal email.
According to this recent G Suite Developers Blog post, installing developer add-ons has now been enabled for users of G Suite.
And indeed, when I go to 'Settings' -> 'Add-ons' in my G Suite account, I do now see the 'Enable developer add-ons for my account' checkbox.
However, when I click this and enter my script's deployment id, I always get the same error message: 'Invalid Add-on'.
I would be interested to hear if anyone has got this working or not?
Edit 02/02/2018:
Further to the above and following communication with Google Support, apparently it looks like a setting in our G Suite Admin was causing the problem.
We managed to fix it by following the instructions here, making sure to select 'Allow users to install any application from G Suite Marketplace': https://support.google.com/a/answer/6089179?hl=en
It's a bit counter intuitive that a setting involving the Marketplace should affect our developer plugin that we hadn't yet put on the Marketplace, but in any case, after an hour or so our developer plug-in started to function.
Obviously it also is not ideal having to allow any app to be installed from the App Marketplace. Hopefully Google will put a more permanent solution in place soon.
I am attempting to publish a simple Google Docs add-on, following these instructions: Publishing an Add-on
However when completing the configuration for Google Apps Marketplace SDK, I enter my script project key (found from file --> project properties) and receive the following error: 'Project Key is not associated with the current project.'
Only instance where I can find someone with the same problem (here) occurred when they created a project on the Google Developers Console instead of going through resources --> Advanced Google Services. This is not the reason for my error, can anyone shred any light onto my problem?
Any help would be gratefully received,
Connor
Kept trying, did not change the way I tried publishing nor the project key I was entering and it worked after so many retries. Wish I could give a more detailed answer...
I was able to fix by combining two successful responses from this post:
use version number, and only the number, e.g. "1" -- Do not use "v1.0" or "Version 1 on Oct 1, 6:10 AM" or your deployment's Description
After completing step 1, delete your entry in field 'Docs Add-On Project Script ID', then re-enter it -- the page seems to not re-evaluate your changes unless you do this; I had tried saving multiple times before doing this with no success using the correct version number and script ID.
For me I need to go Publish->Deploy as API. Select the correct version and then the publish screen worked
I needed to include a correct version number (1,2,3,4; not "v0.1") in addition to the script ID. The error suggested my script ID was wrong, but the error went away when I picked a valid version number.
For me, the Google App Script file needed to be associated with the project.
In the GAS, go to Resources > Cloud Platform Project.
Under Change Project, enter the project number (which can be found on the home page of the Google Cloud Platform Project in the Project info module), and click Set Project.
Confirm the notices (though make sure that is really what you want to do).
Once it has been set, go back to the App Configuration, and re-enter the information (if you are already on that page, refresh).
That's what worked for me, but maybe other developers get that error for other reasons.
Source: https://developers.google.com/apps-script/guides/cloud-platform-projects#switching_to_a_different_standard_gcp_project
Hmm I had issues as well. It didn't work with version 1 in "Docs Add-on script version" but while I tried a bunch of stuff I ended up deploying again and then I incremented version to "2" and then it worked.
I got the same error today, I made it finally work. I will go through the fields I checked.
App Integration [I'm deploying using deployment ID, you can get the ID from AppScript manage deployment]
Choose which workspace you are releasing [In my case Sheets], type the version from AppScript.
Enter all other general Credentials and save.
The above steps worked for me.
Try to use the Google Workspace Add On and enter the App Script Deployment ID. That accepted for me and showed it as a Sheets Add-On
It's different in deploy or test in legacy editor and new editor.
And I'm using legacy editor before
(because some following steps from documents is not work in new editor),
So when I lookup Mange deployment in new editor,
It wasn't exisisted,
And the deployment ID it's not work when I fill out App configuration in Google Workspace Market.
For me I just change to following the Legacy editor's following steps
https://developers.google.com/workspace/marketplace/enable-configure-sdk#legacy-editor_2
and It works.
Looks like it is not possible to change scriptId after a round of review. So you can just update only version. I changed to last number of deployment version like '6' and it is saved.
In the newly published version of my app that is using Google Maps Android API V2, I've implemented all the things suggested by the developer guides to ensure the user has GooglePlayServices installed, and it has been working well on all the devices I own and the several hundred people that have updated to the new version of the app so far.
Today I received a bug report via acra with a strange error. This is happening on the following line of code, after setupMapIfNeeded() has completed:
mMap.setMyLocationEnabled(true);
Logcat reports:
W/GooglePlayServicesUtil(10401): Google Play Store is missing.
Shouldn't the call to GooglePlayServicesUtil.isGooglePlayServicesAvailable() also ensure that the Play Store is installed? That seems like a huge oversight on Google's part if it doesn't.
Any help is appreciated.
In case someone came here by accident or was just wondering why it was not working...
This could happen when user had old Android Market installed, which was replaced by Google Play Store.
Here is relevant issue: http://code.google.com/p/gmaps-api-issues/issues/detail?id=4862 (fixed in february update).