Google Actions Not Working

[Eric_Speebly]

Hi everyone, I have a skill/action that I’m having a challenge with.
I’m using Jovo Framework 1.3
Both the Alexa skill and. Google action were in production when this problem occurred.
The Alexa skill and google action use the same lambda function for fulfilment. The lambda function connects to dynamoDB. The dynamoDB is configured in the app.json file. In the app.json file I have a different configuration for dev, test and prod. In the prod section I have my db, Alexa and google actions configured.
When I deploy Alexa to my prod environment everything works.
When I deploy google actions which is pointing to the same lambda function as Alexa it doesn’t work. I don’t receive the welcome intent. When I remove the db section in the app.json file under the prod section. Google actions works except for the intents that are dependent on the db.
For the google action using AWS API gateway and AWS lambda is there anything else special I have to do to get the actions/
Lambda function to connect to the dynamo db?
The only difference between the Alexa skill and the google action is the API gateway.
Let me know If it will help if I post the app.json file.
Thanks (edited)

[jan]

As discussed in Slack, this might be related to the user IDs:

How is Jovo Affected by Deprecation of Google userId Request Field?

Got this email from Google: Dear Actions on Google Developer, This is a reminder that on July 29, 2019 , Actions on Google will be shutting down the ‘Anonymous User Identity’ property in AppRequest. What do I need to do? To ensure that your Action is not affected by this shutdown, you should look at your code to see whether you use the userID field. If you discover that your Action utilizes userID, you will need to deploy your updated webhook before July 29, 2019 to avoid loss of features. O…

[Eric_Speebly]

For anyone reading the thread - upgrading to Jovo 2.0 fixed the issue.