preflight manifest/permissions hangs after TypeError on macOS arm64

[flutterrausch]

Thanks for building GPC. It has been very useful for getting a Play release flow wired up from scripts.

I hit a reproducible hang in the offline preflight scanner on macOS arm64 with GPC 0.9.88. The command prints a TypeError, but then does not exit; I have to kill it from a wrapper timeout.

Environment:

• GPC: 0.9.88
• Install: Homebrew
• Platform: macOS 26.5.1, Darwin arm64
• Shell: zsh
• Auth/config: I did not run gpc config init; auth is provided by env/service-account file. Authenticated commands such as gpc doctor and gpc validate <same-aab> --track internal work. The affected manifest and permissions preflight commands are offline scanners, so this does not appear to be an auth failure.

Minimal repro:

gpc preflight manifest build/app/outputs/bundle/release/app-release.aab --fail-on error

Also hangs:

gpc preflight permissions build/app/outputs/bundle/release/app-release.aab --fail-on error
gpc preflight build/app/outputs/bundle/release/app-release.aab --metadata stores/playstore/metadata --source . --fail-on error

Output before the hang:

✦ First time? Run gpc config init to get set up.

TypeError: null is not an object (evaluating 'self2.context.fd')
      at <anonymous> (/$bunfs/root/gpc-darwin-arm64:3349:29)
      at pendGo (/$bunfs/root/gpc-darwin-arm64:3301:7)
      at onCb (/$bunfs/root/gpc-darwin-arm64:3290:15)
      at <anonymous> (/$bunfs/root/gpc-darwin-arm64:3316:11)
      at <anonymous> (node:fs:194:82)

What I expected:

• The manifest/permissions scanner should either complete or exit non-zero after the TypeError.

What happens:

• The command stays running until killed. I reproduced this with a 45s timeout.

Extra isolation:

• gpc preflight metadata stores/playstore/metadata --fail-on error returns normally.
• gpc preflight codescan . returns normally.
• gpc validate <same-aab> --track internal returns normally.

Current workaround:

• I wrapped preflight in a shell timeout and treat timeout as a validation failure.

[yasserstudio]

Thanks for the detailed report, especially the stack trace and the note that it hangs rather than exits. That was enough to pin down what is going on.

Two separate defects here:

1. The crash. The offline scanner opens the AAB with yauzl in file-descriptor mode. In the standalone Homebrew binary (compiled with Bun) that file layer hands yauzl a null descriptor, which is the self2.context.fd TypeError you see. The Node-based npm install uses ordinary OS file descriptors and should not hit this path.

2. The hang. The promise that wraps the ZIP read is not settling on that particular failure, and the file handle stays open, so the process never exits. That is a bug on its own and will be fixed so the command always exits with a proper code even when a read fails.

Both are targeted for the next patch (v0.9.89). The likely fix is to read the archive without the file-descriptor layer so the standalone binary behaves the same as Node.

To unblock yourself now, try the Node install and run the same command:

npm install -g @gpc-cli/cli
gpc preflight manifest build/app/outputs/bundle/release/app-release.aab --fail-on error

If that works it also confirms the diagnosis. Thanks again for the clear repro.

[yasserstudio]

Fixed in v0.9.89 (now live on npm and the Homebrew tap).

The offline preflight scanner no longer reads archives through the file-descriptor path that returned a null descriptor under the standalone binary, so the crash and the hang are both gone. The scanner also can no longer hang on a corrupt or truncated file.

Since you installed via Homebrew, please upgrade and re-run the command that failed:

brew update && brew upgrade gpc
gpc preflight manifest build/app/outputs/bundle/release/app-release.aab --fail-on error

(Or download the gpc-darwin-arm64 asset directly from the v0.9.89 release.) It should complete and exit cleanly now. Please confirm and I will close this out. Thanks again for the clear repro and stack trace.

[yasserstudio]

Friendly nudge: the preflight crash and hang were fixed in v0.9.89 and remain fixed in the current v0.9.92. When you get a chance, please upgrade (brew update && brew upgrade gpc) and confirm the scan completes cleanly on your end and I will close this out. No rush, and thanks again for the clear repro and stack trace.

[flutterrausch]

Hey, you were off github for some days. Tried to contact you on twitter to no avail. sSo I refactored to gplay or sth, sorry man.

[yasserstudio]

Totally understand, and sorry for how the timing played out.

Two things worth clarifying for the record:

The "off GitHub" days were a false-positive account suspension on GitHub's side, which they reversed after review. Bad luck that it landed exactly when you were trying to reach me.

I also never received a DM or mention on X, so that one seems to have gotten lost as well. Sorry you hit two dead ends in a row.

For anyone landing here later: the crash and the hang were both fixed in v0.9.89, released three days after the report above, and the fix is still in place in the current release (brew update && brew upgrade gpc).

@flutterrausch if you ever want to give it another look, the door is open and I would be glad to help you get set up again. Closing this as fixed. Thanks again for the clear repro and stack trace, it made the fix quick.

[flutterrausch]

Those stupid automated shutdowns. Had all my scripting with your great tool done 2d before :)