forcedotcom / SalesforceMobileSDK-Android

Android SDK for Salesforce
Other
341 stars 386 forks source link

Crash on Android 14 devices [One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts] #2530

Closed ashish-kumar1994 closed 6 months ago

ashish-kumar1994 commented 6 months ago

Please fill out the following details:

  1. Version of Mobile SDK Used: 10.2.0
  2. Issue found in Native App or Hybrid App: React Native
  3. OS Version: Android
  4. Device: Android 14 (API 34)
  5. Steps to reproduce: While running the app is not open
  6. Actual behavior: Crash
  7. Expected Behavior:Open the App
  8. Error Log: at com.salesforce.androidsdk.app.SalesforceSDKManager.(SalesforceSDKManager.java:273) at com.salesforce.androidsdk.smartstore.app.SmartStoreSDKManager.(SmartStoreSDKManager.java:74) at com.salesforce.androidsdk.mobilesync.app.MobileSyncSDKManager.(MobileSyncSDKManager.java:58) at com.salesforce.androidsdk.reactnative.app.SalesforceReactSDKManager.(SalesforceReactSDKManager.java:66) at com.salesforce.androidsdk.reactnative.app.SalesforceReactSDKManager.init(SalesforceReactSDKManager.java:72) at com.salesforce.androidsdk.reactnative.app.SalesforceReactSDKManager.initReactNative(SalesforceReactSDKManager.java:90)
brandonpage commented 6 months ago

Hi @ashish-kumar1994, this only happens if target/compile for API 34. If you target API 33 the app will run without crashing on Android 14/API 34. React Native did not backport this fix far enough to support the version we were using and we could not upgrade until a major release due to large breaking changes (Grade 8 + Java 17). Non React Native apps can target API 34 on the current release, Mobile SDK 11.1.

This issue is isolated to React Native but will be fixed with the release of Mobile SDK 12.0 next month.

roshanmtx commented 5 months ago

@brandonpage can you please let me know when Mobile SDK 12.0 will be released? I have one crucial release pending.

mahipalsingh-syt commented 4 months ago

issue reproducible in 12.0.1: one of RECEIVER_EXPORTED or receiver_not_exported should be specified when a receiver isn't being registered exclusively for system broadcasts