You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2023. It is now read-only.
Unfortunately I've been giving "soon now" as an ETA for a while, but as it's open source work it has to slice in between paying stuff. It's worth doing, but priorities, right? To be clear though: the code removed from react-native-firebase worked and it still exists, the job is not to code new stuff, it's just to mostly clone the react-native-firebase monorepo / packages / maintenance+testing infrastructure and drop the code-that-actually-worked in there. So it's not a bunch of unknown programming things to figure out, which means as a thing to estimate it's not too hard. I was thinking maybe a week to stand it up and make it public.
We actually have a repo and npmjs space already they're just not public yet since there's nothing to show. I'm hoping for it to exist and be public sometime February / March, it's close to the top of my list at the moment.
Sorry I can't be more concrete but guarantees only come with funding, which this doesn't have much of really
No worries! We still have some ground to cover on our side. I'll ping you when we start working on the ML features and maybe even give you a hand with migrating the code to the new react-native-firebase monorepo. Thanks!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Related to react-native-camera/react-native-camera#2018 and react-native-camera/react-native-camera#2931
Starting from version 4 we should deprecate all google cloud vision features and replace them with ML kit on both Android and iOS
In regards to react-native-camera/react-native-camera#2931 (comment) , @mikehardy do you have any ETA or roadmap for a standalone ML kit react native module we can depend on?
The text was updated successfully, but these errors were encountered: