SQLite data lost when killing the app #385

New Issue

Closed

opened 2025-12-29 15:30:40 +01:00 by adam · 12 comments

adam commented 2025-12-29 15:30:40 +01:00

Owner

Copy Link

Originally created by @odilebellerose on GitHub (Mar 30, 2022).

Hi,
when i create some objects by using

dataStack.perform( asynchronous: { (transaction) -> StoredDocument? in) })

, everything is working well i can see datas in my sqlite database. However, when i kill my app, the database is empty.

I've tried to save context on applicationWillTerminate but it doesn't change anything,

do {
	try dataStack.unsafeContext().save()
} catch {
			
}

Any idea of what's happens ?

Thanks you in advance for your answer.

Originally created by @odilebellerose on GitHub (Mar 30, 2022). Hi, when i create some objects by using ``` dataStack.perform( asynchronous: { (transaction) -> StoredDocument? in) }) ``` , everything is working well i can see datas in my sqlite database. However, when i kill my app, the database is empty. I've tried to save context on applicationWillTerminate but it doesn't change anything, ``` do { try dataStack.unsafeContext().save() } catch { } ``` Any idea of what's happens ? Thanks you in advance for your answer.

adam closed this issue 2025-12-29 15:30:40 +01:00

adam commented 2025-12-29 15:30:41 +01:00

Author

Owner

Copy Link

@JohnEstropia commented on GitHub (Mar 30, 2022):

I'm not sure I understand what you mean. You are sure that the SQLite database is created and populated correctly, but the file disappears after you terminate the app?

If so then something in your code is deleting the database manually, as CoreStore doesn't have any mechanism that automatically deletes the store.

@JohnEstropia commented on GitHub (Mar 30, 2022): I'm not sure I understand what you mean. You are sure that the SQLite database is created and populated correctly, but the file disappears after you terminate the app? If so then something in your code is deleting the database manually, as CoreStore doesn't have any mechanism that automatically deletes the store.

adam commented 2025-12-29 15:30:41 +01:00

Author

Owner

Copy Link

@odilebellerose commented on GitHub (Mar 30, 2022):

I'm not sure I understand what you mean. You are sure that the SQLite database is created and populated correctly, but the file disappears after you terminate the app?

If so then something in your code is deleting the database manually, as CoreStore doesn't have any mechanism that automatically deletes the store.

The database still exists but records are deleted. Do you know if there is a way that CoreStore re-create sqlite database or erase the content ?

@odilebellerose commented on GitHub (Mar 30, 2022): > I'm not sure I understand what you mean. You are sure that the SQLite database is created and populated correctly, but the file disappears after you terminate the app? > > If so then something in your code is deleting the database manually, as CoreStore doesn't have any mechanism that automatically deletes the store. The database still exists but records are deleted. Do you know if there is a way that CoreStore re-create sqlite database or erase the content ?

adam commented 2025-12-29 15:30:41 +01:00

Author

Owner

Copy Link

@JohnEstropia commented on GitHub (Mar 30, 2022):

Is the SQLite file URL constant or is it generated and somehow changes every launch?

The only reason CoreStore would reset a database is if the schema was updated AND the .recreateStoreOnModelMismatch option is set on the SQLiteStore

@JohnEstropia commented on GitHub (Mar 30, 2022): Is the SQLite file URL constant or is it generated and somehow changes every launch? The only reason CoreStore would reset a database is if the schema was updated AND the `.recreateStoreOnModelMismatch` option is set on the `SQLiteStore`

adam commented 2025-12-29 15:30:42 +01:00

Author

Owner

Copy Link

@odilebellerose commented on GitHub (Mar 30, 2022):

I have a Singleton, with a start() func :

open func start() {
	
		let store = SQLiteStore(fileName: "documents_storage.sqlite")
		
		do {
			try self.dataStack.addStorageAndWait(store)
		} catch {
			
		}
	}

and i'm calling this function in the AppDelegate :

open func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
  DocumentStorageManager.shared.start()

return true
}

@odilebellerose commented on GitHub (Mar 30, 2022): I have a Singleton, with a start() func : ``` open func start() { let store = SQLiteStore(fileName: "documents_storage.sqlite") do { try self.dataStack.addStorageAndWait(store) } catch { } } ``` and i'm calling this function in the AppDelegate : ``` open func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool { DocumentStorageManager.shared.start() return true } ```

adam commented 2025-12-29 15:30:42 +01:00

Author

Owner

Copy Link

@JohnEstropia commented on GitHub (Mar 30, 2022):

Are you using storyboards? If so you are likely accessing the DataStack before addStorageAndWait() returns. Storyboard initial ViewControllers get initialized before the UIAppDelegate's didFinishLaunching is called. At least if I recall correctly.

Put a breakpoint on the dataStack getter and the addStorageAndWait() call and see if it's getting accessed somewhere else before the store is added.

@JohnEstropia commented on GitHub (Mar 30, 2022): Are you using storyboards? If so you are likely accessing the `DataStack` before `addStorageAndWait()` returns. Storyboard initial ViewControllers get initialized before the `UIAppDelegate`'s `didFinishLaunching` is called. At least if I recall correctly. Put a breakpoint on the `dataStack` getter and the `addStorageAndWait()` call and see if it's getting accessed somewhere else before the store is added.

adam commented 2025-12-29 15:30:43 +01:00

Author

Owner

Copy Link

@odilebellerose commented on GitHub (Mar 30, 2022):

Are you using storyboards? If so you are likely accessing the DataStack before addStorageAndWait() returns. Storyboard initial ViewControllers get initialized before the UIAppDelegate's didFinishLaunching is called. At least if I recall correctly.

