I'm quite new to the world of google home/assistant, but I've tried out the new Actions builder, which seems really good and intuitive. I have added the methods of invocation, an intent that triggers an inline webhook function, and filled out all the mandatory fields under "Deploy" for both languages. Testing works as expected in simulation (except not in my native language, Norwegian).
But when I try to create an alpha release, it says "Missing info", and that i should navigate to the "Overview" to see what's missing.
I head over to the overview only to see that multiple things are missing (in both English and Norwegian). Like "Decide how your Action is invoked" under "Quick setup".
I click on the link, which brings me to settings:
There I can "Edit main invocation handling", which brings med further to the main invocation screen:
As far as I can tell, everything about main invocation is in order, or is it something I'm not seeing here? It also says that there are missing information required for the action directory, among other things for the Norwegian language, that are also present.
PS: Pardon any misspellings, English is not my native language.
UPDATE: As for the English language, it was the name that caused the troubles. "My medicines" contained "My", that apparently don't count, which then caused the name to result to "Medicines", and it's not allowed with single word names. After solving this, I was able to create a release for the English language. But I'm still not sure how to deal with the Norwegian language tho.
UPDATE 2: I ended up just removing Norwegian from the Language settings, and adding it again. Then refilling the mandatory fields and translations. Then it worked!
For the English language, it was the name that caused the troubles. "My medicines" contained "My", that apparently don't count, which then caused the name to result to "Medicines", and it's not allowed with single word names. After solving this, I was able to create a release for the English language.
I was still unable to create a release for the Norwegian language, so I ended up just removing Norwegian from the Language settings, and adding it again. Then refilling the mandatory fields and translations. Then it worked!I was able to create and release in both my languages.
Related
I have problem with automatic invoke code completion when I press dot inside the string when the previous panel is already opened.
I'm using standard yaml language configuration, I added dot notation into some strings. Codecopletion is working, but I have troubles in some specific situation.
Do you know where it is a possible to config some detail around language autocompletion?
Description of the video:
write system without selecting it
add . (dot)
suggestion is NOT automatically invoked (vscode client doesn't create request to LSP)
delete .
add .
suggestion is invoke automatically OK
Note that when I select item from suggested items, everything works ok. When I type the string manually (without selecting it) it works odd.
I tried define this in wordPattern but without success.
https://github.com/redhat-developer/vscode-yaml/blob/a9689529c28cfe83c87e0734e3aa0a84994e76fd/language-configuration.json#L37
Another idea is tmLanguage.json, but not sure where to start.
https://github.com/redhat-developer/vscode-yaml/blob/main/syntaxes/yaml.tmLanguage.json
Note that typescript language is working ok
I will appreciate any help
Thanks
While clicking on the test "The test may not have the latest project changes. Try again later." an error is coming
Go to the "Develop" tab and change the Display Name.
So, while testing you will be saying "Talk to " rather than "Talk to my test app"
Finally, after doing multiple try i am able to resolve it by using following steps.
I found the answers by searching the solution for warning "The test may not have the latest changes.." in action console help.
Pick a display name that is short, unique, and memorable. Your brand or product name is usually a good choice. This name is used as the way users invoke your Action, and it serves as the title of your listing in the Assistant directory.
Caution: If you have multiple Actions projects that use the same display name, the simulator chooses one at random. For consistent testing results, use unique names or release channels for each Action.
Reference Link: https://support.google.com/actions-console/answer/9613473?hl=en
Now how to give display name or change display name.
Go to develop tab and give display name or change display name as follows
I'm working on a Visual Studio Code extension, where some settings are required for it to work properly. Right now, in case the user has forgotten something, I'm showing a warning message indicating this, and telling them to fix this property in the settings. I would, however, like to add a button that opens the settings page of that property.
However, after looking around for over an hour, I can't seem to find any support for this in the Api, or anyone else asking this question (which I find a bit weird?). If it really doesn't exist, I'd still expect at least 1 other person asking this somewhere, but as far as I can see there's absolutely nothing.
Is it possible to open the settings window (preferably even filtering them down to only my extension's properties/the one property that has to be filled in) from code?
Thanks in advance
I found it out myself after digging through the keybinds window. You can use the following to open the settings:
vscode.commands.executeCommand("workbench.action.openSettings2");
I did not, however, find how to pass a search query into it to open a specific place in the settings.
EDIT: You can use openSettings & add the search query as an extra argument to executeCommand. For example - if your property is defined as my.extension.property in package.json, you can use this:
vscode.commands.executeCommand("workbench.action.openSettings", "my.extension.property");
I'm creating an agent that interacts with an API I created, Auroras.live. However I always have troubles invoking the test version of the agent from my Google Home.
I really have to stress the "S" in Auroras, and I also have to say "dot", otherwise Google Home interprets it (I think) as Auroras Live, or Aurora.live, without the dot or "S"
This is definitely going to be a problem for others too, as they might not know to pronounce the dot, or forget to stress the "S", and as a result will get frustrated & not use my agent.
While filling out the app details, I tried using different invocations (such as "Talk to Auroras dot live" and "Speak to Aurora Live"), but it wouldn't let me do it, because I needed to use the exact title of my app.
What should I do? Should I (or can I) submit it as an easier to pronounce name (like "the aurora app")? Can I somehow tell Google to accept it with or without the "S" / dot? Any suggestions welcomed.
This is definitely a case where you would want your invocation name to be (slightly) different than your display name. I would list "Auroras Live" as your display name and "Aurora live" as the invocation name.
As part of the testing instructions, explain the problems you're seeing to the tester and request that both invocations be allowed.
If you want to clearly associate it with the auroras.live website, you could also mention that in the testing instructions (to include the dot), but you should probably also consider including a link to the site from the description and possibly from the action itself.
This app has been under development for more than a year and has had multiple releases already. This development cycle I noticed that the "fallback" language doesn't seem to work anymore.
The app had 3 targets: CountryA, CountryB and CountryC.
Each target has the following localization directories:
CountryA: en.lproj, langA.lproj, langB.lproj
CountryB: en.lproj
CountryC: en.lproj, langC.lproj
In each targets info.plist a key "CFBundleDevelopmentRegion" with value "en" is specified.
The project.pbxproj file has both the following key/values specified in the PBXProject section:
developmentRegion = en;
knownRegions = (
English,
Japanese,
French,
German,
en,
fr,
dk,
da,
nl,
new,
pt,
de,
);
When I start the app on an iPhone or in the iPhone simulator with the system language set different from one of the specified localization directories the UI shows the NSLozalizedString identifiers instead of the localized strings. Even when I specify "English" as System Language in iOS!
So... for some reason the en.lproj file is not picked up, because if I use langA or langB as System Language for target CountryA everything is as expected.
Any help is appreciated!
Kind regards,
Niels R.
NOTE: The problem is caused by a plugin of an external company that we had to integrate and which has a Localizable.strings file too. This will cause that "our" Localizable.strings is overwritten.
Sorry to bother with this! Seems that I just had to look a little bit further before asking the question.
"the UI shows the NSLozalizedString identifiers instead of the localized strings" -- Are you adding the Localizable.strings file correctly for the individual targets?
Another problem could be the "region" setting for languages. You should try to change the region too in the Simulator. I have seen unexpected things happening to NSLocale when setting the region to something totally different than the language.