I have a functioning Google Sheets Add-on that is listed in the Google Workspace Marketplace. I've made changes in the new Apps Script Editor and tested them locally, now I want to push them to my users.
The process as I understand it, to press "New Deployment"
add a description and press "deploy"
after which I copy the "Deployment ID" into the Google Workspace Marketplace SDK page,
and hit SAVE in the bottom.
It's been a few hours and I still cannot see it being live.
Is there a review process for updates like this? Or am I missing a step?
The previous version is still being served to users as far as I can tell.
Update in response to the comment from #ziganotschka
I am making a Google Sheets Editor Addon, and I'm only now understanding the difference between that and the Google Workspace Addon. I've resubmitted my store listing for review with Google Workspace Addon disabled, and removed the "Common" part of my manifest. I've updated the "version" number to correspond to the latest deployment.
Is it not possible to test a Sheets Editor Addon from the new editor without deploying it as a Workspace Addon? And should updating the version number be sufficient to roll out an update?
From the question
Is it not possible to test a Sheets Editor Addon from the new editor without deploying it as a Workspace Addon?
It depends on what kind of test do you want to do, if your Apps Script project is bounded or a standalone project and what do you Editor add-on does and how it does that.
I.E. you might test a simple edit trigger (onEdit) by using a function for mocking the edit event object and passing it to the onEdit function. To be clear this doesn't need to create a new version and for testing and add-on it's not necessary to make a new deployment.
And should updating the version number be sufficient to roll out an update?
It depends on if the Cloud project OAuth consent screen was set for external use or for internal use, in the new version requires new scopes.
Let say that you fixed typo on a variable name, in this case only creating a new version and adding the version number to the add-on configuration page will be enough, but if you added a sensitive API and you add-on is set for external use, then you will have to update the OAuth consent screen and wait for Google review and approval.
Related
we've got an app that's not on the market yet and we are struggling with the testing version that testers download. We're trying to set the v1.0.1 but Google Play redirects them to v1.0.0 which is not up to date. We even tried to deactivate that branch but the issue still insists.
I do a lot of test deployments for multiple test groups.
Google supports 3 separate types of test groups: Open, Closed, Internal.
Open Testing is literally open to anyone who wants to opt in and they can join via a link you can copy from the developer console. Open testing requires the app go thru review before being rolled out.
Closed Testing is similar to Open but you explicitly define who has access with a list of email addresses. Closed testing must also pass through a basic Google review before being rolled out.
Internal Testing is similar to Closed testing but it never goes through a review process. Again, this is controlled via a list of email addresses.
I routinely publish different versions where Internal has the latest bleeding edge.
You don't state which channel you are using (Open, Closed, Internal), but I would carefully review each channel and the email addresses associated. Then I would click on the Publishing Overview button on the console to see if there's something you haven't finished.
I am testing WSO2-Emm system for managing our android mobile app. We have an app for taxi drivers. We deploy it using our tablets and a single gmail account. Our problem is that google allows up to 10 signed in devices for a single google account.
I have tried to load the apk to the WSO2 store. The problem is that when I want to upload a new version of the same app I get a warning message saying that this APK already exists in the store. When I try to rename it and add it as a new apk it works. The problem is that when I go to App-Management, the application appears under 'installed'. The Emm system doesn't detect there is a new version.
To be more specific, my question is is there a way to manage mobile application versions using the WSO2 store and not the google play store.
If there is a way we can go on with this system. If not, we will stop testing it.
The only way I've figured out how update an already installed app is by going to the App Management tab, selecting your latest version of the app in question, and hitting the install button under the Roles tab (NOT the Users tab). It will send the install command to any devices listed under roles you have checked, even if they already have the app installed. Keep in mind this will install the app on all the devices, even devices that already have the version you're trying to put out.
It looks like you already know about the patch on EMM-686 that must be implemented in order to upload multiple versions of the same app to the Publisher. Just in case you want to confirm it's implemented correctly, see my answer here for instructions on how to implement it.
For a Google Apps Script that I am working on, I need to enable Google URL Shortener API and Google Drive API.
The trouble comes when I create a copy of the existing Spreadsheet which has a Script attached to it; (everything working the way I want it but I want a copy.)
Now when I create a copy of the Spreadsheet, its associated Script files also get copied - but what does not seem to be copied over are the enable/disable status of various APIs.
The new copy seems to take on default permissions and only default APIs seem to be enabled.
I would not know if the script has required APIs enabled or not. Only when I try to run it, it would throw up an error and crash.
I would like to programmatically know this and take action when a copy of the spreadsheet is made.
I have done several searches for this but could not find any relevant results hence asking this question here.
Specifically more annoying is the fact that the URL Shortener API and even Drive API have to be enabled in two steps - which includes logging into Developer Console.
If I distribute this tool then they would be forced to go into Source Code and from the code editor forced to enable the APIs.
Please help.
Does anyone know how to integrate tasks from PyCharm CE 4.5.3 with Asana? There is an integration plugin (actually pre-configured generic REST API plugin) available.
I followed documentation on generating the API key but PyCharm returns "unauthorized" error all the time.
API from within valid web browser session works OK:
Project ID can be retrieved using GET on
https://app.asana.com/api/1.0/workspaces
Similar for issues:
https://app.asana.com/api/1.0/projects/PROJECT_ID/tasks?assignee=me
The Project ID is most easily found in the URL of your project when using the web interface: https://app.asana.com/0/{PROJECT_ID}/list. This is the first URL which you should see if you simply go to asana.com and are already logged. This number does not match what's found in this other SO question, but it works with API calls such as pointing your browser to https://app.asana.com/api/1.0/projects/{PROJECT_ID}/tasks?assignee=me
Using the URL in your first bullet will get the workspace ID which is not the same as the Project ID it seems.
Now, click on your user icon in the top right then:
My Profile Settings
Apps tab
API Key...
Copy your API key (or generate one first if you need) and then paste it into PyCharm as the Username for your Task Server. Paste in the PROJECT_ID from above and leave the password blank.
Doing the above worked for me on OS X Pycharm 4.5.3
Problem Description: deployed a new gadget xml but gadget does not refresh although parameter nogadgetcache=1 is used.
Steps to Reproduce:
i makes changes to a gadget xml. Deploy using Eclipse, to an appspot site.
2, Deploy through code.google.com's google app console ( i think this is only for changes to manifest, but with or without this step, refresh does not happen ).
Able to see latest changes on the appspot site hosting the gadget xml
logout of gmail, login with : https://gmail.com/?nogadgetcache=1
gmail gadget behaves like the old version.
Even stopped development for more than a week, still not refreshed.
Anyone here can help or encounter similar issues?
Try renaming the gadget spec file so it uses a new URL (then update your manifest to reflect this new URL). This is from Google's documentation.
we have the same problem it take 30mins to get it work..
https://mail.google.com/mail/u/0/?shva=1#inbox?nogadgetcache=1
i found the problem in chrome take's very long.. if you do it in internet explorer prived mode it much quicker..