I'm working on making a conversation flow for smart speakers.
with google action builder console. And I'm using google cloud function for webhooks.
However, from this morning I cannot change, simulate or release my google action project.
Cannot save any changes in 'develop' menu on the google action console
(error message : "An error occurred saving the scene")
-> screenshot img showing error in develop
I cannot test any version in 'simulator' menu on the google action console
(error message : "We're sorry, but somethin went wrong. Please try again")
->screenshot showing error for save any changes in develop menu
I can't release alpha or beta version in 'Deploy' menu on the google action console
(error message : "Error submitting Assistant app")
-> screenshot showing error in release
No logs are found in google cloud function related to these problems.
And actually I didn't change anything since the recent release. How can I deal with this one?
UPDATE: another solution is to press ctrl+F5 or clear browser data & cache. This works pretty well specially if you have multiple tabs opened.
It is happening to more people. Maybe this can help:
See this link or this one.
Google console doesn't offer much information about those errors. Only for the model ones. When that happens, and if your model is too big, I suggest to reduce it a little bit (or try with a well-known version that is working) and try deploying/running the simulator again. That way you can find out if it's your fault or Google is updating their system.
It is working again for me, after few hours throwing errors.
Related
Do anyone have the similar problem to control Android apps (from google codelab - fitness app) with their voice, using Google Assistant?
In my app, I tried to activate widget using google assistant (app action tool test), but google assistant doesn't give any respond. Therefore, I used the example code google gave to run, but it still has similar problem that widget isn't invoked when I use app action tool test to test the app.
Sample code google provided:
https://github.com/actions-on-google/appactions-fitness-kotlin.git
the shortcut looks like below and how :
enter image description here
Update:
After updating the new running record, the app won't respond when I want to trigger widget after the first time I can do it successfully. Do anyone have similar question or know how to solve it?
App updates running record
The widget cannot update/display the new running record
widget cannot be trigger to get new running record
I'm assuming you're talking about the codelab titled Integrate Android Widgets with Google Assistant.
I've been able to get this codelab to work - mostly.
When testing using the App Actions test tool:
Make sure you have uploaded the app to a project in the Google Play Console. You'll only need to do this once, even if you change your code.
Make sure the account you're using for Android Studio, Play Console, and Google Assistant on your device are all the same.
Make sure you've compiled the app and deployed it to your device. The easiest way to do this just to run it from Android Studio the first time.
When you create the preview, set the name and Locale.
Even tho these are listed as "optional", these make it easier to debug.
The App name should be something you know will be recognized by voice and not used by any other app. I tend to use things like "Splat" and "Bogus".
Set the locale to en-US
Click "Create Preview"
Once the preview is created, you can test the widget running by
Setting the Intent to GET_EXERCISE_OBSERVATION
Changing the value in the "name" property to something like "run". ("Climbing" will also work, but tell you that you don't have that activity logged.)
Making sure the target device is the one you're testing on.
Clicking Run App Action
And you should see the widget appear in the Assistant on the device.
You don't need to use the test tool, however. Once you have created the preview with the Test Tool, you can just test it right on the device:
Start the Assistant by long-pressing on the home button.
Saying or typing a request such as "How far have I run with Bogus" ("Bogus" being the name I've chosen this time
If you have issues with the emulator, there are some other troubleshooting steps which may be useful depending on the error message you get.
Now, I did say "mostly". I have seen issues where it will stop responding at all, either via the Test Tool or directly via the Assistant. A few things that I've done that often (but not always) help:
Delete and then create the preview again.
Remember that the Preview is only available for a few hours.
Force stop the application.
Force stop the Google Assistant.
Even if you don't see a message, check out the Troubleshooting steps for "Sorry, I couldn't find that"
I'm trying to use the GCP pricing calculator but when the page is loaded I'm unable to view the entire interface to use the calculator. The only bottom part of the page is showing completely.
I've tried loading the page with and without sign-in, even loaded in incognito window but the problem is same. What I'm getting every time on loading the GCP pricing calculator can be found in this image link:
What's the solution to this problem?
This is not really a solution but I can not comment due to low point ;(
You can try this link rather than this link
From console message this seems to be possibly related with ISP.
I could not produce this in any browser in my pc though (ubuntu18.04, chrome81.0.4044.122 (Official Build) (64-bit), firefox75.0), except slow loading of the app while using this link to access.
I am new to Google Cloud platform, I am trying out Google's Talent Solution APIs and getting 400 and 409 errors. I would like to know how to see the error trace on my google cloud platform console for those requests? I could see those requests in the dashboard, not sure if I can drill down and see the exact error?
If you see these errors in your Developer Console main dashboard in the "Error Reporting" section, you should be able to click on the "Go to Error Reporting" link. There, you'll see a list of errors that happened lately. Clicking on one of them, you'll see more info on that specific error (occurrences, last seen, etc...) and a stack trace sample. Further down, you'll see a list of the last occurrences for that error and their respective link to the logs.
Alternatively, you may go directly to your Dev Console -> Logging section and choose the Talent Solution resource if available or the resource where you call the API from (App Engine, GKE, etc...) and filter the logs by error code to get details about these.
I'm following Tensorflow tutorial
Quick Start: Distributed Training on the Oxford-IIIT Pets Dataset on Google Cloud
At the step 3 "Enable the ML Engine APIs", I'm facing the following problem:
"Enabling API" box never disappears and I'm stuck on this page.
Endless Enabling API
Question:
Why the problem occurred and how can I solve it?
In the screenshot I can see that a project hasn't been selected. You need to select a project from the dropdown menu at the top of the screen, where it says 'Select a project'.
If you haven’t got a project yet then you need to create one.
Choose a project from Console first and then go to ML Engine via dashboard, you'll see a more descriptive explanation regarding what's going on (you have to wait up to 10 minutes).
Not sure that the same applies when you follow the step 3 link: I recall waiting more than 10 mins a few times.
Enabling API message
We are starting to enable Stackdriver for our project, but while I have a ubuntu instance with stackdriver logging, and I am getting the logs shipped back (I can see the logs in Stackdriver Logging), when I browse to Error Reporting, it's just a blank screen with a button to "Setup Error Reporting", which takes me to some API documentation which I think is tailored for new application coding. We are running nginx and the logging is working, but I can't for the life of me figure out how to get the Error Reporting to work properly, if that's even doable.
"Setup Error Reporting" should guide you to the setup documentation (not API documentation). Depending on the platform you are using, you might need to perform some changes in your application's code or log format. Read more at https://cloud.google.com/error-reporting/docs/setup/
If you have Stackdriver Logging setup and on Google Compute Engine, the requirement is for your exception stack traces to be log in single log entries.