I have developed an Action for google assistant using Dialogflow v1, everything is working perfectly in a developer version, but once I have submitted it for the Alpha release, the user entity not working for the alpha version or with the testers account.
I have checked my logs and it shows me that user entity is created successfully but it didn't detect it in the slot filing.
I have also tested it with the Get request from Postman with the same sessionId and successfully get the entities but I understand why it is not detecting in slot filing in Alpha version.
I have attached the video also about the issue, Please help me to resolve this.
https://drive.google.com/file/d/1y2zSKqcZ3OTey_RGnRxHMZfFVhP5oSlh/view
I got stuck with this same issue a few weeks ago, after a looong conversation with AOG support I got this answer :
"I had to do some digging. Currently, the session entities arent available for alpha/beta/prod AoG versions."
Related
I have a capsule that I want to test on my Samsung S9+, and have enabled developer options, and created a submission.
However, when I attempt to launch on the phone, I get "Oh, there was a connection problem. Try again later"
How can I figure out what is going on?
This is a reported issue in the latest version of Bixby. It is being addressed.
https://support.bixbydevelopers.com/hc/en-us/articles/360023521654-Bixby-client-2-1-17-10-breaks-on-device-testing
issues should be resolved as of 5/31/2019
I got this email from the development team a few days ago. I guess we should just sit tight.
Hello Bixby Developers,
On the latest version of the Bixby client (2.1.17.10), if you are
using private submissions for on-device testing, there is currently an
issue that causes Bixby to fail with an error: "Oh there was a
connection problem. Please try again later"
Our engineering teams are working hard to release a hotfix as soon as
possible. We will provide a final email update once this issue is
resolved. In the meantime, we will provide ad-hoc updates here.
Thanks, The Bixby Team
I am trying to save user information on google assistant bot with the help of dialogflow using actionpermission intent in my webhook to store user previous details which he/she had filled for the first time. Saving like this works perfectly on my developer account and when i add alpha testers for testing my bot and saving their name and type on google assistant bot it works fine for some testers and parallel its not saving information for some other alpha testers. I don't know why its happening. If anyone can help regarding this issue it would be great. Thank you.
I believe the issue is not related to the alpha test but rather to the voice match.
On smart speakers, which are in a multi-user environment, it cannot be assumed by default that the user speaking is always the same. To get around this, smart speakers have a "voice match" feature which needs to be enabled in the device settings.
Until that is enabled, interaction data is not saved between sessions.
I've been developing on Actions on Google using Dialogflow. The webhooks worked like charm when using the simulator for testing.
I published an Alpha released but it isn't working at all. The Alpha testers can't get it connect and when I tested that Alpha version on the simulator, it tells " isn't responding right now. Try again soon."
In the documentation "Releasing Your Actions to Alpha and Beta Environments", a paragraph reads:
"Implement fulfillment for alpha/beta releases
The release channel information is not included in the HTTP request from the Assistant to your fulfillment. To handle release channels in your fulfillment, you should provide different fulfillment URLs (for example, one fulfillment URL for the beta and another URL for the production version of your Action)"
I searched everywhere and I could not find any pointers on how to implement a new fulfillment for the Alpha (and eventually the published release).
I have one url that I use in the fulfillment on Dialogflow, so how can I do otherwise?
The same webhook will work for all the versions, (at least it is working for aplha in my case), check for one of the following cases...
Make sure you have added Alpha testers' mail addresses to alpha testers list, otherwise they will not be able to access the alpha release.
Make sure you have deployed the latest updated version of agent on actions on google page. If not do so,
If you are getting a "modified action" message like this, that means you have a change that is not yet deployed.
Deployment of agent is not instant and takes quite a bit of time to get accessible on Google actions platforms. Check the current release status of your latest deployment, it should show "deployed", if it's showing "deploying" you have to wait for some time to get it deployed.
If all of the above is Ok, test the alpha release and check out your web-hook log (even check if web-hook is at least receiving the requests or not) , that will be the only place where you will find any possible error.
i created a chat bot with dialogflow (V1) and integrated it with google actions for Google Assistant. My company was supported by Google for all development process.
The first release of the chatbot was deployed for all users before 8 may. All works well and the actual release on Google assistant is working well.
The problem now is if i want update the bot with new actions and features the behavior of the chatbot is different in the simulator from draft state to aplha or beta release.
In the webhook the data provided by dialogflow is different (the logs on the cloud function): in the draft all parameters are set correctly , but when switch to alpha or beta version (created from the draft that works well) the parameters are always empty and all the bot answers are wrong.
There are specific actions to make or settings after 8 May to switch from draft to alpha/beta release of Actions on Google to avoid this strange behavior?
Alpha and Beta releases people made last August used to lack the training (machine learning) the agent received. It may be the case here that your alpha and beta versions have the same problem.
I saw the commercial library for iAd's from Monte but he isn't developping it anylonger due to the coming of InnerActive Ads in Livecode, right? So, I have created an InnerActive account and tried the only lesson I found on Livecode Lessons. That didn't work. So I posted a comment there which is awaiting moderation for quite some time now. I also mailed Inneractive, got a ticket replied, but no answer from them either.
If anyone has Ads with Inneractive running please tell/show us how you did it. I am calling mobileAdRegister with my appID and that seems okay. Then I try mobileAdCreate and mobileAdSetTopVisible and 'the result' tells me 'could not create ad'.
Dictionairy then tells me the app does not have Internet permissions or the registered app key is not valid. But I do check for internet connection and I'm sure I'm using my valid appID..
Regards, Amsterfrank
I have tested ads in the current release of LiveCode and they do indeed seem to be broken.
The LiveCode quality control team is aware of this and are currently investigating what could be the cause of this. A report on this issue can be viewed here-
http://quality.runrev.com/show_bug.cgi?id=11224
A workaround for now is to use an older version of LiveCode. After running a few tests, the last version of LiveCode that does not exhibit the mobile ad bug is LiveCode 6.0.0. This is available to download from here-
http://downloads.livecode.com/livecode/
With that being said, I would recommend holding off until the issue is resolved in a more current releases as there have been many bug/enhancements to LiveCode since 6.0.0