Eduard Monfort
Eduard Monfort
Yes... But look like a difficult solution to something quite usual. Maybe would be better to create a FutureProvider apart to handle update logic.
Hello @joanofdart I don't think it is needed any update. It is clear the usage of asyncValue with Remi's example. The use case I exposed later could be solved really...
I'm also seeing the same issue, receiving apple `NSLocationWhenInUseUsageDescription` everytime even if I have `"enableLocation": false`. The thing is, I even tried to have have `"enableLocation": false` in my `app.config.js`...
I'm using typescript and using `app.config.ts` with version 4.0.1 and when I type "enable" it isn't showing the hint or error for "enableLocation", thats why I was trying to follow...
@mrousavy I understand that typescript works if you use "withVisionCamera" plugin. But if you add the plugin through Expo via: ``` { "name": "my app", "plugins": [ [ "react-native-vision-camera", {...
I can confirm the same issue on Android. Exact the same error and fixed by deleting data and cache in the app's settings as @behenate described. So if a user...
Ok, so apparently it is normal behavior not to delete Secure Storage and also It is normal not being able to decrypt old data after reinstalling. The solution is to...
> Also experiencing this issue. > > > > Using `expo ~48.0.0`, `expo-secure-store ~12.1.1` and `react-native 0.71.3`. > > Device: OnePlus 5t, still on Android 10. > > > >...
> Could you at least throw or return a specific, typed error, so we know **that's** what happened? Because otherwise we're seeing this thousands of time on Sentry, and I...
It is happening to everyone. For the good of the repo mantainers try not commenting "me too" that isn't helpful at all for the team and other members. That said...