You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keep the existing single REST request flow unchanged and add a separate full-width concurrent-request card.
Run 5, 10, 20, or 50 mixed read-only requests using API Resources and Describe Global, weighted toward the cheaper API Resources call and avoiding permission-dependent endpoints.
Show queued, in-flight, success, and failure state per request, with copyable diagnostics when a failed square is tapped.
Support manual, revoke-in-flight, and logout-in-flight scenarios bound to the account captured when the batch starts.
Update the AuthFlowTester test inventory and screenshots.
Dependency
The concurrent refresh paths exposed cooperative-executor starvation in the SDK safe collection writers. The focused UI validation below was run with #4174 applied; merge #4174 before relying on this suite as a stable concurrent-token baseline.
Validation
AuthFlowTester app and UI-test targets build successfully.
Valid RTR session: 20/20 mixed requests succeeded with peak in-flight of 20.
Deterministic failure: the batch settled and the failed square exposed the request number, type, endpoint, status, message, and Copy action.
Logout during an RTR batch remained logged out after a cold relaunch.
DPoP + RTR invalid-token recovery completed 20/20 requests while preserving binding and rotating access and refresh tokens.
DPoP revoke during flight settled the batch and a follow-up request recovered successfully.
Multi-user logout during flight preserved the remaining RTR account across a cold relaunch and removed the logged-out DPoP + RTR account.
Focused final reruns passed for the valid RTR batch and logout-under-load cold relaunch.
Screenshots
The completed grid below was captured from the passing authenticated 20-request XCTest run. The error-details image uses the deterministic DEBUG failure hook exercised by the UI suite.
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
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
Dependency
The concurrent refresh paths exposed cooperative-executor starvation in the SDK safe collection writers. The focused UI validation below was run with #4174 applied; merge #4174 before relying on this suite as a stable concurrent-token baseline.
Validation
Screenshots
The completed grid below was captured from the passing authenticated 20-request XCTest run. The error-details image uses the deterministic DEBUG failure hook exercised by the UI suite.
Completed 20-request batch
Tappable request error details