Closed austenstrine closed 2 years ago
We did this for our project: https://stackoverflow.com/questions/64803179/how-do-i-avoid-build-errors-when-i-include-sqlcipher-pod-in-swift-project/65020426#65020426. You have to download the SQLite.swift library and used it locally, and adding SQLCipher as an external dependency.
We did this for our project: https://stackoverflow.com/questions/64803179/how-do-i-avoid-build-errors-when-i-include-sqlcipher-pod-in-swift-project/65020426#65020426. You have to download the SQLite.swift library and used it locally, and adding SQLCipher as an external dependency.
still had same issue redefinition of bla bla bla, am i miss something ?
The answer in stack overflow worked for our project, dunno any further...
pod 'SQLCipher', '= 4.2.0' pod 'SQLite.swift/SQLCipher', '~> 0.12.2'
and change code in 'SQLiteObjc.h'
change line26: @import SQLite3; to @import SQLCipher;
this is work for me.
xcode 12.2 mac mini m1
Should be fixed by #1051 and #1053
I'm using Xcode 12.3, and affects devices on iOS 14+. Here is the version of SQLite.swift I am using in my podfile: pod 'SQLite.swift/SQLCipher', '~> 0.12.0'
This was working 3-4 months ago when I checked last. Now it gives me compiler errors:
And it seems I'm not the only one to experience this issue: https://stackoverflow.com/questions/63971403/why-does-xcode12-give-me-sqlite-compiler-error
They have identified a workaround, but I would have to abandon the SQLCipher branch, which would be a very bad idea because of what I am using the package for.
Is there any chance we could get this to a point where it can compile without wonky workarounds?
Otherwise, I will be completely screwed for relying on this package when I built it into the app I'm maintaining in April of 2020. If you're going to abandon a package, say as much so that people don't build it into their projects, and so that people who have it in their projects already can start replacing it.