[ANR]: Broadcast of Intent { act=com.google.android.c2dm.intent.RECEIVE cmp=com.onesignal.notifications.receivers.FCMBroadcastReceiver }

[ayushi-sk]

What happened?

This issue is affecting users in a production track, and should be prioritized

Steps to reproduce?

- OneSignal.initWithContext(applicationContext, ONESIGNAL_APP_ID)
- ANR was detected during the app startup process.

What did you expect to happen?

no ANRs please!

OneSignal Android SDK version

Release 5.1.34

Android version

14

Specific Android models

Relevant log output

at java.lang.reflect.Executable.getSignatureAnnotation (Native method)
  at java.lang.reflect.Executable.getSignatureAttribute (Executable.java:713)
  at java.lang.reflect.Executable.getMethodOrConstructorGenericInfoInternal (Executable.java:699)
  at java.lang.reflect.Executable.getGenericParameterTypes (Executable.java:270)
  at java.lang.reflect.Constructor.getGenericParameterTypes (Constructor.java:164)
  at com.onesignal.common.services.ServiceRegistrationReflection.doesHaveAllParameters (ServiceRegistration.kt:101)
  at com.onesignal.common.services.ServiceRegistrationReflection.resolve (ServiceRegistration.kt:62)
  at com.onesignal.common.services.ServiceProvider.getServiceOrNull (ServiceProvider.kt:79)
  at com.onesignal.common.services.ServiceProvider.getService (ServiceProvider.kt:67)
  at com.onesignal.common.services.ServiceProvider.getService$com_onesignal_core (ServiceProvider.kt:35)
  at com.onesignal.internal.OneSignalImp.initWithContext (OneSignalImp.kt:212)
  at com.onesignal.OneSignal.initWithContext (OneSignal.java:135)

Code of Conduct

• I agree to follow this project's Code of Conduct

[ayushi-sk]

at com.onesignal.notifications.internal.bundle.impl.NotificationBundleProcessor.processBundleFromReceiver (NotificationBundleProcessor.kt:77)

[jinliu9508]

@ayushi-sk Thank you for reporting this! This appears to be an ANR caused by the use of reflection. We will look into it and share updates here.

[ayushi-sk]

Any updates?

[jinliu9508]

@ayushi-sk Thank you for your patience. We've identified that this issue is related to a method introduced in version 5.1.34 that is incompatible with Gradle version 7 and below. The issue has been resolved in our latest release, version 5.1.35. Please try upgrading to this version and let us know if it resolves the problem on your end.