Hi @fredo6 and all,
After two hours of trying to fix the Fredo update-check crash (spoiler — fixed it), here's what I found. Might be useful for pep75/Rienk/MDVolle above too, since it looks like the same class of issue.
Setup: macOS 26.6, tested side-by-side across three SketchUp installs on the same Mac — SketchUp 2025, SketchUp 2026 and SketchUp 2027, each with its own LibFredo6 16.1a (+ FredoTools + JointPushPull) installed via Sketchucation Tools.
Symptom (SketchUp 2025 and SketchUp 2026 — identical on both): the "Check Fredo6 Plugins for Update" dialog opens completely blank (no version table, no icon, nothing), and the Ruby Console shows:
!LibFredo6: Error when requiring Binary .../Fredo6_!LibFredo6/Binaries/Mac_32/bin_body_Lib6G6.bundle - dlopen(...) tried: '.../bin_body_Lib6G6.bundle' (code signature invalid in <...> '.../bin_body_Lib6G6.bundle' (errno=1) sliceOffset=0x00054000, codeBlobOffset=0x000500B0, codeBlobSize=0x00004CE0), ... - .../bin_body_Lib6G6.bundle
#<NoMethodError: undefined method register_from_key' for Traductor::ChromiumWdlg:Class> .../body_lib6chromiumwdlg.rbe:1498:in show'
.../body_lib6upgrade.rbe:864:in initialize__' .../lib6upgrade.rbe:161:in initialize'
.../lib6upgrade.rbe:154:in new' .../lib6upgrade.rbe:154:in show'
.../lib6upgrade.rbe:66:in time_for_check?' .../top_libfredo6.rbe:514:in block in after_startup'
So the update dialog can't fully init because the ChromiumWdlg engine's native module (bin_body_Lib6G6.bundle) fails to dlopen — macOS rejects its code signature at runtime.
Important: SketchUp 2027, with the literal same LibFredo6 16.1a files, has no problem at all — dialog renders fine, no console errors. So this doesn't look like a corrupted download or a bad LibFredo6 build; it looks like SketchUp 2025/2026 vs. 2027 differ in how they enforce code-signing/library validation for third-party native bundles at dlopen time.
What did NOT fix it (ruling out a leftover-config issue on my end):
Fully quit SketchUp.
Removed every Fredo6 folder + .rb loader from Plugins (LibFredo6, FredoTools, JointPushPull).
Deleted every orphaned Fredo6 key from the SketchUp prefs plist (ALToolPalette_Fredo6_, Fredo6_CheckForUpdateWarning.) — leftovers from older Fredo tools removed previously.
Reinstalled LibFredo6 16.1a completely fresh via Sketchucation Tools.
Exact same blank dialog / same console error on the totally clean install.
What DID fix it (local workaround): re-signing every .bundle under Fredo6_!LibFredo6/Binaries with a local ad-hoc signature:
find ".../Fredo6_!LibFredo6/Binaries" -name "*.bundle" -exec codesign --force --deep --sign - {} ;
After this, the dialog renders completely and the console is clean. codesign -dv on the original file actually reported the signature as valid (TeamIdentifier 66M89AU23J, properly signed 31 Aug 2026) — it's specifically the runtime dlopen/library-validation check inside SketchUp 2025/2026 that rejects it, not a malformed file.
This is obviously just a workaround I have to redo after every LibFredo6 update/reinstall, not a real fix — posting in case it helps track down why 2025/2026 reject it while 2027 doesn't.