Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

whatsapp popup shows error #157

Open
dillon opened this issue May 25, 2018 · 3 comments
Open

whatsapp popup shows error #157

dillon opened this issue May 25, 2018 · 3 comments

Comments

@dillon
Copy link

dillon commented May 25, 2018

Everything's working perfectly except for my whatsapp button. I've tested on iOS and Firefox 60

browser popup attempts the following URL
whatsapp://send?text=I%2520filled%2520out%2520my%2520Midterm%2520Elections%2520voting%2520card%2520at%2520Example.com%20https%3A%2F%2Fgithub.com

On Firefox 60, this Firefox error fills the popup
"The address wasn't understood: Firefox doesn't know how to open this address, because one of the following protocols (whatsapp) isn't associated with any program or is not allowed in this context. You might need to install other software to open this address."

On iOS, it seems to bring me to the exact correct page, but still has an error overlay that I have to click away from.

I'm using react-router-dom with create-react.

@dillon dillon changed the title whatsapp popup shows error in firefox and iOS whatsapp popup shows error May 25, 2018
@murilomentor
Copy link

For me it works fine on Google Chrome, but I get the same error while trying to send from Firefox.
When I use Chrome the url path in the address bar starts with: https://api.whatsapp.com/send?...
But on Firefox the url path starts with whatsapp://send?...

@cborboni
Copy link

I have the same problem in Safari, due to the address that starts with whatsapp:// protocol.
I found this article that maybe can help:
https://medium.com/@jeanlivino/how-to-fix-whatsapp-api-in-desktop-browsers-fc661b513dc

@MadalenaGoncalves
Copy link

Hi there! I am seeing the same problem, both in Firefox and in Safari (desktop). I saw in #196 and in #194 that a possible solution is already merged but not yet released. Any idea when will be the next release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants