[v0.74] Android: Promises from native modules stuck about react-native HOT 12 OPEN

Hey @cortinico , any thoughts about this one?

I'd say, let's start by attaching a reproducer to this issue. This week we're all busy with ReactConf so we won't be able to take a look at it

from react-native.

This week we're all busy with ReactConf

I hope, ReactConf was fun :)

Regarding my issue — following the trial-and-error approach, I tried to comment out different parts of my app relying on different 3rd party libraries, and narrowed it down to react-native-google-mobile-ads — if I don't use any functionality from it, my app works fine. Though, while I was testing that library got some fixes... thus, I am still to try whether the problem is there with v13.3.1 of that library, and if so, what might be causing it.

from react-native.

from react-native.

from react-native.

Hey @cortinico , any thoughts about this one? I am not sure what can I do — I can't get Android Studio debugger to work on C++ RN code; I don't see any apparent issues with my code on TS & Java side; and although the issue reliably happens shortly after the app start-up, it is not in an deterministic way, sometimes I get it sooner, sometimes later.

It feels like perhaps some dependency in the app, not correctly migrated to the new arch, does something wrong with communications to the native layer, and somehow rapidly exhaust the ability of bridgleless communication to handle new callbacks / promises... but I don't see anything in adb logcat logs, or app behavior hinting on where to look for the problem (though my first guess would be react-native-webview, or @react-native-firebase to blame — both poorly maintained, and using some weird patterns in their code, which I haven't seen in RN docs).

from react-native.

@cortinico I have narrowed it down to the issue still happening with react-native-google-mobile-ads v13.3.0, and the issue not present after it upgrade to v13.3.1 and above. The only code change between these versions seems to be a change in event name: invertase/react-native-google-mobile-ads@v13.3.0...v13.3.1

I am not sure why that event name was changed, and how may it affect unrelated promises not being resolved in the bridgeless mode. Though, if it makes any sense, I'd say RN misses to detect some problem here, and warn about it, or probably throw a hard error.

from react-native.

@birdofpreyru, it's very tough for us to diagnose this issue without code examples, or a reproducer.

I strongly urge you to to create a minimal reproducer! I think that'll be the quickest way to see this problem resolved.

from react-native.

Hi, I don't have a minimal reproducer but I do want to chime in that I believe I also have this issue on ios. When bridgeless is on my promises that cross the bridge do not resolve, but with bridgeless off they do resolve

from react-native.

@chrisnojima @birdofpreyru Thanks for reporting this. We are very committed in fixing this, but as @RSNara mentioned, it is really hard for us to figure out what's going on without a reproducer.
If it helps, you can start from this template and you can create a simple app that send over a promise?
Is it ok if you need some libraries to do so.

from react-native.

Understood, unfortunately I don't have free time to invest into it now, especially once it is not a problem for my projects anymore. Just saying in case somebody else facing the issue has doubts whether to look into creating a repro, or wait till the issue reporter does so :)

from react-native.

One more piece of random data, when I switched my ios build to bridgless + hermes it worked fine. Its only the combination of JSC + bridgeless that has the issue. JSC/Hermes old bridge / old arch is also fine.

from react-native.

@chrisnojima I have experienced it with Android + Bridgeless + Hermes. As I said above, for me it was caused by [email protected], so perhaps a good first take on repro would be to try upgrading & running the example app of that lib version with RN v0.74 / Android / Bridgeless / Hermes, and see how that behaves; and as I said, it might take me a while to actually try it.

from react-native.