-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐛] Bug: Error receiving firebase push notification in background #8091
Comments
As far as I understand this is not an error in this repo and we need an upstream fix. |
Note the implication of this is that you cannot use fabric / react-native 0.76 until this is fixed upstream, assuming I understand it correctly. Notifee is waiting on the same issue (invertase/notifee#1077) |
We'll ship that in 0.76.1 which will be out in the next days |
@cortinico can we also expect the fix in next minor release for 0.75? |
@ravindraguptacapgemini you probably want to have that discussion on the reactwg repo issue, it's not really a fit for here I'm thrilled to hear it is about to land though, thanks! |
FYI: I tested it with the new react-native 0.76.1 version and have the same error.
The background message handler seems to have been executed, but the crash still occurs. Reference: facebook/react-native#47570 |
@mbpictures hmm 🤔 thanks for testing - that's unexpected, I was under the impression that should be working in 0.76.1 and that 0.76.2 was the hopefully-final fix to get setTimeout working (reactwg/react-native-releases#617) This may need more investigation - @lovegaoshi apologies for the ping but do you continue to have headlessJS issues in 0.76.1 besides setTimeout, or is it working for you? |
callstack? submitted a pr for the settimeout issue and afaict rntp works
fine with that, though im having material-top-tab not able to navigate
completely in the new arch right now, and forced to stay in old (totally
unrelated to headlessJs, but im quite disappointed in how many things still
break with the new arch)
…On Tue, Nov 12, 2024, 4:59 AM Mike Hardy ***@***.***> wrote:
@mbpictures <https://github.com/mbpictures> hmm 🤔 thanks for testing -
that's unexpected, I was under the impression that *should* be working in
0.76.1 and that 0.76.2 was the hopefully-final fix to get setTimeout
working (reactwg/react-native-releases#617
<reactwg/react-native-releases#617>)
This may need more investigation - @lovegaoshi
<https://github.com/lovegaoshi> apologies for the ping but do you
continue to have headlessJS issues in 0.76.1 besides setTimeout, or is it
working for you?
—
Reply to this email directly, view it on GitHub
<#8091 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZMOVVTK6EVDODXLAEAHRRL2AH3STAVCNFSM6AAAAABQV26G3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZQGQ3DONZYHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Looks like we have a reproducer on upstream issue with 0.76.1 -- facebook/react-native#47570 - thanks to mbpictures - so we do still have some issues I suppose the only workaround at the moment is to disable new architecture on android if you are using headlessJS |
Per extensive repro attempts in linked issue+comment, I can no longer reproduce a problem with new architecture facebook/react-native#47570 (comment) I'm very curious to know of any reproduction if one exists, will investigate more if so (note that old architecture has a problem with receiving background FCM now, so you win some and you lose some) |
Crossposting from facebook/react-native/issues/46775 issue of the react-native repo. All credits go to the original author! Reproduction repo available here: https://github.com/DmytroKoblents15/notificationsReproduce
Issue
Getting error Error: Exception in HostFunction: Could not enqueue microtask because they are disabled in this runtime, js engine: hermes when receiving background message from firebase on react native after updating to 0.75.3 with newArch and hermes enabled. If I disable the new arch or rollback to RN 0.74 error doesn't show up
Project Files
Javascript
Click To Expand
package.json
:firebase.json
for react-native-firebase v6:# N/A
iOS
Click To Expand
ios/Podfile
:AppDelegate.m
:Android
Click To Expand
Have you converted to AndroidX?
android/gradle.settings
jetifier=true
for Android compatibility?jetifier
for react-native compatibility?android/build.gradle
:android/app/build.gradle
:android/settings.gradle
:MainApplication.kt
:AndroidManifest.xml
:Environment
Click To Expand
react-native info
output:react-native-firebase
version you're using that has this issue:21.0.0
Firebase
module(s) you're using that has the issue:messaging
TypeScript
?Y
React Native Firebase
andInvertase
on Twitter for updates on the library.The text was updated successfully, but these errors were encountered: