-
Notifications
You must be signed in to change notification settings - Fork 265
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
Compilation error after updating to 16.0.1 #301
Comments
I am having troubles reproducing but currently am on a m1 mac without x86_64 simulators. I tested on an IOS 12 device though and did not receive that crash. I wont have access to an intel machine until tomorrow. Do you have this issue on iOS 13 or iOS 14 simulators? |
@kofoednielsen Still cant reproduce using an intel device. Have you tried cleaning and wiping any derived data? Any chance you can share a project with me to help reproduce the issue? |
@kofoednielsen If your project was an already existing project and you tried to migrate to latest Airship version, you may find an older Swift reference laying around in your Xcode project settings. I faced the same link problem here after migrating to Airship 16+ (intel Mac, xcode version 13.1 - 13A1030d). In Xcode, double click the project icon in the tree, and look for library search paths in the "Build Settings" tab of PROJECT. Then click on the minus icon to remove any reference to swift-5.0 in the value list, be sure to keep " |
Thank you @AlbrechtAndrzejewski for providing the fix. I am going to close this now since I am seeing less linked issues coming through. If it comes up again Ill add it to the README |
Preliminary Info
What Airship dependencies are you using?
What are the versions of any relevant development tools you are using?
Compiling for iOS 12 on Xcode 13.
Report
What unexpected behavior are you seeing?
Compilation error, see logs below.
What is the expected behavior?
Successful compilation
What are the steps to reproduce the unexpected behavior?
We upgraded to 16.0.1 from 14.6.1 when this started happening.
Do you have logging for the issue?
The text was updated successfully, but these errors were encountered: