Fatal error: Uncaught exception 'RuntimeException' with message 'Curve curve

[akhilesh-kk2]

Hi,
Issue is already raised at #14

I tried to send push using V4, but code throwing new error messages. Please find error message below.

1. Warning: hex2bin(): Hexadecimal input string must have an even length in C:\xxxxxx\web-push-php-example\vendor\minishlink\web-push\src\Utils.php on line 60

2. Warning: hex2bin(): Hexadecimal input string must have an even length in C:\xxxxxxxx\web-push-php-example\vendor\minishlink\web-push\src\Utils.php on line 61

3. Fatal error: Uncaught TypeError: bin2hex() expects parameter 1 to be string, boolean given in C:\xxxxxx\web-push-php-example\vendor\minishlink\web-push\src\Encryption.php on line 94

4. TypeError: bin2hex() expects parameter 1 to be string, boolean given in C:\xxxxx\web-push-php-example\vendor\minishlink\web-push\src\Encryption.php on line 94

[naval-goel]

i am facing the same issue. in earlier version, in more than 70% of the cases, the error was curve point error which is issue number #14 and now it is the above mentioned issue. it does not come for all subscribers but is throwing the error for more than 70% of the cases. Please help.

[Minishlink]

Please fill in the issue template. Also provide your php.ini

[akhilesh-kk2]

Hi Minishlink,
I already fill the issue template, but don't know where to check it.
Sending it again below manually.

1. Yes , I have read the README entirely
2. Yes, I have verified in the issues that my problem hasn't already been resolved
3. I am tried on both php 5.6 and php 7.1
4. installed and enabled PHP extensions : gmp, mbstring, curl and openssl
5. experiencing problems with : Chrome, Firefox
6. Features used : VAPID Support
7. Issue in php 7 is already mentioned above.
8. Issue in php 5.6 is raised at Runtime exception with Mdanter ECC library #14

[t1gor]

@Minishlink any update on the issue so far?

[RedSpeeds]

Same issue here unable to solve it

[t1gor]

If that helps someone, in my case it was an error in my code, nothing lib related. This comment actually pointer me to the right direction:

Please make sure that the user public key and user auth token are base 64 encoded (in the MIME specification RFC2045).

A frequent mistake is to encode in URL-safe base 64.

#12 (comment)