I built a custom app for Google Assistant and basicly everything works fine.
Now I added account linking regarding the google documentation (OAuth 2.0 with Authorization Code Flow). Also this is working fine in test environment.
Now the problem: When testing from my device (Google Assistant App on smartphone) the following error appears local on the device when linking the app through the Discover tab:
"ServiceId is not configured".
And no https request from Google is made to my OAuth server.
I made hard research through all platforms but I cannot find any place where I could configure the so called ServiceId.
Any ideas?
Account linking does not work from the directory listing when the app is in testing (Not in production).
Related
I implemented google login in flutter without using firebase in flutter (google cloud console). It was working in apk then later I needed push notification service for which I used firebase (fcm token and all) then I released the app to playstore but google login does not work. I keep getting apiexception error. Has anybody faced this issue? if yes any help would be highly appreciated.
I do not have a specific answer to your problem but I have also faced this problem once, I accidentally resolved it though.
But Error 12500 is a general error code that may occur when attempting to use the Google Sign-In feature and is caused by a few potensial issues:
An issue with the SHA-1 fingerprint of your app's signing
certificate: To use Google Sign-In, you need to configure your app's
SHA-1 fingerprint and package name in the Firebase console. Make
sure that the fingerprint and package name you have configured in
the Firebase console match the ones you are using to sign your app.
An issue with the Google Services configuration file: Make sure you
have properly added the Google Services configuration file to your
app.
An issue with the Google Play Services library: Make sure you have
the latest version of the Google Play Services library installed in
your app.
An issue with the device or emulator you are using: Make sure you
are testing on a device or emulator that has Google Play Services
installed and is up to date.
Possible fixes to try/check:
Double-check the SHA-1 fingerprint and package name: Make sure that
the SHA-1 fingerprint and package name you have configured in the
Firebase console match the ones you are using to sign your app.
Make sure you have added the Google Services configuration file: The
Google Services configuration file is required for your app to
communicate with Google services, including Google Sign-In. Make
sure you have properly added this file to your app.
Update the Google Play Services library: Make sure you have the
latest version of the Google Play Services library installed in your
app. You can check for updates by going to the "SDK Manager" in
Android Studio.
Test on a device or emulator with Google Play Services installed:
Make sure you are testing on a device or emulator that has Google
Play Services installed and is up to date.
I hope this helps! I will quickly search if I can find any other solution.
Issue: When tapping on redirect link it gives Page Not Found.
What is expected: Tapping on the redirect link sent to your email should open up the app if it is installed.
Have tried the suggestions from most related solutions on StackOverflow and GitHub.
My custom domain in Hosting:
It is also authurized:
Dynamic links I made:
ActionCodeSettings URL prod project: https://myprodapp.com/login/welcome
firebase.json:
added to info.plist:
Associated domain for iOS
Callback URL:
Android
iOS
Need to mention we have two firebase projects connected to our flutter app - one for the development environment (dev) and the other for the product environment (prod). Passwordless sign in with the firebase default domain works on dev environment for only Android. So seems the coding part works fine.
Problem:
I ve a problem for long time, where the smarthome app I created with Actions SDK doesnt show up in the Google Assistant app under home control as a test app.
I tried 3 different accounts, looked for being signed in with the same account, started from scratch but nothing helped!
Can you please help to solve this, since it is pretty bad that I cant test the final User oAuth flow from the Google assistant app.
This is BLOCKING me from continuing at all and also make me feel that Google Home is not that production ready.
Iam developing the smarthome app action for a worldwide known opensource project and a lot of users ask for Google Home. I have the implementation almost finished and it stucked at this not showing up in the assistant app. So I cant test and the community cant test either!
This is from my point of view, not good for Google and the launch of Google Home. I had many support tickets open, but still no solution. Hopefully the developers feel responsible and can help.
Environment:
MacBookAir: Mac OS X 10.12.15
Browser: Chrome, Version 59.0.3071.115 (64Bit)
Android Smartphone (Starting from Android v6)
Framework: Actions SDK (gactions)
Steps to reproduce:
Created a new project under
https://console.actions.google.com/
Added Actions SDK to my project and run these commands:
./gactions update --action_package action.json --project
<project-id>
./gactions --verbose test --action_package
action.json --project <project-id>
Added all needed App information and the Account Linking information
Clicked on TEST (next to SUBMIT FOR REVIEW) Button
Result:
I cant use the Simulator, cause when I type "Talk to ", I always get this ErrorMessage: "Sorry, this action is not available in simulation".
If I open the Google Assistant on an Android device and go to "Home Control" to see my test smarthome app, it doesnt occur in the list with brackets etc. like [test ...]. It is not there at all!
I found other devs having the same problem like me over here:
https://github.com/actions-on-google/actionssdk-smart-home-nodejs/issues/1
Here you have my command in the terminal to deploy the smarthome app via gactions command:
./gactions --verbose test --action_package action.json --project <project-id>
Checking for updates...
Successfully fetched update metadata
Finished checking for updates -- no updates available
Pushing the app for the Assistant for testing...
POST /v2/users/me/previews/<project- id>:updateFromAgentDraft?updateMask=previewActionPackage.actionPackage.actions%2CpreviewActionPackage.actionPackage.conversations%2CpreviewActionPackage.actionPackage.types%2CpreviewActionPackage.startTimestamp%2CpreviewActionPackage.endTimestamp HTTP/1.1
Host: actions.googleapis.com
User-Agent: Gactions-CLI/2.0.7 (darwin; amd64; stable/6f4c996f8ee63dc5760c7728f674abe37bfe5fc4)
Content-Length: 369
Content-Type: application/json
Accept-Encoding: gzip
{"name":"users/me/previews/<project-id>","previewActionPackage": {"actionPackage":{"actions":[{"deviceControl":{},"fulfillment":{"conversationName":"automation"},"name":"actions.devices"}],"conversations":{"automation":{"name":"automation","url":"https://MY-GOOGLE-CLOUDFUNCTION-URL"}}},"name":"users/me/previews/<project-id>"}}
Reading credentials from: creds.data
Successfully pushed the app for the Assistant for testing
Your app for the Assistant for project <project-id> is now ready for testing on Actions on Google enabled devices or the Actions Web Simulator at https://console.actions.google.com/project/<project-id>/simulator/
I am faced with the problem as you are. I have sent email to Smart Home team, but they just explained:
"Smart Home Apps not showing in the list of Apps under the Home Control section on the Google Home App is a known issue and we're currently looking into it. I will reach out to you as soon as I have an update on that."
Unfortunately, I do not receive any feedback so far, even I have opened many support tickets.
By the way, the offcial document has updated twice(July 14,2017 and July 25,2017). But it still now not works, I do not know what does it mean! It is very disappointed.
This bug has recently been fixed, so all users should now be able to see their test devices in the Google Home app.
when I run the Google smart home demo, I have a problem at 25.Find your app in the list of providers. The result is that I can’t find my APP in Home control use the Google Pixel device.
I am sure that:
1、I use the same google account to create the project in web and login in google home App on Google Pixel, and I launch the test in 30 mins which mean that the test shouldn’t be expired.
2、I have done the command "gactions test --action_package PACKAGE_NAME --project PROJECT_ID"
Could you any body gave me some suggestions? I have sticked it for more than two weeks.
The Google smart home demo you mentioned is to help you build web service to process Google smart home requests. After building web service and host it on some public URL, you have to specify this URL in your action.json.
Also you need to build your OAuth 2.0 server and specify it in project setting in AoG console.
Then after executing"gactions test --action_package PACKAGE_NAME --project PROJECT_ID", you shold see your app [test]YOUR_APP_NAME in the add devices section.
Please check if you miss any part above and your gactions command runs without error messages.
Good luck~
I am testing an application I developed using the .NET Devkit 2.0. In My Developer Center I am trying to run the connection tests in the Testing Your App section of the page. The OAuth test works fine but when I try to test OpenID I am getting an error.
When I click the "Test subscribe to app from Intuit App Center (OpenID)" it brings me to the company connect page, then I select the company, then it brings me to a free trial page of my App.
When I click "authorize" I am getting a 404 Error.
The URL points to: https://myserver.com/Error.aspx?aspxerrorpath=/myapp/OpenIdHandler.aspx
Where myserver is the name of my development server and myapp is the name of my application.
I am able to run the application from Visual Studio without a hitch. It connects and runs as expected but when I try it in the dev center it doesn't work properly.
Are my application settings correct?
Should I be pointing to OpenIdHandler.aspx in this instance?
App settings in the dev center:
App URL: https://myserver/myapp/Default.aspx
Disconnect Landing URL: https://myserver/myapp/Disconnect.aspx
Manage Users URL: https://myserver/myapp/Default.aspx
OpenID URL: https://myserver/myapp/OpenIdHandler.aspx
This is my first run at publishing to the Intuit App Center so any suggestions would be a huge help. I'm not even sure if the settings in the dev center are the problem or not.
Thank you
My firewall was not set up properly so it was not allowing any traffic to hit the desired pages of the site. Seems very curious to me that I was able to go to the default page but no others. Any way, it works now.