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
I moved my app to use Firebase instead of APNS for iOS devices, and it was working with the legacy FCM API. After updating to the new HTTP v1 API notifications no longer go to iOS devices. Android devices work as expected.
When sending from the Django admin I get an 'All messages were sent.' success message, and when sending from the command line using send_message I get a success response as well.
I took the device registration ID for my iOS test device and sent a message using the firebase console and the notification worked. So the configuration is correct on that side, is there anything additionally that needs to be done in Django?
The text was updated successfully, but these errors were encountered:
The way it gets wrapped in message is wrong now, one way to circumvent that is wrap this in a message directly as the send message special cases that type.
Something like this :
m = messaging.Message(notification=messaging.Notification(title="Title", body="body"))
should work both on iOS and Android.
note: If you need to send high volumes of message the HTTP v1 API is slow as there is no batching endpoint, and the firebase SDK doesn't use HTTP/2 yet.
I moved my app to use Firebase instead of APNS for iOS devices, and it was working with the legacy FCM API. After updating to the new HTTP v1 API notifications no longer go to iOS devices. Android devices work as expected.
When sending from the Django admin I get an 'All messages were sent.' success message, and when sending from the command line using send_message I get a success response as well.
I took the device registration ID for my iOS test device and sent a message using the firebase console and the notification worked. So the configuration is correct on that side, is there anything additionally that needs to be done in Django?
The text was updated successfully, but these errors were encountered: