Trying to enable my apps script bot for whole domain - hangouts-chat

I am trying to enable my bot for "Everyone in your own domain". An getting this error.
If I enable it via "Specific people and group in your domain" - it works.
Does anybody have an idea what I missed?

When using the HEAD deployment, Apps script bots cannot be shared across an entire domain.
Though subtle, it is mentioned in the docs at https://developers.google.com/hangouts/chat/how-tos/bots-apps-script.
Image of description here
To fix this you can just create a new deployment and it should run just fine.
Go back to your Apps Script project
Click on Publish > Deploy from Manifiest
Click "Create"
Use the new Deployment ID for your project.

Related

How to deploy an update to an already released Google Workspace Addon?

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.

JDeveloper deployment "Page can't be displayed" error

For development, I'm using the integrated weblogic feature in JDeveloper. So far, this has worked fine. I was recently put onto a different project, however, and when I try to deploy it, I'm having trouble. Here are the steps I take:
Run->Debug Server Instance (IntegratedWeblogicServer)
In the Projects, I right-click on Web Content->index.html and select Debug.
According to the log, the applicatoin deploys successfully with the target URL of http://localhost:7101/Myapp-Myapp-context-root/index.html and it then attempts to open the page.
However, this gets me a "This page can't be displayed" in Internet Explorer. No error messages in JDeveloper's log or IE's console. I realize this doesn't give a lot of information to work with, but it's all I've got right now.
One other thing, and I don't know how relevant this is, but if I attempt to refresh the page or enter it into a different browser, it redirects to https://localhost:7102/Myapp-Myapp-context-root/index.html
I figured it out. It switching to a secure port was related, as the finalized product is supposed to do that. Development requires the security-constraint fields in the web.xml to be commented out.

Gmail gadget not refresh although nogadgetcache=1 parameter is used

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..

Make our own "Application unavailable" page

We need to completly stop our application during an upgrade because we have to execute a critical mysql script.
So our application will be turned off during several minute then Cloudbees will display a basic "Application unavailable" page. We would like to change this by our own page with our logo, like we did it when we have our own apache/tomcat server. Could it be possible ?
Btw, is there a page with active sessions like we have in the Tomcat manager ?
Thanks for your help,
You can use beta-featured blue-green support to switch your application to another instance running a "maintenance" page
with latest SDK (1.3.1), run bees app:proxy:update -a acme-maintenance -al www.acme.com to reconfigure the http router for www.acme.com to the maintenance app, then let your application run the mysql upgrade script, and restore the router configuration after completion.
Warning : this feature is in beta and subject to instabilities / API changes
At the moment there isn't an easy way to do that - but there is a feature which will be out there soon to make that easy (amongst other things).
The only way currently is to have an app (another app) - which is your simple page - you then remove the domain name from your current app and add it to that app (etc) - messy, but possible.
In terms of sessions, the operations tab of the web console shows information like that, there is also the newrelic console which provides other insights.

Amazon Git Eb Tools not deploying

I followed the help page here
and I created my application through the eb tools command line tools. I can see the application on command line, however when I log into my AWS Management console and select the region area, and click on "elastic beanstalk" I see the welcome screen asking me to create a new application,my question is why cant I see my application on the web interface? Also the application is running on the web because when I visit the url the link is active, but I see this message "Could not find rake-10.0.2 in any of the sources (Bundler::GemNotFound)" (which if anyone knows how to fix that would also help)
Thanks in advance
It turns out that somehow amazon changed my secret keys, and my instanced where not showing. When I updated the keys on my local machine everything began working correctly.