-
Notifications
You must be signed in to change notification settings - Fork 131
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
Phone format check error with 3 comma separated numbers #478
Comments
Precisely that use case is indeed not supported. You must enter in single number when using the "Input manually" option. The value you enter for the phonenumber is checked as is by libphonenumber-for-php. For your use case you may:
|
May you please check if the last commit (1e17455) on https://github.com/kalkun-sms/Kalkun/tree/fix-478
|
Works great, thanks for the fix! |
Reopen, until this is pushed to devel (after 0.8.0 release). |
Describe the bug
When sending sms manually ("input manually") to 3 or more spanish numbers (format 600000000 or +34600000000) separated by commas this error happens: "The string supplied did not seem to be a phone number."
To Reproduce
Steps to reproduce the behavior:
Expected behavior
You should be able to send messages to 3 or more spanish numbers.
Screenshots
Browser, kalkun setup, database setup..:
0.8.0-rc-1 [Lang: spanish] [CountryCode: ES]
Linux kalkunpod 5.14.0-70.26.1.el9_0.x86_64 #1 SMP PREEMPT Tue Sep 20 17:53:31 UTC 2022 x86_64
8.0.24
MySQLi 10.9.3-MariaDB-1:10.9.3+maria~ubu2204 (mysqli)
Gammu 1.42.0, Linux, kernel 5.14.0-70.26.1.el9_0.x86_64 (#1 SMP PREEMPT Tue Sep 20 17:53:31 UTC 2022), GCC 11.2
17
Chrome 106.0.0.0
Additional context
Error happens at /application/helpers/kalkun_helper.php, line 448. It seems related to kalkun's implementation of
\libphonenumber
being unable to recognised the string as three valid phone numbers.I was able to bypass this issue by running this commands through my dockerfile & it worked, albeit it did not check the phonenumber format obviously:
The text was updated successfully, but these errors were encountered: