techfoundrynz
techfoundrynz
> Hi, [@simonnztg](https://github.com/simonnztg) currently we are not working on this issue because bluntly said, the `gcpfunction` integration doesn't get much use (might be a self-fulfilling prophecy). If you want to...
@kvaster same here For me it seems to be breaking on any use of the Switch component
@Rapsssito was this intentionally closed? I can't see any changes that would make this work make this work. There's a discussion ongoing in the react-native repo https://github.com/facebook/react-native/issues/44255
The fix for compatibility should be available in the latest 0.76.1 React Native release. I'll test it ASAP and will let you know whether this can be closed.
> +1 for scheduling it for 0.76.1. I'm using RNTP and would like to migrate my app to the new arch. I'm in the same boat but for react-native-background-actions.
Thanks @salah-ghanim I look forward to testing it out.
This would be better done in firmware than VESC Tool IMO. Getting different readings when connecting to a controller from a different device would be too confusing.
I'm not using background fetch but I am using react-native-background actions to keep a task running indefinitely on iOS and Android that pulls data from a ble device at roughly...
I'm getting the same thing