Closed sweatherall closed 3 years ago
@sweatherall Thanks for reporting, it seems the OneSignal-Android-SDK is not correctly handling the dot class name shorthand naming.
If you fully namespace the class it should resolve your issue.
<meta-data
android:name="com.onesignal.NotificationServiceExtension"
android:value="com.truckmap.truckmap.NotificationServiceExtension" />
@jkasten2 wow thanks! That indeed fixed it!
I can see that OneSignal gets initialized now with no errors, however now I am receiving no feedback (no logcats) when I send a notification from the OneSignal dashboard, and I don't actually receive any notifications on device.
I will close this issue, but I'm wondering if anyone has any insight on what I can do to debug this new problem?
Description: I am upgrading an app from OneSignal v3 -> v4, and I am following these instructions to implement the functionality of receiving a push notification while the app is in background on Android. However, there is an issue during initialization where it is not finding/initializing my
NotificationServiceExtension
class, and I'm not sure why.Environment RN: 0.66.3 react-native-onesignal: 4.3.3 installed via npm
Steps to Reproduce Issue:
Logcats on app start up:
NotificationServiceExtension.java:
AndroidManifest.xml:
So OneSignal Android SDK is
attempting to call constructor
, but a system error gets thrown right after. Sometimes it logs out specifically aClassNotFoundException
error.Is there anything I can do to help debug this? Please let me know what other info I can provide! Thanks