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

useFcmV1 must be a boolean error #33

Open
Brune04 opened this issue May 15, 2024 · 1 comment
Open

useFcmV1 must be a boolean error #33

Brune04 opened this issue May 15, 2024 · 1 comment
Assignees

Comments

@Brune04
Copy link

Brune04 commented May 15, 2024

After upgrading to 0.0.14 I'm now getting this error:

YieldStudio\LaravelExpoNotifier\Exceptions\ExpoNotificationsException: Expo service error: HTTP 400 response: {"errors":[{"code":"VALIDATION_ERROR","message":""useFcmV1" must be a boolean.","isTransient":false,"requestId":"6471d747-14dc-4caf-a9e1-0388

This is what my expo-notifications.php config looks like:
'use_fcm_legacy_api' => env('EXPO_USE_FCM_LEGACY_API', false),

and this is what I have in my .env
EXPO_USE_FCM_LEGACY_API=true

I also tested just putting true and just putting false in the expo-notification.php file. It works fine whenever I put false, but not whenever I put true.

@Brune04 Brune04 changed the title YieldStudio\LaravelExpoNotifier\Exceptions\ExpoNotificationsException: Expo service error: HTTP 400 response: {"errors":[{"code":"VALIDATION_ERROR","message":"\"useFcmV1\" must be a boolean.","isTransient":false,"requestId":"6471d747-14dc-4caf-a9e1-0388 useFcmV1 must be a boolean error May 15, 2024
@joemugen
Copy link
Contributor

Thanks for the assignment as, after a quick check, the problem seems more complicated than expected 😓
I'll give a look ASAP.

From what I tested, the useFcmV1 is a query param with the value true or false but as a string (since it's a query param). I don't know why we'd get this validation error then...
Hope to have good news soon.

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

2 participants