| commit | cd6247b58fc31d7351bf823f145e9ff04e33555f | [log] [tgz] |
|---|---|---|
| author | Jérôme Lebel <jlebel@chromium.org> | Fri Sep 05 13:37:57 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 05 13:37:57 2025 |
| tree | f7575560fb8839a89f18d270c7b0d68936585a8b | |
| parent | c8f931506c4b27d089ac101052fec28d1e825fc4 [diff] |
[iOS] Avoid reentry in add account coordinator It is unclear how it possible, but while there is a way to have a stack of coordinator, the user is able to sign-in using another UI: - SigninAndHistorySyncCoordinator - InstantSigninCoordinator - AddAccountSigninCoordinator In the bug, AddAccountSigninCoordinator is stuck by displaying the alert dialog (to say that it is not possible to open to add account at the same time). Since the primary account is set, InstantSigninCoordinator stops itself and shutdown AddAccountSigninCoordinator. While the add account coordinator stops, it also stops the alert dialog. By stopping the alert dialog, this triggers a second stop of the add account coordinator. To avoid a reentry, when before stopping the alert dialog, `alertCoordinator.noInteractionAction` needs to be set to nil. This patch should be cherry-picked in M141, and maybe in M140. Fixed: 441677851 Change-Id: I6511ea7c447d853a5e578e1d6dfd36106b2d1fa8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6917619 Auto-Submit: Jérôme Lebel <jlebel@chromium.org> Reviewed-by: Boris Sazonov <bsazonov@chromium.org> Commit-Queue: Boris Sazonov <bsazonov@chromium.org> Cr-Commit-Position: refs/heads/main@{#1511520}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.