Put a breakpoint on the dataStack getter and the addStorageAndWait() call and see if it's getting accessed somewhere else before the store is added.

I'm not using Storyboards and i tried to put breakpoints on functions using the dataStack it's seems ok. The addStorageAndWait() func seems to be called first.

@odilebellerose commented on GitHub (Mar 30, 2022): > Are you using storyboards? If so you are likely accessing the `DataStack` before `addStorageAndWait()` returns. Storyboard initial ViewControllers get initialized before the `UIAppDelegate`'s `didFinishLaunching` is called. At least if I recall correctly. > > Put a breakpoint on the `dataStack` getter and the `addStorageAndWait()` call and see if it's getting accessed somewhere else before the store is added. I'm not using Storyboards and i tried to put breakpoints on functions using the dataStack it's seems ok. The `addStorageAndWait() `func seems to be called first.

adam commented 2025-12-29 15:30:43 +01:00

Author

Owner

Copy Link

@JohnEstropia commented on GitHub (Mar 30, 2022):

How are you confirming the SQLite file contents? Are you sure the perform() methods are completing successfully?

@JohnEstropia commented on GitHub (Mar 30, 2022): How are you confirming the SQLite file contents? Are you sure the `perform()` methods are completing successfully?

adam commented 2025-12-29 15:30:43 +01:00

Author

Owner

Copy Link

@odilebellerose commented on GitHub (Mar 30, 2022):

If i open the SQLite file in a browser i can see my records. In fact, i'm using CoreStore to store documents that i'm going to upload by using operation queue and background task. If i keep the app open or put it in the background, everything is working well. That's why i can confirm SQLite file contents. If i kill the app and re-open it, my app should fetch documents in database and try to re-upload documents but they have been deleted.

@odilebellerose commented on GitHub (Mar 30, 2022): If i open the SQLite file in a browser i can see my records. In fact, i'm using CoreStore to store documents that i'm going to upload by using operation queue and background task. If i keep the app open or put it in the background, everything is working well. That's why i can confirm SQLite file contents. If i kill the app and re-open it, my app should fetch documents in database and try to re-upload documents but they have been deleted.

adam commented 2025-12-29 15:30:44 +01:00

Author

Owner

Copy Link

@JohnEstropia commented on GitHub (Mar 30, 2022):

After restarting the app, do you still see the records in the SQLite browser?

@JohnEstropia commented on GitHub (Mar 30, 2022): After restarting the app, do you still see the records in the SQLite browser?

adam commented 2025-12-29 15:30:44 +01:00

Author

Owner

Copy Link

@odilebellerose commented on GitHub (Mar 30, 2022):

No, i can't.

@odilebellerose commented on GitHub (Mar 30, 2022): No, i can't.

adam commented 2025-12-29 15:30:44 +01:00

Author

Owner

Copy Link

@JohnEstropia commented on GitHub (Mar 30, 2022):

There's definitely something deleting your file (or a parent folder) somewhere. If you can isolate the issue in a shareable project I'll try to take a look.

@JohnEstropia commented on GitHub (Mar 30, 2022): There's definitely something deleting your file (or a parent folder) somewhere. If you can isolate the issue in a shareable project I'll try to take a look.

adam commented 2025-12-29 15:30:45 +01:00

Author

Owner

Copy Link

@odilebellerose commented on GitHub (Mar 30, 2022):

Unfortunately i can't :/
Thanks you for your help, i'm going to try to figure it out.

@odilebellerose commented on GitHub (Mar 30, 2022): Unfortunately i can't :/ Thanks you for your help, i'm going to try to figure it out.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

develop

master

prototype/concurrency

minIOS13

prototype/containers

transactionSourceTracking

prototype/swiftui

minIOS11

swift5_3

prototype/propertyWrapperFields

prototype/propertyWrappers

prototype/propertyWrapper

Swift5

throwables

prototype/Swift_4_1

prototype/Swift_4_0

prototype/Swift_3_2

prototype/queryBuilders

temp/develop

corestore4_develop

prototype/mainContextToPSC

master_ios_7_to_9

swift_2_3

gh-pages

_corespotlight-test

9.3.0

9.2.0

9.1.0

9.0.0

8.1.0

8.0.1

8.0.0

7.3.1

7.3.0

7.2.0

7.1.0

7.0.4

7.0.3

7.0.2

7.0.1

7.0.0

6.3.2

6.3.1

6.3.0

6.2.1

6.2.0

6.1.0

6.0.0

5.3.1

5.3.0

5.2.0

5.1.1

5.1.0

5.0.0

4.2.4

4.2.3

4.2.2

4.2.1

4.2.0

4.1.4

4.1.3

4.1.1

4.1.0

4.0.5

4.0.4

4.0.3

4.0.2

4.0.1

4.0.0

4.0.0-beta3

4.0.0-beta2

4.0.0-beta

3.1.1

3.1.0

3.0.3

3.0.2

3.0.1

3.0.0

2.1.3

2.1.2

2.1.1

2.1.0

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.1

2.0.0

1.6.10

1.6.9

1.6.8

1.6.7

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.1

1.2.0

1.0.2

1.0.1

1.0.0

0.2.1

0.2.0

0.1.2

0.1.1

0.1.0

Labels

Clear labels

abandoned

corestore bug

discussion

duplicate

enhancement

fixed

fixed

help wanted

in progress

investigating

ios/compiler bug

irreproducible

looking for workarounds

not a bug

pending

pending docs update

pull-request

Mirrored from GitHub Pull Request

question

regression

user bug

wontfix

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

adam

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/CoreStore#385