FCM plugin exception - Namespace SPRINGBOARD, Code 0x8badf00d

[andrehtissot]

FCM plugin exception - Namespace SPRINGBOARD, Code 0x8badf00d

[meghanadixit1]

Hi,
Thanks for reverting back!!

Below is a demo repo created. In this new project, only FCM plugin is installed and on launch the app is crashing
https://github.com/meghanadixit1/FCMDemo

When for the first time, app is installed to the device via xcode, it works well, for the subsequent launches, it crashes everytime.

Since it is crashing on app launch, we are not able to test any functionality.

Attached are the XCode logs and the mobile device logs and my environement info

IonicInfo.docx
FcmDemoLog.docx

Please let me know if any other info is required.

.

[andrehtissot]

The thread dying is concerning, yes, but did experience functionality issues?

Would you be able to share a repository of which the app presents this error?

I'll investigate as soon as possible.
But until then, if you can send your findings.

Thank you

[andrehtissot]

I've found the thread firebase/firebase-ios-sdk#1399 that mentions that, this issue occurs due to keychain deadlocks.

I'll investigate possible solutions.

[meghanadixit1]

Hello There,
Any updates on this??

[andrehtissot]

Hi, I've written a simple experiment, that just delay the Firebase initialisation by 10 seconds. Just to check if a solution like this could work in your case (master...andrehtissot:delayed-firebase-initialization-experiment).

So, from the root app directory, execute something like:

cd ..
git clone https://github.com/andrehtissot/cordova-plugin-fcm-with-dependecy-updated.git
cd -
cd ../cordova-plugin-fcm-with-dependecy-updated
git checkout delayed-firebase-initialization-experiment
cd -
ionic cordova plugin remove cordova-plugin-fcm-with-dependecy-updated
ionic cordova plugin add ../cordova-plugin-fcm-with-dependecy-updated

And please let me know if the crashes still happen.

[meghanadixit1]

Will check and revert to you!
Thanks

[meghanadixit1]

Hi There, With this workaround, now on iOS device, no crash is observed. However, when the same plugin is used while building android app, we ran into below issue D8: Program type already present: android.support.v4.app.INotificationSideChannel FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.

com.android.builder.dexing.DexArchiveMergerException: Error while merging

dex archives: Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes. Program type already present: android.support.v4.app.INotificationSideChannel * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. * Get more help at https://help.gradle.org BUILD FAILED in 2m 14s

Task :app:transformDexArchiveWithExternalLibsDexMergerForDebug FAILED

35 actionable tasks: 9 executed, 26 up-to-date (node:10136) UnhandledPromiseRejectionWarning: Error: F:\orciFcm\OrciCare\platforms\android\gradlew: Command failed with exit code 1 Error output: Note: Some input files use or override a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: Some input files use unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. D8: Program type already present: android.support.v4.app.INotificationSideChannel FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.

com.android.builder.dexing.DexArchiveMergerException: Error while merging

dex archives: Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes. Program type already present: android.support.v4.app.INotificationSideChannel * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. * Get more help at https://help.gradle.org BUILD FAILED in 2m 14s at ChildProcess.whenDone (F:\orciFcm\OrciCare\node_modules\cordova-common\src\superspawn.js:135:23) at ChildProcess.emit (events.js:210:5) at ChildProcess.cp.emit (F:\orciFcm\OrciCare\node_modules\cross-spawn\lib\enoent.js:34:29) at maybeClose (internal/child_process.js:1021:16) at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5) (node:10136) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:10136) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. With FCM plugin version 4.2.0 android app is built successfully.

…

On Tue, 7 Apr, 2020, 16:34 André Tissot, ***@***.***> wrote: Hi, I've written a simple experiment, that just delay the Firebase initialisation by 10 seconds. Just to check if a solution like this could work in your case ( master...andrehtissot:delayed-firebase-initialization-experiment <master...andrehtissot:delayed-firebase-initialization-experiment> ). So, from the root app directory, execute something like: cd .. git clone https://github.com/andrehtissot/cordova-plugin-fcm-with-dependecy-updated.gitcd -cd ../cordova-plugin-fcm-with-dependecy-updated git checkout delayed-firebase-initialization-experimentcd - ionic cordova plugin remove cordova-plugin-fcm-with-dependecy-updated ionic cordova plugin add ../cordova-plugin-fcm-with-dependecy-updated And please let me know if the crashes still happen. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIWHZR37IDTBOP5LKLZCQ2LRLMCDLANCNFSM4LYSY73A> .

[andrehtissot]

This is an error due to Androidx migration.

I suggest you to try some of the solutions found in https://stackoverflow.com/questions/51918301/program-type-already-present-android-support-v4-app-inotificationsidechannelst.

If those don't work, let me know, then you might have to use a special version of the plugin, of which won't require androidx, by not importing androidx.core.app.NotificationCompat.

[andrehtissot]

But it's good to know that this solution avoids crashing on iOS.

In the near future, I intend on implement the feature requested in #31, which, in theory would also fix the issue you found.

[meghanadixit1]

HI

Tried the solution in below link-
https://stackoverflow.com/questions/51918301/program-type-already-present-android-support-v4-app-inotificationsidechannelst.

But still could not be successful.
ALso tried something as below

arnesson/cordova-plugin-firebase#1083 (comment)

But then also ran into an error

[andrehtissot]

I'll try to minimize the reliance on AndroidX dependency to avoid these compatibility issues. I'll update here, when I get it working.

[andrehtissot]

Also, just to let you know, a small delay was added to the main release version, so the first issue you mentioned (ios thread crashing), should not occur anymore.

[andrehtissot]

Hi @meghanadixit1, I published a new version of cordova-plugin-fcm-with-dependecy-updated@beta, which, besides a lot refactoring on the ios side, has fewer androidx dependencies.

Would you give it a try, and let me know if it fixes the build on Android, and if for iOS it still works as expected?

[andrehtissot]

The new release v5.0.0 has the changes I mentioned.

[andrehtissot]

Issue closed due to inactivity.

[meghanadixit1]

Hey,
Sorry about the delayed response -
Here is the observation -
With the code in branch "delayed-firebase-initialization-experiment" the code builds and notifications are also received.
But when tested with below versions-

V5.0.0 beta
V5.0.0
V5.1.0
V6.0.0
V6.0.1

The code is built but notification is not received in iOS devices.
Can you please look into further.