I am developing social sharing plugin where I want to share my web application url in a browser using whatsapp for mobile device. I am using below code:
"whatsapp://send?text=Hello%2C%20World!"
Using above code, when I try to share without whatsapp installed in the device, it opens up a blank page.
If the user is sharing it via whatsapp and the device doesn't have whatsapp then how can we notify the user that whatsapp is not installed or redirect user to appstore or playstore to install whatsapp?
Related
I have a web app that is for Spotify users. To authenticate Spotify it currently takes the user to https://spotify.com/en/login?... as described in the Spotify docs. It works fine but it opens Safari instead of the Spotify app. This is an issue because a user may not know their password and then abandon the onboarding flow.
Since the user will be on their phone when accessing the web app, I would prefer to open the Spotify app in order for the user to grant us access. Songkick is able to do it but they do it from an iOS app so I'm not sure if it's possible to do from a web app on mobile to Spotify iOS app.
Also, I am building on Bubble.io which is a no-code builder. I am able to open the Spotify app directly from my web app by using https://open.spotify.com/artist/{artist_id} but that does not seem to work for authenticating.
I am building an app using Expo/React-Native for multiple platforms using OAuth2 as AuthProvider.
So far, successfully logging in on android devices, web browsers (Chrome, Edge), iOS devices.
But unfortunately, I have an issue completing logging in on electron/desktop app.
I am directed to OAuth2 server (using promptAsync from Expo Api/AuthSession)
, and successfully logging in, but not being redirected into my desktop app. Once the credentials are successfully entered on the popup dialog, the login popup dialog should redirect back to the app so I can use ‘code’ to get to access_token.
Sample project here.
How do you expo AuthSession.useAuthRequest to complete login from electron?
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".
Good Day
I had a Whatsapp API I used in a URL to send a Whatsapp to a specific person or group in my contact list. Below is the code I used.
https://api.whatsapp.com/resolve?deeplink=/%3Ftext%3D%252AeTrack%2BNational%2BLookout%253A%252A
It normally worked fine and no issues. Now looks like Whatsapp page has been removed. I need a similar external link to send messages from my PHP page to a whatsapp contact or group. We use either Whatsapp Web or their Downloaded app on Windows. On our Android phones the link still works and opens Whatsapp and we can select the recipient. But using Chrome and a Windows system it does not open Whatsapp anymore.
I have implemented the Google maps iframe embed api to my website, the map API is working correctly on desktop web browsers as well as Google Chrome for mobile.
However when i attempt to view the page of my site with the API on in mobile safari on iphone i get an error saying;
"The Google Maps API server rejected your request. This IP, Site or mobile application is not authroised to use this API key".
I Have enabled Google Map API for IOS on the google developer console and the issue still hasnt gone away. As i said the API works fine on other mobile browsers.
Does any one have any suggestions how to fix this?
Thanks, Martin
Did you create a new Client ID?
Handheld devices require "Installed Application" Client ID, not "Web Application. "