8000 Work around ffi "symbol not found" error from CocoaPods on ARM Macs with x86_64 ffi gem · Issue #70796 · flutter/flutter · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Work around ffi "symbol not found" error from CocoaPods on ARM Macs with x86_64 ffi gem #70796

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.

Sign up for GitHub

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

Jump to bottom
Closed
jmagman opened this issue Nov 18, 2020 · 2 comments
Closed

Work around ffi "symbol not found" error from CocoaPods on ARM Macs with x86_64 ffi gem #70796

jmagman opened this issue Nov 18, 2020 · 2 comments
Assignees
@jmagman
Labels
P1 High-priority issues at the top of the work list platform-host-arm Building on an ARM-based platform platform-ios iOS applications specifically tool Affects the "flutter" command-line tool. See also t: labels.

Comments

@jmagman
Copy link
Member
jmagman commented Nov 18, 2020

Running CocoaPods in Rosetta on an ARM mac to embed plugins (arch -x86_64 pod install) fails:

LoadError - dlsym(0x7fbbeb6837d0, Init_ffi_c): symbol not found - /Library/Ruby/Gems/2.6.0/gems/ffi-1.13.1/lib/ffi_c.bundle
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/Library/Ruby/Gems/2.6.0/gems/ffi-1.13.1/lib/ffi.rb:6:in `rescue in <top (required)>'
/Library/Ruby/Gems/2.6.0/gems/ffi-1.13.1/lib/ffi.rb:3:in `<top (required)>'

The workaround is to install the ffi gem in x86:

arch -x86_64 sudo gem install ffi

Figure out how to install this from flutter (prompt sudo) without making bundler people mad, or at least add a doctor check similar to the one where CocoaPods isn't installed and prompt them to run that command.
@jmagman jmagman added platform-ios iOS applications specifically tool Affects the "flutter" command-line tool. See also t: labels. P1 High-priority issues at the top of the work list labels Nov 18, 2020
@jmagman jmagman self-assigned this Nov 18, 2020
This was referenced Nov 18, 2020
Closed
Merged
@jmagman
Copy link
Member Author
jmagman commented Nov 20, 2020

The tool now detects this issue and suggests how to fix it. That's probably the best we can do until it's fixed on CocoaPod's side.

Also mentioned in https://github.com/flutter/flutter/wiki/Developing-with-Flutter-on-Apple-Silicon.

@jmagman jmagman closed this as completed Nov 20, 2020
@darshankawar darshankawar mentioned this issue Jan 6, 2021
Closed
@TahaTesser TahaTesser added the platform-host-arm Building on an ARM-based platform label Feb 12, 2021
@TahaTesser TahaTesser mentioned this issue Feb 12, 2021
Closed
@WhidRubeld WhidRubeld mentioned this issue Feb 14, 2021
Closed
@zarinfam zarinfam mentioned this issue Feb 19, 2021
Closed
@andycall andycall mentioned this issue Apr 19, 2021
Closed
@lipemorais lipemorais mentioned this issue May 7, 2021
Open
5 tasks
@github-actions
Copy link
github-actions bot commented Aug 5, 2021

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jmagman jmagman

Labels
P1 High-priority issues at the top of the work list platform-host-arm Building on an ARM-based platform platform-ios iOS applications specifically tool Affects the "flutter" command-line tool. See also t: labels.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jmagman @TahaTesser @pedromassangocode
0