-
Notifications
You must be signed in to change notification settings - Fork 130
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
Prebuilt frameworks using Swift 5.5 (Carthage) #498
Comments
Hi @pokryfka, thanks for bringing this to our attention. aws-mobile-appsync-sdk-ios uses Travis CI, which does not yet support Xcode 13. Until Xcode 13 is available in our CI pipeline, it should be possible for Carthage to build the SDK from source. Is this behavior working for you? |
Thank you for following up on that. Yes, I can compile it. The main issue with it is that it takes quite a long time. Looking forward to CI update. |
@ameter Travis CI added an image with Xcode 13.1 from https://docs.travis-ci.com/user/reference/osx/#xcode-version
|
👋 |
@pokryfka Thanks for following up. We'll update the build and provide an update here when the new version is ready. |
@pokryfka we updated our CI script and released a new of version of the SDK. Let us know if that solves your issues |
Thank you for the change.
Please note that Travis does have image with Xcode 13.2.1/Swift 5.5.2:
|
Thank you! |
Well, binaries are fetched as expected but they dont include AppSync at all. |
Thank you for the update. I made a quick test and the generated framework can be imported (embedded), however when the library is loaded (runtime) it lacks some symbols from
For the record,
and its resolved to:
|
@pokryfka are you getting that error from a clean build? If you haven't done that already, I'd also recommend to clean your derived data folder just to rule out that the issue isn't related to old artifacts. |
removing derived data does not help.
The problem does not happen when I build
(without
-- enums seem to be compiled/bridged/exported differently, |
BTW |
@pokryfka how are you linking the framework in your project?
That's expected, we've opted to temporarily embed and renamed that to |
right, I link all of these: private let appSyncFrameworks = [
"AWSAppSync",
"AppSyncRealTimeClient",
"AWSCore",
"SQLite",
"Starscream",
"Reachability",
] it all works well when I build them myself via |
we can close it as far as I am concerned, BTW I noticed that even when adding AppSync via SPM it still gets AWSCore xcframeworks, |
Describe the bug
Please prebuilt frameworks using Swift 5.5. (Carthage)
To Reproduce
Steps to reproduce the behavior:
Result:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
n/a
Environment(please complete the following information):
Device Information (please complete the following information):
n/a
Additional context
n/a
The text was updated successfully, but these errors were encountered: