Skip to content
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

Crash reports after switching to use AppGroups due to 0xdead10cc #650

Open
mattsellars123 opened this issue Mar 19, 2024 · 2 comments
Open

Comments

@mattsellars123
Copy link

Hello,

We are using MMKV in a react native app and were hoping to share our mmkv stores using AppGroups. After configuring things everything seemed to work fine for a while then we started getting crash reports with:

Termination Reason: RUNNINGBOARD 0xdead10cc

We do not yet have any extensions writing to this store. I was wondering if there is some other configuration we need to add so that iOS isn't killing our process when the user happens to background it during file writes.

Any insight is very appreciated.

@mrousavy
Copy link
Owner

I need full crash logs.

@mattsellars123
Copy link
Author

mattsellars123 commented Mar 21, 2024

Here you go. Thanks for taking a look. Generally what I've seen from other file uses for iOS specifics are listening on backgrounding event from App delegate and using the UIApplication.shared.beginBackgroundTask but this is very iOS/UIKit specific in this case and from the react side there are many mmkv uses we would need to ensure are sync'd out to the filesystem and released/closed. It's worth noting our app doesn't have any extensions yet, adding app groups support was a preemptive change for a future in which we would.

2024-03-19_11-30-10.6591_-0700-2bd285d62f19f77b80ec7dd30686dfc7c6f74e90.crash.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants