I'm trying to test an unpublished Google Sheets add-on with other google accounts.
I've followed the documentation but it doesn't work as expected:
In any case no "Install add-on" button is displayed for the head deployment
In order to display the button "install as add-on", the tester needs to create a new deployment
If the user has read-only access it shows the following error
If the user has edit access, then it shows the button
Once the button is displayed, clicking on it shows a message saying that it's deploying the add-on but...
In no case the add-on appears in a spreadsheet, nor in the Manage add-ons pop-up
When I come back to the "deploy from manifest" list, the deployment that was supposed to be associated to the add-on doesn't show the expected button "uninstall add-on"
I have tried:
with Gsuite users having editing rights and myself, the owner.
FYI,
with a stand-alone script and a script associate to a spreadsheet... same results
I think the whole flow is just not working. So please G Suite team check out this message
Related
I tried to register an application in the Googlt Cloud Platform They ask me to enter a home site and a link to the privacy policy because I do not have my own site, I entered my telegram channel into the window of the home site, and threw the privacy policy on google drive
And I got the problem shown in the picture:
https://imgur.com/0OducVW
The error you are getting is not because you have added google as the privacy policy, that is perfectly fine. The error you are getting is requiring you to add the domains added in the previous steps by clicking Add Domain.
Simply click the blue button in your screenshot, then add google.com. If you do not have a website, you do not need one right now. I would not add the t.me unless that is actually your website's domain. If you want to add it, follow similar steps to the previous domain and enter it in the field box as t.me. If you do not wish to use this, then remove it from the previous step and leave it blank for now.
We are developing a google smart home action. As per this and this guides we added testers as viewer and shared action and it worked few months ago. Now we don't see this share button in our simulator anymore. Wonder how to share with testers anymore? As guides still wants us to share the project through this button.
Screenshot from documentations:
Screenshot of my simulator:
We are able to add the tester in IAM project, but tester is unable to see the action like owner does ([test] ABC agent) in google assistant app.
Edit 1:
It doesn't work even sharing an action with owner rights. Second user is unable to see that action in Home Control under google assistant app
As per discussion with 'Actions on Google Support Team' they say that "There has been a slight modification on the interface in the simulator page. Unfortunately, the current documentation hasn't been updated yet to reflect this change."
You can still share your Action without the share button. To recap:
Go to the Actions console and select your project.
In the right navigation menu, select the three dot icon and then Manage User Access.
This redirects you to the IAM page for your project.
Click ADD to set a team member's access to your project. You must be an owner of the project.
Type the member's email address in the Members box. To assign view access, from the Roles menu, select Project and then Viewer. The members you add will be able to see the Action on their console. Please note that the system does not proactively notify the added members.
Tester/Viewer will have to login in to console and Enable testing in simulator to see the action in Google Assistant App.
Happy Coding !
I created a DialogFlow app that works perfectly in my developer account.
But I need to test it as another user, so in my Google Action simulator, I added another test account as a OWNER to the project.
I verified this user has OWNER status in both the DialogFlow and Google Action UI.
They are able to edit both projects with full access.
However, when the test account tries to use the simulator it says:
Sorry, this action is not available for your app. Sorry, this action
is not available for your app. In the simulator, you are only able to
invoke actions that you have added to your app. For more information
on how to invoke your app, click here
https://developers.google.com/actions/discovery/explicit
This makes no sense to me:
I verified the test user has OWNER/ADMIN status on both DialogFlow and Google Actions for the project.
In DialogFlow, I verified the Google Assist is pointing to Default Welcome Intent as the default intent.
In Google Actions, I verified that the Default Welcome Intent is visible on the BUILD > ACTIONS UI.
As others suggested, I tried renaming the app several times with no luck.
I tried publishing an Alpha version, with still no luck.
My gut tells me it is some sort of permission/visibility problem, but I am completely stuck. Any ideas would be of great help.
EDIT:
THIS ISSUE HAS BEEN SOLVED. SEE COMMENT BELOW.
"I revisited my activity controls and noticed my "Web and App Activity" had a special clause due to organization permissions. I completely missed it due to the confusing UI. Posted a picture in the main thread. Thanks for reminding me to double check that area."
After you asked your company admin to enable this feature, it should be same as the image in below.
This error message is quite misleading. I have encountered this error a couple of times, and generally the problem was with one of the privacy settings in my Google account.
In this case you should go to https://myaccount.google.com/activitycontrols, confirm that you are logged in using your test account, and make sure the following are enabled:
Web & App Activity
Device Information
Voice & Audio Activity
Now that my Google Assistant service is approved and deployed for use with Google Home, I am seeing inconsistent behavior from the Google Home app WRT account linking.
There are 2 places you can do account linking for a service in the Google Home app:
When you navigate in the menu to 'More Settings', then 'Services', then pick the Service that you want, then scroll down and hit 'Link Account'. This works successfully some of the time. When it does, I can then invoke my service and verify that account linking is complete.
After saying 'OK Google, talk to XYZ', (where XYZ is your service name) the google assistant responds with "It looks like your XYZ account is not linked yet. You can link XYZ to your google account from the google home app". Then when you go to the Google Home app you see a new blue card that says 'Link to XYZ'. When you click 'link', it will sometimes successfully link, and many times an error 400 comes up: "Your client has issued a malformed or illegal request.".
I haven't been able to conclusively determine why it works some of the time but fails many times as well. I did find in my latest round of testing that if I removed all other users from the Google Home app other than the specific user account that I was working with, I could get it to successfully link after multiple attempts. With this inconsistent behavior, it doesn't seem like the problem is on my side with the account linking process I put together per these docs, but I don't know.
Has anyone else experienced similar account linking issues? If so did you find the root cause and resolve?
Our site is using the 'Integrate with Google' button to allow G Suite admins to install our web application without needing to go to the app marketplace (we're doing as described here). Unfortunately, if our user is signed into multiple Google accounts, the integrate button seems to just use whichever account they happened to sign into first, which might not be the right one. A workaround is to sign out of all accounts and back into the desired one, but we can't very well ask that of our users.
Is there some way to force the button to show an account selector? Or alternatively is there some way to provide a 'login hint' similar to the one that the OAuth API takes?