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
[ x] I have searched for a similar issue in the project and found none
Environment details
Info
Value
iOS Version
18.1
Quickblox iOS SDK version
2.20.0
QuickbloxWebRTC SDK version
3.1.0
Xcode Version
Xcode 16.1
Repro with our demo sample
e.g. does it happen with our demo sample? Yes
Did this work before?
Not sure
Actual behavior
App is not receiving chat push notifications. When I send chat in Debug build, chat push notifications are delivered to the app. But not when shared Release build.
I don't have logs for the release build.
Steps to reproduce the behavior
Just generate a Release build and install that build on your iPhone. Send a Chat message from another phone; the app will not receive a chat push notification, though it is receiving a chat message. But I want push notifications as well.
Any other comments
I am using the FREE Starter plan. Will it be that blocking to send push notifications? I read this from the StackOverflow link. https://stackoverflow.com/a/45327276/2530570
The text was updated successfully, but these errors were encountered:
New Issue Checklist
Environment details
Did this work before?
Not sure
Actual behavior
App is not receiving chat push notifications. When I send chat in Debug build, chat push notifications are delivered to the app. But not when shared Release build.
I don't have logs for the release build.
Steps to reproduce the behavior
Just generate a Release build and install that build on your iPhone. Send a Chat message from another phone; the app will not receive a chat push notification, though it is receiving a chat message. But I want push notifications as well.
Any other comments
I am using the FREE Starter plan. Will it be that blocking to send push notifications? I read this from the StackOverflow link.
https://stackoverflow.com/a/45327276/2530570
The text was updated successfully, but these errors were encountered: