Requests of intents not reaching hosted Fulfilment when running test suite

[DevDipro]

Hi everyone,

My situation is the next one, I have a Google action cloud-to-cloud project where I've implemented Oauth2.0, the 4 intents SYNC, QUERY, EXECUTE, and DISCONNECT.

When I connect to the voice app through the Google Home of my smartphone, everything works fine, I can login in the selected voice app, see the devices listed and call the intents and see the request logged in the hosted machine. But when trying to pass the test suite from the account that has the project registered, I don't even get the requests in my server.

In Google my activity, I can see the petitions from the assistant being made, but I see in the details of the log the next errors being repeated through all the commands.

- Sorry, I couldn't reach the [project name]

- Sorry, it looks like the [project name] is unavailable right now.

And in the Google Home Analytics - Cloud Integration dashboard, It doesn't even register the requests.

I've thought that the reason can be that the test suite isn't login to the Fulfillment code before testing the intents.

I can provide more information if needed.

Thank you

[armen_dpe]

Thanks for bringing this up. Are you selecting the correct project ID when signing in on test suite website?

Can you please share the screenshots of the following: signing in on test suite website, running test suite.

This will help us to debug the issue further.

[DevDipro]

Hi armen_dpe,

Thank you for landing a hand, I attach the screenshots below. I've cancelled the test before finishing because, unless the request of device requirements, the rest of the tests fail.

[armen_dpe]

Can you control your device via your app? Is it online?

[FORSIT]

I'm experiencing the same issue in my cloud-to-cloud action. Executing an action with "Hey Google", Alexa or my own mobile application works and a lock for example is locking and unlocking and the right state is set in HomeGraph. When starting the test suite, the test results are always the same. I'm logging everything and no single request is done to my service. Also I have my own OAuth2 provider and there goes nothing in, too.