Mixing
Inconsistent crash while trying to add a persistent store in CoreData
I am facing a weird crash that happens on some devices, reported by Firebase and Xcode crashes history, while migrating to a new CoreData model. The only chan and adding 3 new propertiesge needed to be done is to remove a couple of properties in one table/object. I have regenerated the classes and upgraded the model version as it doesn't need but a light weight migration.
And all I am getting is:
crash_info_entry_0
Fatal error: Error migrating store: Error Domain=NSCocoaErrorDomain Code=256
"The file "<FileName>.sqlite" couldn't be opened." UserInfo={NSFilePath=/var/mobile/Containers/Data/Application/45859729-F07E-4006-8742-3B53DF6D1CE9/Documents/<FileName>.sqlite, NSSQLiteErrorDomain=23}: file /ProjectName/Repo/Models/Storage/CoreData/CoreDataEngine.swift, line 137
I am using Swift 4.2.
ios core-data core-data-migration
edited Feb 4 at 22:33
halfer
14.7k759116
asked Jan 2 at 15:16
Ashraf TawfeeqAshraf Tawfeeq
2,62111529
add a comment |
I am facing a weird crash that happens on some devices, reported by Firebase and Xcode crashes history, while migrating to a new CoreData model. The only chan and adding 3 new propertiesge needed to be done is to remove a couple of properties in one table/object. I have regenerated the classes and upgraded the model version as it doesn't need but a light weight migration.
And all I am getting is:
crash_info_entry_0
Fatal error: Error migrating store: Error Domain=NSCocoaErrorDomain Code=256
"The file "<FileName>.sqlite" couldn't be opened." UserInfo={NSFilePath=/var/mobile/Containers/Data/Application/45859729-F07E-4006-8742-3B53DF6D1CE9/Documents/<FileName>.sqlite, NSSQLiteErrorDomain=23}: file /ProjectName/Repo/Models/Storage/CoreData/CoreDataEngine.swift, line 137
I am using Swift 4.2.
ios core-data core-data-migration
edited Feb 4 at 22:33
halfer
14.7k759116
asked Jan 2 at 15:16
Ashraf TawfeeqAshraf Tawfeeq
2,62111529
add a comment |
I am facing a weird crash that happens on some devices, reported by Firebase and Xcode crashes history, while migrating to a new CoreData model. The only chan and adding 3 new propertiesge needed to be done is to remove a couple of properties in one table/object. I have regenerated the classes and upgraded the model version as it doesn't need but a light weight migration.
And all I am getting is:
crash_info_entry_0
Fatal error: Error migrating store: Error Domain=NSCocoaErrorDomain Code=256
"The file "<FileName>.sqlite" couldn't be opened." UserInfo={NSFilePath=/var/mobile/Containers/Data/Application/45859729-F07E-4006-8742-3B53DF6D1CE9/Documents/<FileName>.sqlite, NSSQLiteErrorDomain=23}: file /ProjectName/Repo/Models/Storage/CoreData/CoreDataEngine.swift, line 137
I am using Swift 4.2.
ios core-data core-data-migration
edited Feb 4 at 22:33
halfer
14.7k759116
asked Jan 2 at 15:16
Ashraf TawfeeqAshraf Tawfeeq
2,62111529
I am facing a weird crash that happens on some devices, reported by Firebase and Xcode crashes history, while migrating to a new CoreData model. The only chan and adding 3 new propertiesge needed to be done is to remove a couple of properties in one table/object. I have regenerated the classes and upgraded the model version as it doesn't need but a light weight migration.
And all I am getting is:
crash_info_entry_0
Fatal error: Error migrating store: Error Domain=NSCocoaErrorDomain Code=256
"The file "<FileName>.sqlite" couldn't be opened." UserInfo={NSFilePath=/var/mobile/Containers/Data/Application/45859729-F07E-4006-8742-3B53DF6D1CE9/Documents/<FileName>.sqlite, NSSQLiteErrorDomain=23}: file /ProjectName/Repo/Models/Storage/CoreData/CoreDataEngine.swift, line 137
I am using Swift 4.2.
ios core-data core-data-migration
ios core-data core-data-migration
edited Feb 4 at 22:33
halfer
14.7k759116
asked Jan 2 at 15:16
Ashraf TawfeeqAshraf Tawfeeq
2,62111529
edited Feb 4 at 22:33
halfer
14.7k759116
asked Jan 2 at 15:16
Ashraf TawfeeqAshraf Tawfeeq
2,62111529
edited Feb 4 at 22:33
halfer
14.7k759116
edited Feb 4 at 22:33
halfer
14.7k759116
edited Feb 4 at 22:33
halfer
14.7k759116
14.7k759116
asked Jan 2 at 15:16
Ashraf TawfeeqAshraf Tawfeeq
2,62111529
asked Jan 2 at 15:16
Ashraf TawfeeqAshraf Tawfeeq
2,62111529
asked Jan 2 at 15:16
Ashraf TawfeeqAshraf Tawfeeq
2,62111529
2,62111529
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
SQLite error 23 is an authorization error. This probably means that you have data protection turned on in your app's capabilities (or else you're using NSPersistentStoreFileProtectionKey when loading the persistent store), and you're trying to access the persistent store when the file is not accessible (e.g. when the screen is locked).
If you can turn off data protection, that would solve the problem. If you need data protection, you need to use data protection related methods in your app delegate to detect when your app can safely access the file.
answered Jan 2 at 17:51
Tom HarringtonTom Harrington
53.7k5104131
Actually store protection neither set in my app's capability nor while loading the store. It's a bit odd as I can only see the crash on Firebase. It crashes specifically hereaddPersistentStore(ofType: NSSQLiteStoreType, configurationName: nil, at: persistanceStoreURL, options: options)
– Ashraf Tawfeeq
Jan 3 at 8:24
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54008797%2finconsistent-crash-while-trying-to-add-a-persistent-store-in-coredata%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
SQLite error 23 is an authorization error. This probably means that you have data protection turned on in your app's capabilities (or else you're using NSPersistentStoreFileProtectionKey when loading the persistent store), and you're trying to access the persistent store when the file is not accessible (e.g. when the screen is locked).
If you can turn off data protection, that would solve the problem. If you need data protection, you need to use data protection related methods in your app delegate to detect when your app can safely access the file.
answered Jan 2 at 17:51
Tom HarringtonTom Harrington
53.7k5104131
Actually store protection neither set in my app's capability nor while loading the store. It's a bit odd as I can only see the crash on Firebase. It crashes specifically hereaddPersistentStore(ofType: NSSQLiteStoreType, configurationName: nil, at: persistanceStoreURL, options: options)
– Ashraf Tawfeeq
Jan 3 at 8:24
add a comment |
SQLite error 23 is an authorization error. This probably means that you have data protection turned on in your app's capabilities (or else you're using NSPersistentStoreFileProtectionKey when loading the persistent store), and you're trying to access the persistent store when the file is not accessible (e.g. when the screen is locked).
If you can turn off data protection, that would solve the problem. If you need data protection, you need to use data protection related methods in your app delegate to detect when your app can safely access the file.
answered Jan 2 at 17:51
Tom HarringtonTom Harrington
53.7k5104131
Actually store protection neither set in my app's capability nor while loading the store. It's a bit odd as I can only see the crash on Firebase. It crashes specifically hereaddPersistentStore(ofType: NSSQLiteStoreType, configurationName: nil, at: persistanceStoreURL, options: options)
– Ashraf Tawfeeq
Jan 3 at 8:24
add a comment |
SQLite error 23 is an authorization error. This probably means that you have data protection turned on in your app's capabilities (or else you're using NSPersistentStoreFileProtectionKey when loading the persistent store), and you're trying to access the persistent store when the file is not accessible (e.g. when the screen is locked).
If you can turn off data protection, that would solve the problem. If you need data protection, you need to use data protection related methods in your app delegate to detect when your app can safely access the file.
answered Jan 2 at 17:51
Tom HarringtonTom Harrington
53.7k5104131
SQLite error 23 is an authorization error. This probably means that you have data protection turned on in your app's capabilities (or else you're using NSPersistentStoreFileProtectionKey when loading the persistent store), and you're trying to access the persistent store when the file is not accessible (e.g. when the screen is locked).
If you can turn off data protection, that would solve the problem. If you need data protection, you need to use data protection related methods in your app delegate to detect when your app can safely access the file.
answered Jan 2 at 17:51
Tom HarringtonTom Harrington
53.7k5104131
answered Jan 2 at 17:51
Tom HarringtonTom Harrington
53.7k5104131
answered Jan 2 at 17:51
Tom HarringtonTom Harrington
53.7k5104131
answered Jan 2 at 17:51
Tom HarringtonTom Harrington
53.7k5104131
53.7k5104131
Actually store protection neither set in my app's capability nor while loading the store. It's a bit odd as I can only see the crash on Firebase. It crashes specifically hereaddPersistentStore(ofType: NSSQLiteStoreType, configurationName: nil, at: persistanceStoreURL, options: options)
– Ashraf Tawfeeq
Jan 3 at 8:24
add a comment |
Actually store protection neither set in my app's capability nor while loading the store. It's a bit odd as I can only see the crash on Firebase. It crashes specifically hereaddPersistentStore(ofType: NSSQLiteStoreType, configurationName: nil, at: persistanceStoreURL, options: options)
– Ashraf Tawfeeq
Jan 3 at 8:24
Actually store protection neither set in my app's capability nor while loading the store. It's a bit odd as I can only see the crash on Firebase. It crashes specifically here
addPersistentStore(ofType: NSSQLiteStoreType, configurationName: nil, at: persistanceStoreURL, options: options)– Ashraf Tawfeeq
Jan 3 at 8:24
Actually store protection neither set in my app's capability nor while loading the store. It's a bit odd as I can only see the crash on Firebase. It crashes specifically here
addPersistentStore(ofType: NSSQLiteStoreType, configurationName: nil, at: persistanceStoreURL, options: options)– Ashraf Tawfeeq
Jan 3 at 8:24
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54008797%2finconsistent-crash-while-trying-to-add-a-persistent-store-in-coredata%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
