Fix QR Login: treat authenticate success(false) as rejection, not completion#25520
Draft
Fix QR Login: treat authenticate success(false) as rejection, not completion#25520
Conversation
Adds `unused_closure_parameter` to `.swiftlint.yml`'s `only_rules` and applies SwiftLint's autocorrection across the codebase. 340 violations were autofixed across 167 files; no manual fixes or `swiftlint:disable` comments were needed. Part of the Orchard SwiftLint rollout campaign. --- Generated with the help of Claude Code, https://claude.com/claude-code Co-Authored-By: Claude Code Opus 4.7 (1M context) <noreply@anthropic.com>
Collaborator
Generated by 🚫 Danger |
…jection When the server responds to the authenticate request but sets authenticated=false, the success callback fires with `false`. Previously this was ignored (using `_`) and the UI incorrectly moved to the done state with a qrLoginAuthenticated track. Now we check the Bool: false → show authentication failed error + track failure; true → proceed to done state as before. Also adds a test case for the server-rejected scenario. Agent-Logs-Url: https://github.com/wordpress-mobile/WordPress-iOS/sessions/378e64a4-563e-46cb-ad8b-017d726bc2ba Co-authored-by: mokagio <1218433+mokagio@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] [WIP] Address feedback on enabling SwiftLint rule: unused_closure_parameter
Fix QR Login: treat authenticate success(false) as rejection, not completion
May 4, 2026
Contributor
|
| App Name | WordPress | |
| Configuration | Release-Alpha | |
| Build Number | 32092 | |
| Version | PR #25520 | |
| Bundle ID | org.wordpress.alpha | |
| Commit | d845891 | |
| Installation URL | 2scpsgfj3p5e0 |
Contributor
|
| App Name | Jetpack | |
| Configuration | Release-Alpha | |
| Build Number | 32092 | |
| Version | PR #25520 | |
| Bundle ID | com.jetpack.alpha | |
| Commit | d845891 | |
| Installation URL | 2jamnaj81n78o |
Base automatically changed from
mokagio/swiftlint-unused-closure-parameter
to
trunk
May 5, 2026 05:00
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.


QRLoginServiceRemote.authenticatecalls its success closure withfalsewhen the server responds but rejects the authentication (i.e.,authenticated == falsein the API response). The coordinator was ignoring this value and always transitioning to the.donestate, incorrectly firingqrLoginAuthenticatedand showing the completion UI on a rejected login.Changes
QRLoginVerifyCoordinator: Replace{ _ inwith{ authenticated in }and guard on the value —falsenow transitions to.error, callsview.showAuthenticationFailedError(), and tracksqrLoginVerifyCodeFailed:QRLoginVerifyCoordinatorTests: Add.authenticationRejectedmock expectation (callssuccess(false)) and a corresponding testtestConfirmFromWaitingForUserVerificationAndAuthenticationRejectedasserting the coordinator reaches.error, shows the auth-failed UI, and records the failure track.