Some time ago, I made a few test projects on Actions on Google. I later removed these projects by deleting them on Actions on Google and/or on GCP. However, these projects still appear in the Google Home app:
I've tried relinking them (as per Remove 'Google Actions' project from Google home app), but this doesn't seem to make a difference. The endpoints for the project probably aren't live anymore, so the relinking process fails without error.
How can I go about removing these projects from the app?
This is currently a bug - I would recommend subscribing to the public issue tracker related to this to be informed of updates once it is solved.
Related
I have a Raspberry Pi running Home Assistant (Hassio actually) and it is communicating with Google to make the lights go on and off using Google Assistant. To do that I have followed the cook book on the home assistant website. When Hassio updated from an API password to Oauth, I created a new project, because I had some issues with discovering devices.
In the current situation, when I ask Google to turn on the lights, it turns on the light, but also states that [lastprojectname] is not reachable. I did remove the project from the Google Actions console, but it does still show up in the Google Home app. I unlinked the account there, but still the same issue. So the old project is still in the linkable account list.
When I ask Google to turn on the lights in the 'office' (for example), it states, 'OK turning off 4 lights' while there are only 2. The lights are not in the app anymore, the account is not linked. Very weird. Any ideas?
This happens to me some of the time (I'm also using Home Assistant, but just starting with Google Assistant integration). When it happens, I just link, and then re-unlink the app. It usually sticks the second time.
I know that's the equivalent of "turn it off, then turn it back on", but it works, and I don't have a better solution :|
In my developer account, I can succesfully test the app using the simulator.
I also sucessfully deployed an Alpha version, and waited 24 hours.
However the opt-in link doesn't work. Every time I navigate to it, I see:
We can't find what you're looking for at the moment. Please try again later.
YES, I have the activity controls all enabled
YES, I have a google home device connected to this account
YES, I am the developer of this action, and have verified permissions
in IAM
This is driving me bananas. Does anyone have any suggestions on how to get it to appear?
The problem is that I was not opening these links using Google Assistant (I was trying to open them using Safari). The documentation says "open on mobile", but it doesn't tell you to use the Google Assisant.
If you have iOS, make sure you download Google Assistant!
I know this is an old question, but for the past few days I have been in the same situation with no answers to be found on the internet.
The situation is represented in the image below:
My opt-in link was the following:
https://assistant.google.com/services/a/uid/uuid?hl=en
Removing the trailing ?hl=en at the end of the link worked for me.
The Action's settings have become available via the link https://assistant.google.com/services/a/uid/uuid?hl=en after Alpha deployment.
Still, the Action doesn't look good in the Actions explore menu and settings button is missing.
I accidentially moved to the new Actions on Google dashboard. Since then my project does not really work anymore.
I changed the json structure and uploaded a new version that is now running fine on the simulator.
Unfortunately, my Google Home device is not recognizing that such an action exists. This was working before when using the old actions on google api.
Ciao
Fabio
The invocation name has changed when testing apps on the Google Home device.
You should now say
Talk to my test app
I had implemented leaderboard in google play store console. But after implementing when I see the play store console it shows:
One or more APIs that are required for game services to work have been turned off in the API console. We recommend to turn them on again to ensure your game is working properly.
Also the leaderboard not working.
I had this same issue, and when I clicked the Turn APIs button back on, it would show the error again after a page refresh.
I got in contact with Google and they said that a few other developers were experiencing this issue and that they would email me back once they had made progress finding out what's wrong
Now then - because this all happened around the time I was re-linking a project into Google Play Games Services, I thought I had messed something up. Being restless I decided just now to create a new keystore file, and generate a fresh SHA-1 fingerprint. I was able to enter the newly generated code on the API Manager console, under the Credentials tab.
For some reason, it worked; I am now able to sign via Google and access the high-scores page.
Might be worth a try?
Through reading the the flow of registration and development for google marketplace apps, a funny idea came to my mind: after finishing the tests(continuously install and test) for my app(base on web application), can I avoid to submit(never click "Submit for approval") the app to google marketplace so that I could use it privately(may be longtime or forever)? Anyone tried this approach?
You don't have to install or publish your applications from/to the marketplace. You can sideload your app and use it for as long as you want. You could even submit it to an alternative marketplace.
Yes you can just avoid submitting (this is the "old way" of having in-house apps on the More menu).
There is now though a new, better way if you want to add functionality for your own Google Apps domain. It's called the Google Apps Extensions Console and it gives you the ability to share ownership with other developers on your domain and more. Check it out.