You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First up, this isn't particularly a bug with react-qr-code, but definitely something which could be added to the Readme to avoid a lot of unnecessary and confusing debugging when using this component.
When generating URL QR codes based on this library, Android devices will generally (we tried four or five different methods on various phones) refuse to parse URLs with a host name of 'localhost', giving a very unspecific and cryptic error message. Using the exact same URL (even very long URLs) with 127.0.0.1 as the host fixes this, and we couldn't reproduce it with any other host.
This does not affect iOS devices - Apple phones scanned the QR code just fine. I found basically no other discussions of troubleshooting this problem online.
Perhaps you could consider making a note in the readme of this project, as it could save people a lot of headache when trying to use this component during local testing and development.
The text was updated successfully, but these errors were encountered:
I had the same problem but thanks to your comment you saved me
In a quick search on the internet, and also using some generators, it seems that there really is a restriction on the use of the url "http(s)://localhost", which when read, does not show as a link but as text just.
First up, this isn't particularly a bug with react-qr-code, but definitely something which could be added to the Readme to avoid a lot of unnecessary and confusing debugging when using this component.
When generating URL QR codes based on this library, Android devices will generally (we tried four or five different methods on various phones) refuse to parse URLs with a host name of 'localhost', giving a very unspecific and cryptic error message. Using the exact same URL (even very long URLs) with 127.0.0.1 as the host fixes this, and we couldn't reproduce it with any other host.
This does not affect iOS devices - Apple phones scanned the QR code just fine. I found basically no other discussions of troubleshooting this problem online.
Perhaps you could consider making a note in the readme of this project, as it could save people a lot of headache when trying to use this component during local testing and development.
The text was updated successfully, but these errors were encountered: