React-native-firebase: [🐛] NPM package '@react-native-firebase/messaging' depends on '@react-native-firebase/app' v8.4.2 but found v8.4.3

[lorenc-tomasz]

NPM package '@react-native-firebase/messaging' depends on '@react-native-firebase/app' v8.4.2 but found v8.4.3

[mikehardy]

Yes! Sorry about that. Something isn't quite right with the publish from #4275 - I'm not sure what happened.

Please know that it shouldn't be a problem this time but yes it should be fixed, that's on me, I'll sort it out when I get a moment but it will likely be a day or three

[lorenc-tomasz]

@mikehardy Thank you for answer :)) And sorry for that short description.

[mikehardy]

haha it was nevertheless complete. Still hoping to get this early next week, launching other stuff today

[sangameshrently]

@mikehardy : is that just warning message ? for me ios app is getting crashed on launch.

[mikehardy]

@sangameshrently This is just a warning. Your crash will be unrelated.

[ArrudaWillyan]

I have the same problem. When i execute npx react-native run-android the app run without problems en real device, but when i execute npx react-native run-android --variant=release to build an android release return build filed with

Task :app:packageRelease FAILED
ReactNativeFirebase WARNING: NPM package '@react-native-firebase/storage' depends on '@react-native-firebase/app' v8.4.2 but found v8.4.3, this might cause build issues or runtime crashes.

@mikehardy Can this apply to the same issue or should be another section?

I have the same problem, does anyone have any solutions?

[mikehardy]

THIS IS A WARNING. It is not the source of your problem.
If app:packageRelease FAILED you are looking for a FAILURE, an ERROR, not a WARNING

I am SHOUTING because if you are attributing your problems to this you are wasting your precious time while you have a real problem somewhere else, and I know that for me at least when I am troubleshooting - especially a build failure! - I have no time to waste.

Look in other areas for your problem. The peer dependency warning here is not your problem.

[ArrudaWillyan]

@mikehardy
I'm not getting a compilation error, I apologize for the mistake. However, my release version is always closed when running the generated apk on a device. During debugging the application runs smoothly, however after following the documentation to generate a signed apk I am unable to run it on devices. The only north I have is this warning that I always receive at the terminal after running gradlew clean or npx react-native run-android --variant = release

[mikehardy]

@ArrudaWillyan you have a separate problem. It is not related to this thread - you should look through the issues and post a new one if needed, also adb logcat (watch the android device log...)

[lorenc-tomasz]

@ArrudaWillyan @cristiankmb I'm using those versions without issues. Only annoying warning ;) If I were you I would lower the packages versions and check what will happen. And then I start looking deeper into the issue. Maybe you use custom firebase library versions, etc. No idea.

PS Sorry for offtopic :(

[mikehardy]

@lorenc-tomasz that's okay - it's got the goal of saving people time (by focusing on the real problem vs this) which is valuable - that was the point of my SHOUTING above as well - I sincerely want people to fix their problems, and one of the important steps in doing so is discarding incorrect ideas. I hope to fix this actual issue soon but it should be apparent by my not having done so yet that it is not a high priority matter

[daniyal-ahmed-khan]

Did anyone figured out the solution for this ??

[codecog]

@daniyal-ahmed-khan There's no need for a solution here. It's not an error, as @mikehardy just a misstep in the publishing. You can ignore the warning for now until the next patch release is out.

[Odinwan]

guys i cant build apk because of this error

[quyetthang122]

Hi @Odinwan, you can apply this patch - link: https://github.com/invertase/react-native-firebase/actions/runs/259924803, either run update the package, I think they already fix the issue.

[daniyal-ahmed-khan]

Cant run the application it just terminates

[mikehardy]

I will repeat myself for @daniyal-ahmed-khan @quyetthang122 and @Odinwan who are not reading the comments and misdiagnosing their problems:

THIS IS A WARNING. It is not the source of your problem.
If app:packageRelease FAILED you are looking for a FAILURE, an ERROR, not a WARNING

I am SHOUTING because if you are attributing your problems to this you are wasting your precious time while you have a real problem somewhere else, and I know that for me at least when I am troubleshooting - especially a build failure! - I have no time to waste.

Look in other areas for your problem. The peer dependency warning here is not your problem.

[cxrod]

@mikehardy The last version on NPM of @react-native-firebase/messaging es 7.8.6, but in GitHub the last release es 7.8.8. The last GitHub version fix the warning? Do you know why is not published on NPM yet?

[mikehardy]

There was a publishing failure in the last release
The last github version will likely fix the warning

Do you know why is not published on NPM yet?

Because it's just me keeping the lights on here at the moment and I had a major work feature to deliver in the app I develop for money, hadn't gotten around to diagnosing what the publish failure was yet and didn't want to do a new release until I knew the root cause

Hoping to get to it in the next day or so, as well as reviewing the stack of PRs queued https://github.com/invertase/react-native-firebase/pulls?q=is%3Apr+is%3Aopen+label%3A%22Workflow%3A+Needs+Review%22 and do a release.

And I need to figure out why the patch-package task is failing https://github.com/invertase/react-native-firebase/pull/4306#issuecomment-698998034

Any contribution of effort that distributes the load here would be welcome if you want to review and test PRs etc

I'm not complaining - I enjoy working on the module, just answering your question. Help is always welcome though, sincerely

[mikehardy]

I believe I've diagnosed the root cause of the publish failure as an inclusion of workflow auto-cancel-of-prior-jobs which is normally a feature you want, but is specifically bad for our publish setup because it runs two workflows and the second was cancelling the first before it finished.

lerna http fetch PUT 200 http://registry.npmjs.org/@react-native-firebase%2ffirestore 5016ms
Error: The operation was canceled.

The good news? I've got a PR up for that in #4330 and as soon as it's approved I can merge it and release a correctly cross-dependent set of modules.

[mikehardy]

A coherently-cross-dependent set of packages exists and that should not recur
Thanks for patience, sorry for the hassle! Onwards...

[Nehal-29]

@mikehardy facing the same warnings in updated version as well.
I've both dynamic links & messaging added into my project

NPM package '@react-native-firebase/dynamic-links' depends on '@react-native-firebase/app' v8.4.6 but found v8.4.7, this might cause build issues or runtime crashes.

[!] NPM package '@react-native-firebase/messaging' depends on '@react-native-firebase/app' v8.4.7 but found v8.4.6, this might cause build issues or runtime crashes.

which version to keep?

[mikehardy]

@Nehal-29 I don't reproduce dependency warnings with https://github.com/mikehardy/rnfbdemo/blob/master/make-demo.sh using current stable versions of all releases. So the "version to keep" should be the highest version of all packages