itch.io

Hey — I've been trying to get UInjectForge 1.0.1 (macOS Intel build) running and worked through it with Claude to help diagnose what's going wrong. Wanted to pass along what I found in case it's useful.

Here's the sequence:

• Fresh download, moved UInjectForge.app to Applications — got "The application 'UInjectForge' can't be opened" with no further detail (turned out the execute bit wasn't set on the main binary).
• After fixing permissions and clearing the quarantine flag, the next launch attempt gave "'UInjectForge' is damaged and can't be opened. You should move it to the Trash." — the standard Gatekeeper signature-rejection message.
• Running codesign --verify --deep --strict --verbose=4 on the app showed a sealed resource is missing or invalid, with essentially every file under Contents/MacOS and Contents/Resources/Runtime (~250 files) flagged as "file modified" relative to the embedded code signature.
• To get past Gatekeeper and see what was actually happening, I ad-hoc re-signed it locally (codesign --force --deep --sign -). It then launched but crashed immediately. Running the binary directly from Terminal showed: Failed to load .../libhostfxr.dylib ... slice is not valid mach-o file — meaning that dylib isn't a valid Mach-O binary anymore, not just mis-signed.
• I deleted the app and did a completely independent fresh re-download, and got the identical "damaged" result on the new copy too.

Since a second, separate download reproduced the exact same signature/corruption pattern, this doesn't look like a bad download on my end — it looks like the distributed 1.0.1 macOS-Intel build itself doesn't match its own code signature. One thing that stood out: the RELEASE-INFO.json bundled inside the app reports "version": "1.0.0" and "preparedInfoPlistNormalized": false, even though the release is labeled 1.0.1 — made me wonder if this particular build skipped a finalization/normalization step before being signed and uploaded.

My Mac: Intel Core i5, macOS 15.7.2. I couldn't generate the app's own Support Bundle since it won't stay open long enough to do that.

Is there a corrected 1.0.1 Intel build available, or is this a known issue with this release?