Nicola Corti

> Our React Native project requires com.facebook.fbjni:fbjni-java-only:0.0.3 which is currently only available on jcenter. Quick update: the mentioned artifact has now been re-uploaded to MavenCentral https://repo1.maven.org/maven2/com/facebook/fbjni/fbjni-java-only/0.0.3/ @passy we should be...

Piggybacking here as we're facing the same exact issue on React Native. We're looking into consume `fbjni` as a Prefab: - https://github.com/facebook/react-native/pull/33397 I think the best approach here would be...

Following up here @cpsauer > All that said, it seems like maybe the app and using-library cases could be solved by just dynamically linking against (the same) C++ standard library...

> 👍🏻 I suppose more generally, is it clear that FBJNI should be bundling libc++_shared at all, as opposed to just requiring it? could you clarify? As I'm not sure...

> More and more libraries are built with rust these days, so it would be a real benefit to have it bundled into this container. Hi @maximilize I would suggest...

> this PR should be merged first? Correct 👍

> clean build fails To clarify, calling `gradle clean` will fail. Not a clean build (i.e. building from a clean repo). But yeah, worth to address

> Remote host terminated the handshake It seems like your failure is network related. Have you investigated why this is happening? > Is jdk8 support for a react native project...

> that the Android AVD emulator is not available for arm64 architecture and fails to install What's the failure message?

> I was trying to find an issues link for it but could not, I would be interested in reading more about it, if you find any issue to link