developers/fxplug/ #306

2023-12-16T19:46:12Z

giscus[bot]
bot Dec 16, 2023

developers/fxplug/

This section of the site is dedicated to FxPlug.

mkuhnkey · 2023-12-16T19:46:13Z

mkuhnkey
Dec 16, 2023 — with giscus

Service.pluginkit/Contents/MacOS/../Frameworks/PluginManager.framework/Versions/B/PluginManager' (fat file, but missing compatible architecture (have 'i386,x86_64', need 'arm64'))

MacBook Pro (16 inch) M1 (arm64e) maOS Sonoma with Xcode 15 does not support FxPlug PluginManager's "fat-binary"

11 replies

latenitefilms Dec 16, 2023
Maintainer

Can you share the full Terminal command I need to enter?

mkuhnkey Dec 16, 2023

That's it...
% lipo PluginManager -info

Should provide the "Universal Binary" aka "fat-binary" with the supported architectures.

latenitefilms Dec 16, 2023
Maintainer

fatal error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo: can't open input file: PluginManager (No such file or directory)

mkuhnkey Dec 16, 2023

....I'll be in the corner for awhile...banging my head on the wall. Thanks for the "info" and your time, much appreciated!

mkuhnkey Dec 18, 2023 — with giscus

Followup....Resolved by deleting "Derived Data" in Xcode. FxPlug4 Good to Go!

mkuhnkey · 2024-01-05T20:55:55Z

mkuhnkey
Jan 5, 2024 — with giscus

Examples...FxPlug4.2.9 Have me "banging-my-head-in-the-corner"...Specifically "FxPictureInPicture" (macOS Sonoma M1, Xcode 15).....dyld[88289]: Library not loaded: @rpath/PluginManager.framework/Versions/B/PluginManager
Referenced from: <60A0B8E5-7C2F-304E-B5FB-BE60279C31A9> /Users/mikekuhnkey/Library/Developer/Xcode/DerivedData/FxPictureInPicture-fcpuksxzjnmgkqbijshcugpgtthp/Build/Products/Release/FxPictureInPicture.app/Contents/PlugIns/FxPictureInPicture.pluginkit/Contents/Frameworks/FxPlug.framework/Versions/A/FxPlug .......Note "Versions/A" is supported by FxPlux4 (x86_64 & arm64).......However PluginManager is limited to "Version/B" (i386 & 86_64)?..........Resulting in
"missing compatible architecture (have 'i386,x86_64', need 'arm64'".....PluginManager.tbd <--tapi is a problem??

1 reply

latenitefilms Jan 5, 2024
Maintainer

The FxPictureInPicture sample project in FxPlug v4.2.9 works fine for me out-of-the-box?

I'm on a 16-inch MacBook Pro (M1 Max, 64GB RAM, 8TB SSD) running macOS Sonoma 14.1.2 and Xcode 15.1.

mkuhnkey · 2024-01-05T21:26:56Z

mkuhnkey
Jan 5, 2024

Did you run a "Release" build with no Debug? Was it working in Motion/FCPx? I ran "out-of-the-box" also...Deleted "DerivedData" and "Clean Build"...exact same issue with PluginManager missing arm64. Was able to build FxBrightness attached to Motion but it didn't produce an "effect" in Templates.

…

On Jan 5, 2024, at 3:03 PM, Chris Hocking ***@***.***> wrote: The FxPictureInPicture sample project in FxPlug v4.2.9 works fine for me out-of-the-box? I'm on a 16-inch MacBook Pro (M1 Max, 64GB RAM, 8TB SSD) running macOS Sonoma 14.1.2 and Xcode 15.1. — Reply to this email directly, view it on GitHub <#306 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEC7OJCZFN3UHCERRDHBCQDYNBTDTAVCNFSM6AAAAABAXZLQHGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DAMRWHE4TM>. You are receiving this because you commented.

1 reply

latenitefilms Jan 5, 2024
Maintainer

Yes, it works fine in Motion:

mkuhnkey · 2024-01-05T21:36:56Z

mkuhnkey
Jan 5, 2024

I'm also getting "Thread 1 signal SIGBRT"....assume it's related PluginManager (Xcode error)

…

On Jan 5, 2024, at 3:03 PM, Chris Hocking ***@***.***> wrote: The FxPictureInPicture sample project in FxPlug v4.2.9 works fine for me out-of-the-box? I'm on a 16-inch MacBook Pro (M1 Max, 64GB RAM, 8TB SSD) running macOS Sonoma 14.1.2 and Xcode 15.1. — Reply to this email directly, view it on GitHub <#306 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEC7OJCZFN3UHCERRDHBCQDYNBTDTAVCNFSM6AAAAABAXZLQHGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DAMRWHE4TM>. You are receiving this because you commented.

0 replies

mkuhnkey · 2024-01-05T21:51:38Z

