Skip to content

fix(mobile): keep organization settings with the active account - #3465

Open
vedanth-jadhav wants to merge 1 commit into
CapSoftware:mainfrom
vedanth-jadhav:fix/mobile-organization-settings-ownership
Open

vedanth-jadhav wants to merge 1 commit into
CapSoftware:mainfrom
vedanth-jadhav:fix/mobile-organization-settings-ownership

Conversation

@vedanth-jadhav

@vedanth-jadhav vedanth-jadhav commented Oct 27, 2026 •

Copy link
Copy Markdown

The organization settings screen keeps its draft and pending actions when the active organization changes. A late save can then replace the next organization's form, and a photo selected for the previous organization can be uploaded using the new active organization.

Reset the screen state on account or organization changes, ignore results from the old screen, and stop an old photo-picker or action-sheet flow before it can submit. If the settings response identifies a different organization from the current bootstrap, show an error rather than exposing editable fields.

Validation: 21 focused mobile tests pass (seven organization-settings, six profile-settings, eight existing auth-provider tests). Five new regressions fail against main 97c8d63; two existing controls pass. The new tests cover organization switching with a draft, a pending save, a pending photo picker and an old action sheet, plus a server/bootstrap mismatch. Combined with the pending auth fix in #3356, all 28 settings/auth-provider tests pass. Biome and git diff --check pass. Tests mount the screen with React Test Renderer and controlled native API responses; a native app build and full mobile typecheck were not run.

The mobile API resolves the active organization server-side and does not accept an expected organization ID. This fix protects changes known to the app and mismatched reads; an independent server-side organization switch before the app refreshes remains outside its guarantee. No API or dependency changes.

RetriggerView in GreptileConfidence Score: 5/5

The PR appears safe to merge; no actionable issues were found.

Summary

Keeps organization settings tied to the signed-in account and active organization.

  • Organization settings stay tied to the active account and organization.

vedanth-jadhav explicitly notes that an independent server-side organization switch before the app refreshes remains outside this fix's guarantee because the API does not accept an expected organization ID.

Review checks were read-only. Tests and a native build were not run.

Reviews (1) · Last reviewed commit: "fix(mobile): keep organization settings ..." · Reviewed by Greptile

@vercel

vercel Bot commented Oct 27, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
cap-status Skipped Skipped Oct 27, 2026 7:55am UTC

@vercel
vercel Bot temporarily deployed to Preview – cap-status October 27, 2026 07:55 Inactive

This branch was previously deployed

1 inactive deployment
Preview – cap-status — 3db939a7 Deployed Oct 27, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant