I got some error: Invocation Error in AOG last week, shown all of Chinese projects can’t executed and show “Invocation Error “. I didn’t do any change, all Chinese projects became OK in pass three days. Now, again I got same errors today, all English version projects are OK, but Chinese projects all FAIL, even a very very small project without any Intent.
Invocation Error
You cannot use standard Google Assistant features in the Simulator. If you want to try them, use Google Assistant on your phone or other compatible devices.
This question is regarding to Chinese, perhaps, it’s almost impossible to have replies in an English-based community, that is why I proposed this question to AOG support team again, this is an extremely fundamental question: Does AOG really support Traditional Chinese? If positive, why it is such unstable?
I have wasted two weeks at this issue. Anyone experienced the AOG Chinese issue? which is, I can trigger the Invocation phase, but any input will induce Invocation Error
All of my 4 Chinese AOG projects are back to normal without previous error suddenly, this error happened once in three days ago. Already issue an email to the AOG team before, they just respond that AOG does support Chinese version.
In fact, all of Chinese projects are all FAIL with “Invocation Error” yesterday, and when I arrived office in this morning, before I revise anything, I perform one Chinese AOG project,it is suddenly OK in this morning, and the rest Chinese AOG projects are all NORMAL now.
Is it very weird?
Related
I kinda have an issue with the search-based Message Extension.
When I debug locally, my app works fine. After deploying the messaging extension on Azure and testing it in the Teams app, I can search for specific queries. The Message Extension gives me the desired results, up to here we are good to go.
The Problem:
After I select one of the delivered search results, the messaging extension does not return the adaptive card. The chat-box in Teams is simply empty.
Is anyone familiar with this issue?
I cannot reproduce this issue. Can you always reproduce this issue? I think you can retry several more times.
Or copy and paste the codes in bot/teamsBot.js here for troubleshooting.
I've been using Azure form recogniser for about a month now, and I've tried with with a variety of forms and European languages. However recently I've run into what I believe is a bug. That's when I use their UI through the dockerized label tool mcr.microsoft.com/azure-cognitive-services/custom-form/labeltool which exposes a web app for labelling and training.
I am working on a German document, and for some reason the UI will ignore umlauts and danish O, even before training and most definitely after.
Is this something anyone has run into before, is there a solution or a compromise to be made? I know this is a long shot, but I thought it's worth asking.
The current version of service doesn't fully support those European languages yet.
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 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."
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