Xcode9.3/iOS11.3环境下FMDB/SQLite调试首次运行频繁崩溃咨询

Hey there, I’ve seen this exact issue pop up a lot after iOS 11.3 rolled out with Xcode 9.3, so let’s break down what’s going on and how to fix it.

iOS 11.3’s SQLite Changes That Trigger This Crash #

Yes, iOS 11.3 introduced key changes to the system’s built-in SQLite library that are directly causing this crash:

• Apple upgraded the SQLite version and enabled stricter multi-thread access checks specifically in Debug mode. Before iOS 11.3, many thread-unsafe database operations might have slipped through silently (or caused intermittent issues), but now Debug builds actively detect cross-thread connection access and throw that illegal multi-threaded access error immediately.
• This is tied to SQLite’s SQLITE_THREADSAFE configuration—Debug builds now enforce strict thread ownership checks for database connections, which exposes issues that were previously hidden.

Why Your Code Is Crashing #

The root cause almost always comes down to how you’re using FMDB:

• FMDatabase instances are not thread-safe. If you’re reusing the same FMDatabase object across multiple threads (even accidentally), iOS 11.3’s Debug checks will catch this and crash your app.
• It’s common for this to happen on first run if your app initializes database operations from multiple threads at startup (e.g., background fetch, UI thread initialization, and a helper thread all hitting the same connection).

Fixes to Resolve the Issue #

Here are the most reliable solutions, ordered by recommendation:

1. Switch to FMDatabaseQueue (Best Practice) #

FMDB provides FMDatabaseQueue explicitly for multi-threaded scenarios—it handles all thread safety internally by serializing database operations.

// Initialize once (e.g., in your app delegate or a singleton)
NSString *dbPath = [NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES).firstObject stringByAppendingPathComponent:@"yourDB.sqlite"];
FMDatabaseQueue *dbQueue = [FMDatabaseQueue databaseQueueWithPath:dbPath];

// Perform any database operation through the queue
[dbQueue inDatabase:^(FMDatabase *db) {
    if (![db open]) {
        NSLog(@"Failed to open database");
        return;
    }
    // Execute your query
    BOOL success = [db executeUpdate:@"INSERT INTO your_table (column) VALUES (?)", @"sample data"];
    if (!success) {
        NSLog(@"Query failed: %@", [db lastError]);
    }
}];

2. Use a Unique FMDatabase Instance Per Thread #

If you need to avoid FMDatabaseQueue for some reason, ensure every thread creates its own FMDatabase instance, opens it, performs operations, and closes it when done. Never share instances across threads.

3. Audit Startup Database Operations #

Check your first-run code for cases where multiple threads might be initializing or accessing the database at the same time. Consolidate these operations to run on a single thread, or wrap them in FMDatabaseQueue to avoid conflicts.

Important Note #

Even if this crash only happens in Debug mode, don’t ignore it! The thread-unsafe behavior exists in Release builds too—it just doesn’t crash immediately. This can lead to data corruption, silent failures, or random crashes down the line.

内容的提问来源于stack exchange，提问作者lauren1573