-
Notifications
You must be signed in to change notification settings - Fork 466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS: Failed to write value. The folder “xxxxxxx” doesn’t exist. #1089
Comments
Have the same problem on Expo SDK 50 / Dev client / iOS Simulator Build.
|
I checked again and there is also an error regarding the
|
This issue has been marked as stale due to inactivity. Please respond or otherwise resolve the issue within 7 days or it will be closed. |
Still valid |
Still get the same error:
Is there any workaround to fix this temporarily? |
I see this error quite a lot on iOS too. Deleting the app on the simulator before running |
Same here :( |
Also hitting this after migrating to Expo 50/ |
Any update on this?, after updated to
|
It's a major issue with AsyncStorage. How can one reliability write apps with expo if there are so many platform bugs with basic libraries? |
I have downgraded @react-native-async-storage/async-storage to version 1.23.1 to ensure compatibility with React Native 0.76.3. |
I have entirely deleted async storage because of this and went on mmkv |
@valmnt Are you by chance getting this error on iOS 18? |
I started getting this error after updating to iOS 18.1 (and now getting it on 18.2) |
What happened?
I have a react-native-macos app that uses async-storage to dump the data periodically. The app is connected to Sentry and this error pop-up periodically:
I have just updated the package to
1.23.1
and I'm waiting to see if the error is solved, but in the meantime I thought I'd ask if anyone has experienced this or knows why this would be hapenning.Version
1.17.11
What platforms are you seeing this issue on?
System Information
Steps to Reproduce
I have not been able to reproduce it myself.
The text was updated successfully, but these errors were encountered: