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

Not arm64 compliant #42

Closed
San-Jeevan opened this issue Sep 28, 2016 · 6 comments
Closed

Not arm64 compliant #42

San-Jeevan opened this issue Sep 28, 2016 · 6 comments

Comments

@San-Jeevan
Copy link

San-Jeevan commented Sep 28, 2016

"type metadata for (extension in myproject):__ObjC.UIView.(ToastError in _9435D8AD737309FD1AA87C6149FEA121)", referenced from:

ld: symbol(s) not found for architecture arm64

cant compile it on arm64 architecture.

@RegisStGelais
Copy link

I have the same issue when archiving

@btanner
Copy link

btanner commented Oct 7, 2016

Same problem here. No idea how to fix, but app deploys to connected devices or simulator, just can't archive.

@scalessec
Copy link
Owner

Xcode 8? Can you reproduce when you try to archive the Toast-Swift demo project? I just archived and exported an ad-hoc build of the demo project without issue.

@btanner
Copy link

btanner commented Oct 10, 2016

I think I originally just copied Toast.Swift directly into my project in the Spring of 2016 and have been using it without issue since then.

The problem is now with XCode 8 using Swift 2.3. It looks like you've updated to Swift 3 which I cannot move to quite yet because of other issues I'm fighting with.

I'll let you know after we get to Swift 3 if there are any probs. Please let me know if there is a Swift 2.3 file hanging around I can use :)

@RegisStGelais
Copy link

The problem is now with XCode 8 using Swift 2.3. It looks like you've updated to Swift 3 which I cannot move to quite yet because of other issues I'm fighting with.

Same thing for me

@bijington
Copy link

@btanner @RegisStGelais this might be a little late however I encountered the same issue and found that set the Optimization Level to None for Release let me Archive. I also plan to move to Swift 3.0 at some point but it is quite daunting seeing all of those errors pop-up.

Here is the credit:
SwiftGen/SwiftGen#57 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants