Repository navigation
docs: record Windows Android build recovery and remaining gates - #43
Merged
Merged
Conversation
Document the CMake path override, successful emulator and ARM64 builds, Docker restart requirement, and authorized admin sign-in prerequisite. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Windows native APK build previously failed on React Native CMake/Ninja paths longer than 260 characters. Document the verified Gradle path override and record successful emulator and ARM64 APK builds, while preserving the remaining Docker restart and hosted account acceptance gates.
Related Issue
Related to #4 for the remaining hosted authentication/device acceptance; this PR does not close that issue.
Changes
-Pexpo.android.cmakeObjectPathMax=240.This is a documentation-only repository change. Machine installations, ignored environment values, APKs, and operator scratch files are not committed.
Validation
git diff --check: passed.npx.cmd jest tests/security/secret-exposure.test.js --runInBand: 1 suite / 4 tests passed.Status: ok, 1526ms).user_not_found/require_user_login; no changes applied.Screenshots
No UI changes. Emulator launch evidence remains locally in ignored
.codex-artifacts/emulator-launch.png.Security Review
Only the four reviewed Markdown files are included. Local credentials, the owner email configuration, signing material, generated Android files, and APKs remain ignored. No hosted role grant or provisioning apply occurred. APKs use generated development signing; production signing and physical-device acceptance are not claimed.
Cost Review
External spend remains PHP 0 / USD 0. No billing, payment method, paid cloud build, or automatic overage service was enabled.
Known Limitations
Next Steps
Restart Windows, verify
docker info, rerun the database checks, establish the authorized owner Auth identity, grant and verify its admin role, then complete physical-device and two-principal acceptance. Owner approval is required before merge.