Repository navigation
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
🚧 Files skipped from review as they are similar to previous changes (5)
Included review availability: Your plan includes up to 10 reviews per rolling hour; 2 remain after this review. 📝 WalkthroughWalkthroughThe Android APK release tag is pinned to Merge Risk: ⚪ Minimal · up to This localized change pins Android downloads to the current release and adds recovery guidance for stalled downloads; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
src/renderer/src/components/mobile/mobile-platform-copy.test.ts (1)
9-12: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winAssert the complete APK URL.
The test only checks that the URL contains the release tag and that
getInstallCopy()returns the same exported constant. It would pass if the repository path or APK filename were wrong. Assert the complete expected URL.Proposed test adjustment
expect(ORCA_ANDROID_APK_RELEASE_TAG).toBe('mobile-android-v0.0.37') - expect(ORCA_ANDROID_APK_URL).toContain(ORCA_ANDROID_APK_RELEASE_TAG) - expect(getInstallCopy('android', 'stable').url).toBe(ORCA_ANDROID_APK_URL) + const expectedUrl = + 'https://github.com/stablyai/orca/releases/download/mobile-android-v0.0.37/app-release.apk' + expect(ORCA_ANDROID_APK_URL).toBe(expectedUrl) + expect(getInstallCopy('android', 'stable').url).toBe(expectedUrl)
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 24b7ab9a-20ef-4b06-9782-865a6f2ca8f1
📥 Commits
Reviewing files that changed from the base of the PR and between 9825706 and 538c7c32e29c44730e0ddf34bba9d3d20cb0ace7.
📒 Files selected for processing (9)
docs/readme/README.es.mddocs/readme/README.fr.mddocs/readme/README.ja.mddocs/readme/README.ko.mddocs/readme/README.pt.mddocs/readme/README.zh-CN.mdsrc/renderer/src/components/mobile/mobile-platform-copy.test.tssrc/renderer/src/components/mobile/mobile-platform-copy.tssrc/renderer/src/components/settings/MobileSettingsPane.tsx
538c7c3 to
4554d35
Compare
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
Settings and mobile install copy still linked mobile-android-v0.0.32 while README shipped 0.0.37, and phone browsers often stall near 99% with no recovery hint. Point UI/docs at the current APK tag and document the desktop-transfer workaround for stuck downloads. Closes stablyai#11444
4554d35 to
4a57315
Compare
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
|
Refreshed onto current Head
The six translated README changes were removed because #14696 already landed the 0.0.43 links. Verification:
@coderabbitai review |
|
✅ Action performedReview finished.
|
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
|
Closing: both halves have been handled on main, by a different route. The APK link pinning landed via #14696 / #13565 — For the "stuck at 99%" copy, Closing to keep my open-PR queue honest. If this turns out to be wrong I'll reopen — please just say so, or reopen it yourself, within the next 7 days. |
ELI5
Android downloads can occasionally stall near completion. Orca now tells users how to recover by downloading the APK on a computer and transferring it to the phone, while keeping every renderer install entry pointed at one verified release URL.
What Changed
mobile-android-v0.0.43release.Why
#11444 describes an external browser/OS download failure that Orca cannot repair directly. A visible alternative install path prevents that failure from blocking onboarding. Sharing the renderer URL also prevents Mobile and Settings from drifting during future release updates.
Linked Issue
Fixes #11444
Visual Proof
Not captured locally: this session does not provide the repository-required
$electronvalidation skill. The copy is covered by a happy-dom rendering test; no screenshot is claimed.Testing
mobile-platform-copy.test.tsandMobileSettingsPane.test.tsx— 2 files, 2 tests passed.mobile-android-v0.0.43/app-release.apkreturned HTTP 200.pnpm typecheckpnpm lint, including localization catalog, extraction, and coverage checks.pnpm run check:code-quality:changed— 0 findings across 4 code files.pnpm exec oxfmt --checkon all 5 changed files.pnpm test,pnpm build, and rendered Electron screenshot were not run locally.AI Disclosure
Codex (GPT-5) was used to refresh the branch, migrate the release tag, add regression coverage, and review the final diff.
Review
Please focus on whether Settings is the right surface for the recovery guidance and whether the shared renderer URL fits the Android release-update workflow.
Agent skill upstream boundary
Notes
Checklist
pnpm testandpnpm buildwere not run locally; focused tests and CI cover the change.Author