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
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.
The text was updated successfully, but these errors were encountered:
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
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.
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-0388This 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.
The text was updated successfully, but these errors were encountered: