We setup Google OK (Google Now) with my app success fully integrate with this
example.
in example, its says "App must be uploaded on play store" or you can test using adb command.
So may app work with command, but in some device(not all device) also work with "google now".
My requirement is , when user launch "Google Now" and speak like "Total amount of site number 117 in 2017 on "App name" then my app is open.
Here my app is not open directly search in search bar.
So what's problem here.
Note: My app is not available in play store yet.
Related
I am pretty sure that I successfully connected to Whatsapp Web from a mobile browser an year or two back. I opened the site www.web.whatsapp.com, the usual desktop interface showed up, and I scanned the QR code using a whatsapp account on another phone, and I was logged in from the mobile browser just as I'd be from a desktop browser.
When I try it these days, as of 2020, it doesn't happen. The url www.web.whatsapp.com is automatically and invariably redirected to www.whatsapp.com.
Did they purposely block this avenue, or is it something to do with my devices?
Was this feature undesirable to Whatsapp in any way?
You have to tell your browser to open it as a desktop site.
On iPhone: click on Aa letters in the browser and click "Request Desktop Website".
On Android: click on three dots in the URL section and check "Desktop site".
I am working on Google Action for smart devices and using Dialogflow interaction schema with Java fulfillment. Fulfillment should call third party API to complete requests. For the purpose of the task, I must use a custom OAuth server. According to docs, I filled Action Account Linking information in Action Console with Grant Type: Authorization Code. For all intents including Welcome "Sign in required" is set.When testing with Google Home device or Google Home surface in Simulator menu, I get clear message "It looks like your Demo Service account is not linked yet. You can link Demo Service to your Google Account from the Google Home app." And as expected I get Linking Card in Google Home App to login and get AccessToken for third party service. Everything is OK here.
But when using Telegram integration or Phone surface in Simulator I just get "It looks like your Demo Service account is not linked yet" and nothing happen neither in Telegram, nor in Google Home App. How should user authentication for third party service be managed in this case?
Using the Actions on Google simulator, when you get the "It looks like your Demo Service account is not linked yet" you can achieve account linking by clicking on the DEBUG tab then open in a browser the url in "debugInfo". (See below)
The Phone surface simulates the Google Assistant app on Android or iOS devices. Users on these platforms will be prompted directly for account linking. (See below image)
Is it possible to install a Dialogflow chatbot for testing on my Google Home device
without using the phrase "Talk to my test app?"
I am a rather new user of Dialogflow and have several simple test apps that
I plan to develop as learning exercises. Can set them up for testing on my
personal Google Home device without entering the "Talk to my test app" and without
submitting them for distribution to the Google Home community. I do not consider them
sinificant enough to offer them the the Google community at large.
I anticipate the develop of the following apps: 1 - SillyNameMaker, 2 - Woodchuck,
Gettysburg Address.
Thanks for any help
Jim
If you provide an app name and sample invocations in the "App information" section of the Actions on Google console, you'll be able to use this name to invoke your app on devices that are signed in to the Google account you are using for development.
One thing to note, however, is that you can only have one app in testing at a time. If you start testing a new app, the previous one (even if it is named) will be unavailable.
We are setting up a web app which serves as a wi-fi hotspot using coova chilli and the Javascript Facebook SDK.
The app has a "login with facebook" button that, once clicked, calls the FB.login() function, which opens a pop-up window where the user can insert his credentials and log in.
This solution is working correctly in desktop browsers but it's not working in mobile devices.
These are the problems I encountered:
Android device - When I connect to the wifi network, the system prompts a notification who says "Sign in to wifi network". Once clicked, the captive page opens up correctly. But when I click the fb login button, I am redirected to the url "http://m.facebook.com/v2.8/auth ..." which is correct, but then the windows freezes and I can see only a wsod.
IOS device - same as before, the cna triggers, the redirect to the fb login page works, but once I insert my credentials, the only thing I can see is a wsod.
Both issues can be bypassed by including apple.com, google.com and other domains used for auth in the hotspot walled garden, and then the user can log in to the network by using the device's browser - Safari or Chrome, it works - as pointed out in this discussion Facebook login on Apple CNA.
The thing is, we want to make it work on the "normal" workflow, that is, to make the app work correctly within the IOS captive network assistant and the Android "sign in to wi fi" functionality.
Do you have any idea how can we solve this? We searched far and wide without any success. Thank you.
EDIT
Solved by using PHP SDK instead of javascript. By generating a login link as explained here. This works also on mobile captive portal assistants such as ios and android ones because the fb login page is opened in the same window and not in popup/iframe. I hope this helps others that may encounter the same problem.
When debugging a GDAA app, I need to re-test a "brand new account" situation. I.e. getting the dialog that asks user to allow the Drive access:
"[YourApp] would like to: View and manage Google drive files that you
have opened or created by this app"
Is there a re-set method that would get me back to ground zero?
You can reset this via the Drive "manage apps" page on the web. Disconnect the app from your drive.
Have a look at the 'Google Settings' app on your device, in the 'Connected apps' section you should be able to select and disconnect your app. At least for other kinds of permissions (e.g. contacts), allowed apps show up there.
Edit: The same can be done via the web here.