Nicola Corti

> If you follow the documentation creating it via terminal, are you prompted to specify the key password @cortinico? Nope. However if you're reusing a keychain created by someone else...

> I believe that is not true for JDK11 (which is recommended by [RN docs](https://reactnative.dev/docs/environment-setup)), as you can see [here](https://stackoverflow.com/questions/66621669/warning-different-store-and-key-passwords-not-supported-for-pkcs12-keystores-i). Or you can also use the options on your CLI,...

Have you looked into similar issue already solved like this one? https://github.com/facebook/metro/issues/668#issuecomment-845119616

This is probably worth to move this under github.com/facebook/metro for visibility

@motiz88 @rh389 I've moved over this from RN to Metro. Is there anything actionable on your end here?

> I think it'd be a good idea, but it's likely that you'd have to do the PR yourself to enable this. It'd probably the fastest way to get someone...

> I don't have many details myself about the reasons for not removing these components but from what I read at [facebook/react-native#23313](https://github.com/facebook/react-native/issues/23313) the original idea was to eventually remove all...

@AntoineDoubovetzky the update is the following: - MaskedViewIOS -> Has been removed and now lives inside https://github.com/react-native-masked-view/masked-view - AsyncStorage -> You should use https://github.com/react-native-community/asyncstorage. This hasn't been removed yet as...

@dehlen Thanks for raising this. > Officially supporting more build tools on top of Gradle is more bandwidth than Facebook are still currently prepared for That's essentially the point of...

> Is there any updates from Meta team around this ? Thanks! What @TheSavior mentioned above still stands: > I think the people on our team at FB want these...