---
title: "Verify iOS deferred link routing after sign-in"
description: "Check an externally prepared iOS universal link that requires authentication, preserving its destination through sign-in without exposing private content."
canonical_url: "https://vostride.com/agent-library/ios-flows/universal-link-after-sign-in.md"
md_url: "https://vostride.com/agent-library/ios-flows/universal-link-after-sign-in.md"
content_kind: "recipe"
topic: "ios-flows"
---

# Verify iOS deferred link routing after sign-in

Check an externally prepared iOS universal link that requires authentication, preserving its destination through sign-in without exposing private content.

## Risk

A deferred link can be lost during authentication or replayed in the wrong workspace. Check the public pre-authentication surface, the exact eventual destination, and the absence of cross-account content.

## Fixtures

- A sandbox iOS app target with bundleId, device profile, and explicit app-state policy matching the signed-out fixture.
- An external link-delivery fixture using an owned sandbox universal-link domain and a private document identifier; the fixture records the delivered URL.
- A disposable user authorized for that document, a second same-title document outside its scope, and a read-only permission oracle.

## Steps

1. Confirm the external fixture has opened the prepared universal link on the test device and verify the app shows sign-in without private document text.
2. Complete the product-supported sign-in as the authorized test user and verify the account identity shown by the app.
3. Verify the app continues to the exact linked document identifier, workspace, and fixture body instead of stopping at a generic home screen.
4. Navigate back to the workspace, reopen the document from its list, and verify the linked and list-based destinations are the same record.
5. Inspect the independent permission oracle and verify the user still lacks access to the other same-title document and has no unintended membership changes.

## Expected results

- No private body content appears before successful authentication.
- The post-login destination retains the original document and workspace identity.
- The permission boundary remains unchanged by opening the link.

## False-pass traps

- A matching title does not establish that the original deferred destination survived.
- An already signed-in app skips the authentication transition central to this scenario.

## Cleanup

- Sign out the sandbox account and clear the external link-delivery fixture.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa mobile testing](/docs/agent-qa/guides/mobile-testing.md)
- [agent-qa test](/docs/agent-qa/configuration/test.md)
- [agent-qa hooks](/docs/agent-qa/guides/hooks.md)

- [iOS application QA recipes](/agent-library/ios-flows.md)
- [Software factory QA library](/agent-library.md)