stephencelis/SQLite.swift

SQLCipher decrypt failed on iOS12 & iOS11

Open

#1057 opened on Aug 12, 2021

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Swift (10,145 stars) (1,618 forks)batch import
bughelp wanted

Description

  • Build Information SQLite.swift (0.12.2),SQLCipher (4.4.3) Xcode 12.2 iOS12 & iOS11

  • How do do you integrate SQLite.swift in your project? CocoaPods

  • My Issue SQLCipher works well on iOS13 and later version,but decrypt failed on iOS12 & iOS11

  • Podfile

pod 'SQLite.swift', '~> 0.12.2'
pod 'SQLite.swift/SQLCipher', '~> 0.12.2'

In order to make a success,I edit @import SQLite3 -> @import SQLCipher in SQLiteObjc.h

when I call the key method,Console print error "[logging] misuse at line 222049 of [95fbac39ba]"

db = try Connection(path)
try db!.key("key")

Thanks in advance for your answers

Contributor guide

Tech stack
swiftc
Domain
mobiledatabase
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
SwiftiOS development experienceSQLCipher basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the SQLCipher decryption failure on iOS 12 and 11 by examining the SQLiteObjc.h header and the SQLCipher library initialization. The error 'misuse at line 222049' suggests a misuse of the SQLCipher API, possibly due to linking or configuration differences on older iOS versions. Reproduce the issue with a minimal sample project using the same CocoaPods setup. Check the SQLite.swift build settings for iOS 11/12 compatibility and consider updating SQLCipher to a newer version.