Fatal Exception: FirebaseDatabasePersistenceFailure

[mozeryansky]

• Xcode version: 11.1, iOS 13
• Firebase SDK version: 6.10.0
• Firebase Component: Analytics, Database, RemoteConfig

We're getting crashe almost immediately at startup since updating to 6.10.0. We use background bluetooth and it appears the crashes all were launches were due to bluetooth restoration.

Fatal Exception: FirebaseDatabasePersistenceFailure
0  CoreFoundation                 0x18dc3580c __exceptionPreprocess
1  libobjc.A.dylib                0x18d95dfa4 objc_exception_throw
2  MyFirebaseFramework    0x100e5df5c -[FLevelDBStorageEngine saveUserOverwrite:atPath:writeId:]
3  MyFirebaseFramework    0x100e5d92c -[FLevelDBStorageEngine openDatabases]
4  MyFirebaseFramework    0x100e5ceb8 -[FLevelDBStorageEngine initWithPath:]
5  MyFirebaseFramework    0x100e77f88 -[FRepo deferredInit]
6  libdispatch.dylib              0x18d902610 _dispatch_call_block_and_release
7  libdispatch.dylib              0x18d903184 _dispatch_client_callout
8  libdispatch.dylib              0x18d8af404 _dispatch_lane_serial_drain$VARIANT$mp
9  libdispatch.dylib              0x18d8afdf8 _dispatch_lane_invoke$VARIANT$mp
10 libdispatch.dylib              0x18d8b9314 _dispatch_workloop_worker_thread
11 libsystem_pthread.dylib        0x18d952f88 _pthread_wqthread
12 libsystem_pthread.dylib        0x18d955ad4 start_wqthread

Error initializing persistence: Error Domain=APLevelDBErrorDomain Code=0 "IO error: /var/mobile/Containers/Data/Application/B6E374D0-D5FD-478F-9CBB-26E73BA794C3/Documents/firebase/log/xxxxx.firebaseio.com_xxxxx/server_data/MANIFEST-000001: Operation not permitted" UserInfo={NSLocalizedDescription=IO error: /var/mobile/Containers/Data/Application/B6E374D0-D5FD-478F-9CBB-26E73BA794C3/Documents/firebase/log/xxxxx.firebaseio.com_xxxxx/server_data/MANIFEST-000001: Operation not permitted}

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[morganchen12]

If you're able to reproduce the crash, can you share your app logs from around when this happens? I suspect it's related to file protection.

[mozeryansky]

I use Crashlytics, but I didn't log whether file protection is on. Crashlytics says "0% App in Background", but I don't believe that since I do log the launch options and I know it launched due to restore, which is generally in the background and/or while locked.

I assumed it was file protection related based on the error message "Operation not permitted", but what should I do about it? Shouldn't Firebase handle this in some manner?

[morganchen12]

Yes, Firebase should handle it :) This is most likely a bug in Database and not an error in your code.

In this case, the right thing to do is probably either mark the file as NSFileProtectionCompleteUntilFirstUserAuthentication or make the error non-fatal and create/access the files it needs when data becomes available.

[mozeryansky]

@morganchen12 What should I do about it? The file is part of firebase.

[morganchen12]

The file is located in your app container's Documents/firebase directory, so you could try marking that entire directory as NSFileProtectionCompleteUntilFirstUserAuthentication. This is probably overkill, but it would be a good indicator of whether or not file protection is the source of the crash.

[mozeryansky]

I'm going to update to 6.13.0, but I rather not make any hacks. What's odd is that it's only in our production app and not in any internal build.

[wilhuff]

This seems like the RTDB equivalent of #2846 against Firestore. There we concluded that Firestore is incompatible with NSFileProtectionComplete. I suspect the same conclusion will apply here.

[paulb777]

Closing, since there don't seem to be any actions here.

[mozeryansky]

@paulb777 My issue was not solved. I'll file a new issue with the latest info.

[paulb777]

@mozeryansky Sorry about that. I'll reopen and we can take another look with the latest info.