So if you have not chatted with a number in the past and try to chat with the number using the Whatsapp API URL: https://api.whatsapp.com/send?phone=XXXXXXXXXXXX
it gives the error "Phone Number shared via url is invalid."
Due to this have noticed all chat sender bots have stopped working on desktop.
Normally the API Link used to work perfectly fine on Desktop, but for the past 4 days it has stopped working for numbers which you have not chatted with in the past.
Change it to
https://web.whatsapp.com/send?phone=xxxxxxxxxxxx
To add a message
https://web.whatsapp.com/send?phone=xxxxxxxxxxxx&text=Hi!
Related
I'm using the link wa.me in a web application for open a chat with a message with emojis. With the message like "Hi 😉" the formed link is like this:
https://wa.me/XXXXXXXXXXXXX?text=Hi+%F0%9F%98%89
When the user opens this link on the smartphone everything is fine, but on the desktop (and WhatsApp Web) the message is sent as "Hi �"
The emoji is encoded correctly ("%F0%9F%98%89"). I found that if I use the old api.whatsapp.com/send instead wa.me, I don't have this error. Could there be something wrong when wa.me redirects to the old api.whatsapp? I'm afraid to use the api.whatsapp in production because the whatsapp documentation doesn't talk about it anymore, and can be changed without notice, I imagine.
I stumble upon this GitHub repo: Social Share URLs That has a complete and updated way of using link on how to share to different social networks.
I stopped using:
https://wa.me/XXXXXXXXXXXXX?text=Hi+%F0%9F%98%89
And now I do it like:
https://api.whatsapp.com/send?phone=XXXXXXXXXXXXX&text=Hi+%F0%9F%98%89
and it works perfectly fine with emojis! In the preview of the API webpage shows the � symbol, but when entering the Whatsapp App it shows the emoji correctly!
Last year I developed a chatbot with Microsoft Bot Framework that I integrated in the Facebook Messenger of a page. Everything worked fine until 16th of December (last successful log). The page is not used by a lot of people therefore the application might have worked also longer than that.
Today I tried to use the chatbot again and I did not get any response. In the Logs I just found the error message "Operation returned an invalid status code 'Forbidden`".
After a bit of Debugging I found out that the problem is sending messages back to the Facebook Messenger.
context.SendActivityAsync(...)
I did not change any configuration within my Azure Bot Channel registration recently. I am aware of the privacy changes within the Facebook API, but as I already struggle with sending a simple text response like "Hi" I assume that cannot be the problem. Also the permission scheme has changed for Facebook apps. I have the permission for "pages_messaging". Do I need another permission now? Or did I miss another change in the Facebook API?
Technical Details:
Facebook API Version v6 (tried also v9 but no change in behavior)
Chatbot based on .Net Core 2.1
Bot Builder SDK v 4.11
Any hints what I did wrong or where I can look for further information is much appreciated.
Edit: I tried to add a new page to my Facebook App and get following message:
There is a hint that a permission is missing, but I cannot find out which one I require. As I only send responses to FAQ's and if required handover to the customer service inbox I just requested the "pages_messaging" permission. Do I require any other permission now?
I found the problem. For everyone that might have the same problem:
In our case the administrator that added the Facebook pages to the application was removed from the admin permission list of the pages. After re-adding the admin permissions for the pages the bot started working again.
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 am developer and maintainer of an Angular web app which uses Google OAuth. This works normally.
Last week the app users (me including) started receiving standard Security alert emails from Google (no-reply#accounts.google.com) on a daily basis. The Email says "Appname was granted access to your Google account". This is of course bad signal to the users.
When clicked on "Check Activity" in the Email it always says:
Unrecognised device
X hours ago
Unknown (location)
This is the case for all users tested on many different devices and IPs.
Recently I have upgraded from Angular 5 to Angular 7 if that might help.
Also recently I noticed absolutely the same behaviour when I sign-in to Dropbox using a Gmail. The application I am responsible for is not storing session data for privacy reasons so the users are asked to Sign-in with Google every time they want to use the app. I noticed this behaviour just a week ago (devices and locations not recognised) by Google.
The google group (https://groups.google.com/forum/#!forum/oauth2-dev) redirected me to Stackoverflow. Any help is much appreciated! :)
We are sending notifications to users when they approve certain scopes. That list is expanding and more apps will see the notification.
Thanks for the feedback. Looks like the unrecognized device was an issue and we have rolled back that experiment.
Ideally an app should see the notification only once and for non basic scopes (basic scopes being email, profile etc).
I had a working hangout app until yesterday - but now now I can no longer launch the app in the developer sandbox.
In the process of diagnosing the problem I have tracked back to simply trying to launch one of the Google sample apps (https://plushangoutstarter.appspot.com/static/simpleHangoutApp.xml) in the developer sandbox.
This fails in the same way as my app: the hangout says loading app along with a lovely animation but never loads.
I have tried this from different Google accounts and OS's but the problem is the same whatever.
The js console shows the following error:
Uncaught SyntaxError: Unexpected token < login.corp.google.com/request?s=oz-autopush-full.plus.corp.google.com:443/u….google.com/js/api.js&maxAge=1200&authLevel=2000000&rpMode=v2&keyIds=Do0:2
Interestingly I can launch the hangout apps (mine and the sample ones) outside the sandbox. For example, https://plus.google.com/hangouts/_/16fae425e33645b520c4b14f71adbdbba843f00d
To me it seems as if Google has deployed a breaking change but I can't believe that there would be no activity on twitter or the google plus developer group if they had.
My questions are:
1) Can anyone launch an app in the developer sandbox
2) If not, anyone got any idea what the problem is.
Thanks in advance for any help. As usual in these situations, I was planning on demoing my app to my colleagues in a couple of days to show them how cool the hangouts api is :(
Neil
There was a problem on Google's side over the weekend and has now been corrected.