GardenMobile & interfaces

Early Flutter troubleshooting on Apple Silicon

Several historical M1 failures involving filtering software, IDE discovery, native Ruby extensions, and debugger logs.

The early Apple Silicon transition exposed several different toolchain problems. The original note collected them together, but each has a different boundary.

Filtering and network requests

Error:
Unhandled exception:
Bad state: Future already completed
flutter config --no-analytics
Goto Adguard preferences -> Network -> Select Mode... in "Network Extension" of Automatically filter applications -> Change to "automatic proxy"

The earlier report linked AdGuard’s issue. Changing filtering mode or analytics settings described that environment, not every network failure.

IDE plugin discovery

[!] Android Studio (version 4.1)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
ln -s ~/Library/Application\ Support/Google/AndroidStudio4.1/plugins ~/Library/Application\ Support/AndroidStudio4.1

A plugin-path symlink is specific to the named Android Studio version and directories.

Native Ruby extension loading

LoadError - dlsym(0x7f8926035eb0, Init_ffi_c): symbol not found - 
- Right-click on terminal app -> Get Info -> Check to "Open using Rosetta" to enable Rosetta mode as default 
- Then close all terminal instance and reopen it
- Run sudo gem install ffi
- Run pod install

The old CocoaPods workaround used a translated terminal. Ruby, its native extensions, and the calling process need compatible architectures; a blanket terminal-mode switch is not proof of that alignment.

Debugger log output

flutter channel beta
flutter upgrade
flutter clean

The source tried a beta-channel upgrade for another debugger message. Folding a log line only changes its visibility; it does not repair the underlying condition. No toolchain, network mode, or application was changed for this revision.

← Back to the garden