Jenn Magder

@bparrishMines do you know if this was addressed in v4_webview (3.0)? An internal customer is hitting.

`nm Runner.app/Runner` shows the Objective-C symbols but not the fii function: ``` 00000001000070f0 t -[NativeAddPlugin handleMethodCall:result:] ``` I can can muck up the linker flags to not include `-l"native_add"` and...

@sjindel-google Do you know the last time this worked? Is there an integration test running somewhere?

cc @dcharkes maybe someone working on ffi tooling wants to take a look.

The autotools flags are something like (I'm sure this is missing something important): ``` ./autogen.sh CC="xcrun gcc -isysroot /path/to/xcode/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.0.sdk" \ CXX="xcrun g++ -isysroot /path/to/xcode/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.0.sdk" \ CPPFLAGS="-arch arm64" CFLAGS="-arch arm64" --host...

I reopened https://github.com/flutter/flutter/issues/86926, you can follow along on shipping the arm dart SDK there. This issue is only tracking adding the architecture slice for the listed binaries.

The fix was reverted, reopening https://github.com/flutter/engine/pull/52913

#66399 isn't available until 1.23.0-7.0.pre, so not sure what would have fixed this on 1.22.1.

@acoutts maybe some processing needed in https://github.com/flutter/flutter/blob/e5322acc77f116803c93cfe1d538ae3c16a19423/packages/flutter_tools/lib/src/ios/devices.dart#L721-L722 I haven't looked into it though.

> @jmagman any pointers on where else I can look? Are you able to step through the tool code and put breakpoints in the debugger logging? That's probably the easiest...