BUG : SQLITE Busy error after multiple inserts

[xr1337]

Describe the bug

After a few subsequent event insertion, SQLite sqlite3_step() returns busy state. The SDK does not retry the assertion attempt.

Observation

Function saveEvent(_ message: String) does not check for SQLITE_BUSY and assumes error when no SQLITE_DONE is returned. In fact sqlite3_step can return the following values:

• SQLITE_BUSY
• SQLITE_ERROR
• SQLITE_MISUSE

References:
https://github.com/rudderlabs/rudder-sdk-ios/blob/master-v2/Sources/Classes/Client/RSDatabaseManager.swift#L50
https://www.sqlite.org/c3ref/step.html

To Reproduce
Steps to reproduce the behaviour:

1. Initialise iOS SDK in iOS app
2. Run app on device
3. Fire multiple event and notice the Event insertion error in console:
4. Event is not saved in database

Expected behavior
Upon receiving a busy state, we expect the SDK to retry insertion again later.

Version of the iOS SDK
iOS SDK v2.4.2

** Initialization used **

let config: RSConfig = RSConfig(writeKey: getKey())
      .dataPlaneURL(getDataPlaneURL())
      .loglevel(.debug)
      .trackLifecycleEvents(true)
      .recordScreenViews(true)
    RSClient.sharedInstance().configure(with: config)

[pallabmaiti]

We will look into it.