UIDocument openWithCompletionHandler: crash

Question

I'm using Core Data in my project and get a rare crash in the following code section

 -(void) useDocument{
     AFFormsCoreDataEngine* engine = [AFFormsCoreDataEngine sharedInstance];
     if (![[NSFileManager defaultManager] fileExistsAtPath: [engine.formsDatabase.fileURL path]])
     {
         [engine.formsDatabase saveToURL: engine.formsDatabase.fileURL forSaveOperation: UIDocumentSaveForCreating completionHandler: ^(BOOL success){
            // setup
         }];
    }
    else if (engine.formsDatabase.documentState == UIDocumentStateClosed)
    {
        [engine.formsDatabase openWithCompletionHandler: ^(BOOL success){
             // setup
        }];
    }
    else if (engine.formsDatabase.documentState == UIDocumentStateNormal)
    {
         // setup
    }
}

This is what crash log says:

Last Exception Backtrace:
0   CoreFoundation                  0x371fd88f __exceptionPreprocess + 163
1   libobjc.A.dylib                 0x31272259 objc_exception_throw + 33
2   CoreFoundation                  0x371fd789 +[NSException raise:format:] + 1
3   Foundation                      0x32ce83a3 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 91
4   UIKit                           0x306b3149 -[UIDocument openWithCompletionHandler:] + 173
5   EETECH                          0x00014d23 -[AFFormListViewController useDocument] (AFFormListViewController.m:150)

Can anyone help me to solve this issue? It happens very seldom, but still is very unpleasant

What exception is being thrown? Either catch and log the exception, or set a breakpoint for the source of the exception (click on the + at the bottom of the exception pane and add the one for exception source). This will provide you with why the exception is being thrown. — Jody Hagins, Aug 13 '12 at 12:42
I use exception breakpoints. To make things clearer, I've never caught that exception on my own, but some of the users provided me with crash logs. Would it be possible to log the exceptions on other user's device? — NikGreen, Aug 13 '12 at 15:47

score 13 · Accepted Answer · answered Sep 07 '12 at 19:15

The error occurs if your app attempts to call your useDocument method twice in close succession.

Because the openWithCompletionHandler: opens the document asynchronously, the document may still be opening when the method is called again.

If this happens, your app ends up trying to open the document twice (as the document state will remain UIDocumentStateClosed until completion) and this causes the exception to be thrown.

If you have an exception breakpoint, you may see something like this in the console:

 *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'attempt to open or a revert document that already has an open or revert operation in flight:

This "answer" simply explains the problem in more detail but offers no answer at all. — stephmur, Jul 31 '21 at 19:33

score 2 · Answer 2 · answered Aug 14 '12 at 00:11

Well, an assertion is failing in the UIDocument code. You should probably provide more code, because you are obviously setting something up improperly.

The assertion is then throwing an exception. If you @catch exceptions in this method, you can log the exception.

Or, you can assign your own NSAssertionHandler to the thread, and see the assertion directly.

UIDocument openWithCompletionHandler: crash

2 Answers2

Linked