-
Notifications
You must be signed in to change notification settings - Fork 376
Open
Labels
Description
What happened?
We updated to 5.4.0 and see a new crash in firebase: We haven't changed our init code in 2 years, the only change was updating from 5.1.37 to 5.4.0
Caused by java.lang.IllegalStateException
initWithContext was not called or timed out
com.onesignal.internal.OneSignalImp.waitForInit (OneSignalImp.kt:339)
com.onesignal.internal.OneSignalImp.waitAndReturn (OneSignalImp.kt:393)
com.onesignal.internal.OneSignalImp.getLocation (OneSignalImp.kt:123)
com.onesignal.OneSignal.getLocation (OneSignal.kt:70)
OurApplication.configureNotificationsService (OurApplication.kt:276)
OurApplication.onCreate (OurApplication.kt:141)
android.app.Instrumentation.callApplicationOnCreate (Instrumentation.java:1381)
private fun configureNotificationsService() {
OneSignal.initWithContext(this, BuildConfig.ONESIGNAL_API_KEY)
OneSignal.Location.isShared = false // https://github.com/OneSignal/OneSignal-Android-SDK/issues/1821
OneSignal.Notifications.addClickListener(PushNotificationOpenedHandlerObserver(this))
OneSignal.User.pushSubscription.addObserver(pushNotificationSubscriberObserver)
registerInAppPushNotificationChannels()
}
Steps to reproduce?
1. Update from 5.1.37 to 5.4.0
2. Launch AppWhat did you expect to happen?
I expected the app not to crash on ini
OneSignal Android SDK version
5.4.0
Android version
15
Specific Android models
Event summary
OS version: android16
Model:Moto G Power - 2025
Date:Nov 11, 2025, 1:18:12 AMRelevant log output
Code of Conduct
- I agree to follow this project's Code of Conduct
jvanderwee, kk-atom, HOLIESTAR, SUKI-Huang and dagerler001