-
Notifications
You must be signed in to change notification settings - Fork 26
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
Foreground Push Notifications (Android) #358
Comments
Hello @peterkuiper, Are you experiencing this issue only on Android, or does it affect both platforms? Can you elaborate more on ‘foreground Push Notifications are “hijacked” by Additionally, could you please share your SDK initialization code with us?
|
Hi @peterBrxwn We are only experiencing this on Android, iOS works fine. As said, we are using Expo Push Notifications. Without the With the This is the init function:
These methods aren't called anywhere in our code:
We only use the |
Hi @peterkuiper, Thank you for your prompt response. Quick question: What version of the Countly SDK are you using? |
@peterBrxwn I tried until version |
@peterBrxwn Any updates on this yet ? thanks! |
We are currently investigating the issue. We will provide an update as soon as possible. |
Hi @peterBrxwn ! |
Hello @pavelPX, |
Great news! Thank you @peterBrxwn |
In an Expo project I am working on, foreground Push Notifications are "hijacked" by
countly-sdk-react-native-bridge
on Android. After removingcountly-sdk-react-native-bridge
, foreground Push Notifications on Android work as expected.We only want to use certain parts of Countly, but not Push Notifications. I did not find any option to disable Push Notifications from within the
countly-sdk-react-native-bridge
package.? I tried to disable it by patching the module itself but it seems the initialization is done in the Countly Android SDK.It would be nice to be able to opt-in to the Countly Push Notifications service.
The text was updated successfully, but these errors were encountered: