I am trying to use google assistant in a raspberry pi project. I have created my developer project. However, there is no option to register the device model as instructed in Google Assistant SDK for Devices ->
https://developers.google.com/assistant/sdk/guides/library/python/embed/register-device
As a result i am not able to execute the sample code.
The link was also not there for me. I just started guessing at the URL until I found it:
https://console.actions.google.com/u/0/project/{your-project-name}/deviceregistration/
This allows you to follow the instructions in their docs to register a device.
Since i was not able to do it from the front end consol, I tried the "Alternative ways to register". I was able to register the device eventually by using the Registration Tool Commands mentioned at https://developers.google.com/assistant/sdk/reference/device-registration/device-tool#register-device
I did it after downloading the credentials file and authenticating it. However, i believe even authentication can be done with these commands.
When you create a new project, you'll see a bunch of cards like "Build an X action". Click "Skip" in the corner to create a blank project that will have the device registration tab available.
Related
I've just created an app (slash command) and install it in one of my workspaces. But now I want to add the same app to another one. Is it possible without distribution to App Directory?
If you want to add you Slack app to another workspace, you can do so without going through the process of placing it on the App directory.
All you need to do is
add the ability to install your app to an workspace using OAuth 2.0.
enable public distribution
So instead of clicking "Install app to this workspace", which works great for private Slack app, which live in one workspace only, you need a script than can be called from a web browser to run the Oauth installation routine. This is usually done by adding a Slack button to your website.
You also need to enable "public distribution" for your app. Note, that is not the same as putting them on the App Directory, which requires submitting your app and undergoing a review by the Slack team.
Found the answer, in the small grey caption in the app creation form
Your app belongs to this workspace—leaving this workspace will remove your ability to manage this app. Unfortunately, this can’t be changed later.
We're trying to set up a new marketplace app. As suggested by the Google Apps setup UI, we have provided a Setup URL for setting up an account with the service.
However, if I click on the Test Install Flow button, it redirects to the Universal Navigation link instead of the dedicated application Setup url.
What's going on?
The setup URL is never invoked by Google. I don't know why, and I don't know why they provide a field for it.
An answer I got from a Google guy is that if you need an interactive setup you should just implement it in your Universal Navigation link (on the first time the admin opens it or something). The full answer is here: Google Apps Marketplace app installation callback
Ok, so without much notification given, adding market place listings to your vendor profile is no longer possible. The 'create new listing' button is greyed out.
I need to make changes to an existing marketplace listing but that gives errors. We are forced into the new SDK.
So I went ahead and enabled the apps market SDK, filled out all details including images of all sizes, add a COB extension for the contextual gadget and saved the whole thing.
A minute later I return to make a modification and dang... error: "We are looking into this.".
#Google: HELP !
UPDATE : I can reliably reproduce the error as explained here.
Enable Google Apps Marketplace SDK in your project
click on the gear icon, you will be directed to the old API Console
Fill out all details
Add a COB extension (Contextual gadget)
Save everything
Close the API console
Go back to your cloud console -> Google Apps Marketplace SDK
Click on the gear icon again
ERROR
Tested with several google accounts on different computeres and multiple projects on the cloud console.
#jonathanberi could we have a status on this issue, please? We are experiencing the exact same issue and we are unable to publish our app (which is ready) because of this bug. We have tried both creating a new Google Apps console project from scratch as well as modifying a draft of a yet to be published page with the same result. Is any information that we could provide to help?
You must fill out parameter name and a paramter value or your cloud console will return errors and you will not be able to recover from this.
Ouch, that were 3 useless weeks....
Do you know if the Windows Phone SDK offers an API that allows to add a custom App entry inside the Application Settings page?
I would like to create a new entry "AppXYZ" that links the settings page of the application.
Is this view reserved just for "system" applications or could also be used to add a link to an external app's settings?
Although not well-known, there is a way to do that. In WMAppManifest.xml you can specify that your app belongs in HubType="268435456". That way, it will be integrated there. This is not an officially-supported approach and I am yet to see a third-party app approved in the Store that would handle this.
You can link to the settings page of your own application but not to the windows phone settings page you show us in the screenshot. Developers are only allowed to show some of these by using the corresponding URL schmemes.
Unfortuantely there is no possibility to integrate your app to the official settings hub as a third party developer. Adding HubType="268435456" in your WMAppManifest.xml file will prevent a successful sumbission.
Sorry for the bad news...
When installing a Google Marketplace App, the flow usually ends with the admin in the app's settings on Google with the option to sign in now. Is there a way to end with the user actually using the app (i.e. not having to click the link to sign in to start using the app)? Could the user just be sent to the app on the optional setup without returning to the app settings page on Google without that causing other problems?
Some of the documentation says:
We strongly recommend that the administrator be directed through a short, linear series of actions and returned to Google quickly so additional users can start using the application.
I tried testing this out, but it seems like there's some lag between installing and the app showing up in the "more" drop down for Google (I tried installing another app and did end up on the final page but the app still didn't show up in another account. It's been a few hours and it still isn't there) so it's hard to tell if it's just slow or not actually installed on other users' accounts.
Sorry the last section was misleading. This is not a question about the link not showing up immediately.
The new experience for Google Apps Marketplace lets you land the user in the app instead of the admin console. There's now a popup for the app to request permissions and to agree to terms and then the user ends up in the app. One-step installation. Good work Google.