mkuhnkey
Jan 5, 2024

Was able to "manually create" FxPlug4 in Xcode (Developer Documentation)...but it used Swift in the document. Was able to attach to Motion, but seemed to hang "ProRegistration" and the Motion icon just bounced regularly. So,some success with FXPlug4 and Swift but the "Examples" FxPlug4.2..9 are low-level Objective-C for FxPictureInPicture.

…

On Jan 5, 2024, at 3:03 PM, Chris Hocking ***@***.***> wrote: The FxPictureInPicture sample project in FxPlug v4.2.9 works fine for me out-of-the-box? I'm on a 16-inch MacBook Pro (M1 Max, 64GB RAM, 8TB SSD) running macOS Sonoma 14.1.2 and Xcode 15.1. — Reply to this email directly, view it on GitHub <#306 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEC7OJCZFN3UHCERRDHBCQDYNBTDTAVCNFSM6AAAAABAXZLQHGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DAMRWHE4TM>. You are receiving this because you commented.

1 reply

latenitefilms Jan 5, 2024
Maintainer

When you create a new FxPlug4 using the Xcode template, you can select Objective-C OR Swift.

mkuhnkey · 2024-01-05T22:12:45Z

mkuhnkey
Jan 5, 2024

Tried BOTH...Objective-C used XIB for interface....and Swift was the other. I'm impressed by your results, but really frustrated! Did "EXAMPLES" Subcategory install by itself in Motion?

…

On Jan 5, 2024, at 3:57 PM, Chris Hocking ***@***.***> wrote: When you create a new FxPlug4 using the Xcode template, you can select Objective-C OR Swift. — Reply to this email directly, view it on GitHub <#306 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEC7OJHYA37O4XI2N2DWRFTYNBZLPAVCNFSM6AAAAABAXZLQHGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DAMRXGI4TC>. You are receiving this because you commented.

1 reply

latenitefilms Jan 5, 2024
Maintainer

Yes. When you build the application in Xcode and run it, macOS detects the FxPlug4 extension inside the application bundle, and registers it. Once registered Motion adds it to the Library, based on the settings you have in the FxPlug's plist file.

mkuhnkey · 2024-01-05T22:36:58Z

mkuhnkey
Jan 5, 2024

Any Thoughts....
#0 0x0000000187f6255c in __abort_with_payload ()
#1 0x0000000187f6eb10 in abort_with_payload_wrapper_internal ()
#2 0x0000000187f6eb44 in abort_with_payload ()
#3 0x0000000187ef5584 in dyld4::halt(char const*, dyld4::StructuredError const*) ()
#4 0x0000000187ef2254 in dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*) ()
#5 0x0000000187ef0edc in start ()
Guess I'll go look at "Wrapper"....

14 replies

mkuhnkey Jan 6, 2024

Good information! I'll clean up a bit, build and such...Give it a rest and try tomorrow.

mkuhnkey Jan 6, 2024

...for some reason "pluginkit -m FxPlug" is not working now?

mkuhnkey Jan 6, 2024

pluginkit is working...debug of Motion now returns:.........Unable to load PlugIn: FxPictureInPicture due to error: 4, Extension process exited while/after acquiring startup assertion.

mkuhnkey Jan 7, 2024

I've broken the "out-of-process" capability in XPC. Motion starts and lives. History..Re-installed Xcode and installed FxPlug4.sdk...all FxPlug EXAMPLES showed up in the Xcode "browser" when started initially...bit of troubleshooting required. Seems to be issue with Xcode "build phases" while working with FxPlug4 (Copy and Code Sign PluginManager.framework) under XPC Service. Xcode --> Debug Executable -->Motion (using "Console" in MacOS) confirms crash of "out-of-process" capability.

mkuhnkey Jan 7, 2024 — with giscus

Translated Report (Full Report Below)

Process: FxBrightness XPC Service [30943]
Path: /Users/USER/Library/Developer/Xcode/DerivedData/FxBrightness-emwaebtuzspagudpnqzkpldhxcmq/Build/Products/Debug/FxBrightness.app/Contents/PlugIns/FxBrightness XPC Service.pluginkit/Contents/MacOS/FxBrightness XPC Service
Identifier: FxBrightness-XPC-Service
Version: 1.0 (1)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
Responsible: Motion [30940]
User ID: 501

Date/Time: 2024-01-07 08:43:15.7668 -0600
OS Version: macOS 14.2.1 (23C71)
Report Version: 12
Anonymous UUID: D2F7717B-4DF4-A459-8F86-25BC01D39092

Sleep/Wake UUID: 024E772F-75AD-4B7B-AF92-03CBC2BED272

Time Awake Since Boot: 110000 seconds
Time Since Wake: 7120 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Termination Reason: Namespace DYLD, Code 1 Library missing
Library not loaded: @rpath/PluginManager.framework/Versions/B/PluginManager
Referenced from: <60A0B8E5-7C2F-304E-B5FB-BE60279C31A9> /Users/USER/Library/Developer/Xcode/DerivedData/FxBrightness-emwaebtuzspagudpnqzkpldhxcmq/Build/Products/Debug/FxBrightness.app/Contents/PlugIns/FxBrightness XPC Service.pluginkit/Contents/Frameworks/FxPlug.framework/Versions/A/FxPlug
Reason: tried: '/Users/mikekuhnkey/Library/Developer/Xcode/DerivedData/FxBrightness-emwaebtuzspagudpnqzkpldhxcmq/Build/Products/Debug/FxBrightness.app/Contents/PlugIns/FxBrightness XPC Service.pluginkit/Contents/Frameworks/FxPlug.framework/Versions/A/Frameworks/PluginManager.framework/Versions/B/PluginManager' (no such file), '/System/Library/PrivateFrameworks/PluginManager.framework/Versions/B/PluginManager' (no such file, not in dyld cache), '/System/Volumes/Preboot/Cryptexes/OS/System/Library/PrivateFrameworks/PluginManager.framework/Versions/B/PluginManager' (no such file), '/usr/lib/swift/PluginManager.framework/Versions/B/PluginMan
(terminated at launch; ignore backtrace)

mkuhnkey · 2024-01-10T16:37:04Z

mkuhnkey
Jan 10, 2024

Think this is "rsync" issue: (architecture diffs between PluginManager & FxPlug)
Appears to be why DYLD doesn't happen?
mkdir -p "${TARGET_BUILD_DIR}/${FRAMEWORKS_FOLDER_PATH}" <~~~ still puzzles me
% file /Library/Developer/Frameworks/PluginManager.framework/Versions/B/PluginManager
/Library/Developer/Frameworks/PluginManager.framework/Versions/B/PluginManager: Mach-O universal binary with 2 architectures: [i386:Mach-O dynamically linked shared library i386] [x86_64:Mach-O 64-bit dynamically linked shared library x86_64]

rsync --archive --links --whole-file --no-owner --no-group --checksum --exclude='Headers' "/Library/Developer/Frameworks/PluginManager.framework/" "${TARGET_BUILD_DIR}/${FRAMEWORKS_FOLDER_PATH}/PluginManager.framework/"
if [ "$?" -ne 0 ]; then echo "error: rsync failed; couldn't embed PluginManager.framework"; exit 1; fi

%file /Library/Developer/Frameworks/FxPlug.framework/Versions/A/FxPlug
/Library/Developer/Frameworks/FxPlug.framework/Versions/A/FxPlug: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64] [arm64:Mach-O 64-bit dynamically linked shared library arm64]

0 replies

mkuhnkey · 2024-01-10T20:27:09Z

mkuhnkey
Jan 10, 2024

Terminal:

1 reply

mkuhnkey Jan 10, 2024

FxPlug returns:
% file /Library/Developer/Frameworks/FxPlug.framework/Versions/A/Fxplug
/Library/Developer/Frameworks/FxPlug.framework/Versions/A/Fxplug: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64] [arm64:Mach-O 64-bit dynamically linked shared library arm64]
/Library/Developer/Frameworks/FxPlug.framework/Versions/A/Fxplug (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64
/Library/Developer/Frameworks/FxPlug.framework/Versions/A/Fxplug (for architecture arm64): Mach-O 64-bit dynamically linked shared library arm64

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

developers/fxplug/ #306

{{title}}

Replies: 9 comments 30 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

developers/fxplug/ #306

giscus[bot] bot Dec 16, 2023

developers/fxplug/

Replies: 9 comments · 30 replies

mkuhnkey Dec 16, 2023 — with giscus

latenitefilms Dec 16, 2023 Maintainer

latenitefilms Dec 16, 2023 Maintainer

mkuhnkey Dec 18, 2023 — with giscus

mkuhnkey Jan 5, 2024 — with giscus

latenitefilms Jan 5, 2024 Maintainer

latenitefilms Jan 5, 2024 Maintainer

latenitefilms Jan 5, 2024 Maintainer

latenitefilms Jan 5, 2024 Maintainer

mkuhnkey Jan 7, 2024 — with giscus

Translated Report (Full Report Below)

giscus[bot]
bot Dec 16, 2023

Replies: 9 comments 30 replies

mkuhnkey
Dec 16, 2023 — with giscus

latenitefilms Dec 16, 2023
Maintainer

latenitefilms Dec 16, 2023
Maintainer

mkuhnkey
Jan 5, 2024 — with giscus

latenitefilms Jan 5, 2024
Maintainer

latenitefilms Jan 5, 2024
Maintainer

latenitefilms Jan 5, 2024
Maintainer

latenitefilms Jan 5, 2024
Maintainer