-
Notifications
You must be signed in to change notification settings - Fork 75
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
MACOSX_DEPLOYMENT_TARGET #179
Comments
I could not reproduce the issue with XCode 14.3.1. If you run |
I am getting the same error in MacOS. I cloned and ran the tests above, they work fine but they still report the error that is crashing my app. The error from the tests is:
|
Same issue, same result when running integration tests. I got rid of that error only when I manually bumped '10.11' to '10.14' in several files. I have no idea what I'm doing, I started learning flutter few hours ago but this patch apparently fixes the problem:
|
Ah, found out that this error is not crashing my app, it's just a warning:
I've had a completely different error in my code - directory for the database did not exist and the exception was confusing (ClosedException). |
@simolus3 I believe the reason why you might not have been able to recreate it is that newer versions of flutter seemed to have bumped the version requirement; for other reasons I needed to start a clean macOS folder in my existing project, and I found that this issue popped up:
It looks like it's not isolated to only this package, many packages seem to also be on older deployment targets as well. |
I'm developing an app also for MacOs.
The app may not be built, and log gives an error "The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.11, but the range of supported deployment target versions is 10.13 to 13.3.99. (in target 'sqlite3' from project 'Pods')".
It seems to me that latest Drift 2.11.1 may not be used with Xcode Version 14.3.1.
May be it is possible to upgrade Drift to conform latests versions of Xcode.
The text was updated successfully, but these errors were encountered: