Skip to content
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

Carthage issue with latest version: "dyld: Symbol not found" in Reachability framework #442

Closed
mbuchetics opened this issue Dec 14, 2020 · 3 comments
Assignees
Labels
bug Something isn't working build Issues related to build and CI/CD closing-soon-if-no-response This issue will be closed in 7 days unless further comments are made.

Comments

@mbuchetics
Copy link

Using the latest (3.1.12) version via Carthage, the app crashes with

dyld: Symbol not found: _$sSo18NSNotificationNamea12ReachabilityE19reachabilityChangedABvau
  Referenced from: /Users/rebello/Library/Developer/CoreSimulator/Devices/A60D39B4-E70C-4CB2-A90D-48767C321533/data/Containers/Bundle/Application/14F5DAFA-3F25-43EA-8F02-47DDF6C08D86/nano-dev.app/Frameworks/AWSAppSync.framework/AWSAppSync
  Expected in: /Users/rebello/Library/Developer/CoreSimulator/Devices/A60D39B4-E70C-4CB2-A90D-48767C321533/data/Containers/Bundle/Application/14F5DAFA-3F25-43EA-8F02-47DDF6C08D86/nano-dev.app/Frameworks/Reachability.framework/Reachability

This is due to some version mismatch of the Reachability framework. It is included in the Cartfile using ~> 5.0.0, which currently pulls version 5.1.0 of the framwork (the latest version).

A workaround is to add github "ashleymills/Reachability.swift" "v5.0.0" to my own Cartfile, and pull down version 5.0.0 instead of 5.1.0 (I ran carthage udpate a second time to avoid any version conflict). This works, but please fix the dependencies in your own Cartfile.

@ruiguoamz ruiguoamz added the pending triage Not triaged yet label Dec 14, 2020
@palpatim palpatim added bug Something isn't working build Issues related to build and CI/CD pending investigation It has been triaged and discussed but the actual work is still pending and removed pending triage Not triaged yet labels Jan 29, 2021
@palpatim
Copy link
Contributor

Next steps for us are to see if the recently released XCFramework support in the SDK (which should allow us to support XCFramework builds in AppSyncClient) will allow us to workaround this issue. If not, then the likely fix is to pin directly to version 5.0.0 as @mbuchetics noted in their original post.

@royjit
Copy link
Contributor

royjit commented Feb 1, 2021

Created PR to pin to 5.0.0 - #455

@royjit royjit removed the pending investigation It has been triaged and discussed but the actual work is still pending label Feb 3, 2021
@royjit
Copy link
Contributor

royjit commented Feb 3, 2021

Change is released in 3.1.16 - https://github.com/awslabs/aws-mobile-appsync-sdk-ios/releases/tag/3.1.16. Please take a look, reach out to us if you are facing any other issue.

@royjit royjit added the closing-soon-if-no-response This issue will be closed in 7 days unless further comments are made. label Feb 3, 2021
@royjit royjit closed this as completed Feb 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working build Issues related to build and CI/CD closing-soon-if-no-response This issue will be closed in 7 days unless further comments are made.
Projects
None yet
Development

No branches or pull requests

4 participants