-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS: Could not build Objective-C module 'SQLite3' when install drift #208
Comments
So the problem is that SQLite.swift will also try to link Unfortunately, I'm not experienced enough with Cocoapods to know how to fix this. I think you can override the SQLite.swift pod to not link sqlite3, and perhaps also exclude its |
writing this comment if you have the same problem as me and are desperate for a fix, maybe this works for you. |
I also encountered this problem. Is there any solution? |
Perhaps it works if you use the standalone subspec of SQLite.swift? That one has a dependency on the |
it really help me |
Excuse me, @simolus3 , I don't understand how to fix the issue in a Flutter project, can you explain for dummies where to inject that code? Also, on another topic, why don't you erase the ios part of |
I'm not too familiar with Cocoapods, but I think adding a |
@Rodsevich nope still the same @simolus3 the helped a bit I get only this now `dependencies: cupertino_icons: ^1.0.2 url_launcher: ^6.3.0 local_auth: ^2.1.8 |
It's hard too say which of these packages might be linking sqlite3 as a native dependency - can you check whether adding this snippet to your podfile changes anything though? |
Hello.
I have the following problem. I am running sqlite tests with native code. In iOS I have the code in the image, at first while testing it was working fine. But when I installed drift I get the following error and the app does not start. I am importing the default sqlite3 library. is there any way to fix it or should I use a third party library for native swift code?
PS: On android there is no problem.
Thanks in advance
Full Log:
The text was updated successfully, but these errors were encountered: