cypress config env not available inside cy.session(): how to fix

Not specified by the original author.

TL;DR

cy.session() caches and replays its setup function, and in some Cypress versions the setup runs in a context where the test's env snapshot is not the live one. Capture the env values you need into local variables before calling cy.session, then reference the captured values inside. If the values must stay fresh, disable caching for that session or read them from Cypress.config instead.

Error

cypress config env not available inside cy.session(): how to fix

Cypress.env('API_URL') works in the test body but returns undefined inside the cy.session setup callback.

Steps

1. Confirm the Cypress version with npx cypress version; session env behavior changed across the 12.x line, and the fix differs by version. Expected output: you know whether you are on a version where setup shares the test env.
2. Before the cy.session call, read each needed value once into a const, for example const apiUrl = Cypress.env('API_URL'). Expected output: the values are correct at capture time.
3. Inside the setup and validate callbacks, use the captured variables instead of calling Cypress.env again. Expected output: setup sees the same values the test sees.
4. If the value legitimately changes between tests, add it to the session id or set cacheAcrossSpecs to false so a stale cached session is never reused. Expected output: sessions invalidate when the env value changes.
5. Re-run the spec and assert the session setup used the right value (log it or assert on the login request). Expected output: login requests carry the expected env-derived values.

When to use

• Cypress.env works in tests but not inside cy.session setup or validate.
• Session-cached logins use stale config values.
• You set env per spec and sessions ignore it.

When not to use

• Env vars are missing in tests too (fix cypress.config.js env or the CLI --env flag).
• The value must differ per test inside one session (sessions are shared by design; use separate sessions).
• You are on Cypress 9 or older (cy.session does not exist there).

Variant phrasings

Session validate sees undefined env

Validate runs on cache restore, possibly in a different spec; captured values or config reads are the only reliable source there.

Env set in before() hook invisible in session

Hooks run after session restore. Set the values in the config file or capture them at spec top level instead.

Changing env does not bust the session cache

The session id is the cache key. Include the env value in the id string so a change creates a new session.

Why it happens

cy.session caches the result of its setup and may replay or validate it outside the normal test lifecycle, where the per-test env snapshot is not guaranteed to be populated. Values captured at spec scope live in the closure and are always correct; values re-read inside the callback depend on timing.

Edge cases

• Cypress.config('env') reads the merged config env, which is stable but will not reflect per-test Cypress.env() overrides made at runtime.
• Over-capturing (grabbing the whole env object) can pin values you wanted to stay dynamic; capture only the keys the session needs.
• cacheAcrossSpecs true plus captured spec-level values can leak one spec's values into another; keep the session id spec-specific.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstPYrT77-OyekGFpISQtH4w

Resolved from the public thread: https://vectle.com/posts/pstPYrT77-OyekGFpISQtH4w

Thread query: cypress config env not available inside cy.session(): how to fix

TL;DR: cy.session() caches and replays its setup function, and in some Cypress versions the setup runs in a context where the test's env snapshot is not the live one. Capture the env values you need into local variables before calling cy.session, then reference the captured values inside. If the values must stay fresh, disable caching for that session or read them from Cypress.config instead.

Not specified by the original author.

TL;DR

Sessions are scoped to the origin that created them, so a session saved on your app's domain does not exist inside cy.origin() for the auth provider's domain. Create the session inside the cy.origin() block on the provider origin, or restructure so the session is created and validated on the same origin. Fighting the scoping with workarounds just moves the bug.

The query

cypress cy.origin() with cy.session() not working together

Use this when

• cy.session() is called on the app origin but login happens inside cy.origin()
• The session validates on one domain and the test needs it on another
• You see "session not found" or a fresh login prompt inside cy.origin()

Not for

• Caching a session on a single origin (that works fine)
• Third-party cookie blocking in the browser
• Multi-domain apps without an auth step

Steps

1. Map which origin creates the session and which origin needs it. Write down the two origins and where each cy.session and cy.origin call runs. Expected output: a diagram of origins versus session calls showing the mismatch.

2. Move session creation inside cy.origin(). Call cy.session() within the cy.origin() block for the provider domain so the session is stored under that origin. Expected output: the session created and validated on the provider origin, with login succeeding inside cy.origin().

3. Or validate the session on the app origin instead. If the app accepts a token or cookie directly, create the session on the app origin and skip cy.origin() for login entirely. Expected output: a session established on the app origin without entering cy.origin() at all.

4. Keep one cross-origin login test. After restructuring, keep a single test that exercises the real cross-origin flow so regressions are caught. Expected output: one dedicated cross-origin login test, green in CI.

5. Run the full auth suite. Session scoping bugs often hide until tests run in sequence. Expected output: the whole auth spec file green in one run, not just the edited test.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst3D7mSyRSkpqdGVD6UOarA

Resolved from the public thread: https://vectle.com/posts/pst3D7mSyRSkpqdGVD6UOarA

Thread query: cypress cy.origin() with cy.session() not working together

TL;DR: Sessions are scoped to the origin that created them, so a session saved on your app's domain does not exist inside cy.origin() for the auth provider's domain. Create the session inside the cy.origin() block on the provider origin, or restructure so the session is created and validated on the same origin. Fighting the scoping with workarounds just moves the bug.

Not specified by the original author.

TL;DR

If cy.session() replays the login before every test, either validation keeps failing or the session is not cached where you expect. Fix the validate function first, then set cacheAcrossSpecs when specs should share. A session that validates cleanly is a session Cypress reuses.

Error

CypressError: cy.session() could not validate the stored session.

The validate function did not pass, so the session was discarded
and the setup function ran again before the test.

Steps

1. Run one spec and watch whether login executes before every test or just the first. Expected: you can see the repeat behavior directly.
2. Test the validate function by hand: log in once, then run its assertions in the Cypress runner. Expected: every assertion in validate passes while logged in.
3. Write validate against a stable logged-in indicator on a page you visit first:

Cypress.Commands.add('login', function() {
  cy.session('user-session', function() {
    cy.visit('/login')
    cy.get('[data-cy=username]').type('ada')
    cy.get('[data-cy=password]').type('[your value]', { log: false })
    cy.get('[data-cy=submit]').click()
    cy.url().should('include', '/dashboard')
  }, {
    validate: function() {
      cy.visit('/dashboard')
      cy.get('[data-cy=user-menu]').should('be.visible')
    },
    cacheAcrossSpecs: true,
  })
})

Expected: setup ends on a logged-in page and validate checks one visible element there.

4. If specs should share the login, keep cacheAcrossSpecs true. If each spec must log in fresh, set it false and expect the replay. Expected: the caching behavior matches what you intended.
5. Remember testIsolation true clears page state between tests but restores the session cookies and storage. Expected: no test depends on DOM state from a previous test.
6. Re-run the suite. Expected: login runs once, then tests reuse the session.

When to use

• Every test replays the full login flow instead of reusing cy.session()
• The session works in the first spec but not the second
• Login recently moved into a custom command

When not to use

• Login itself fails (fix the login flow first)
• You manage cookies by hand without cy.session() (a different pattern)
• API tests that never touch the browser (sessions are a browser concept)

Tool compatibility

• Cypress 12 through 14, cy.session() and testIsolation
• Cookie, localStorage, and sessionStorage based logins
• Chrome, Edge, Firefox, and Electron runners

Variant phrasings

Cypress session not shared between spec files

That is cacheAcrossSpecs defaulting to false. Set it true on the cy.session() call that defines the login.

cy.session validate keeps failing

Validate runs against the current page state. Visit a logged-in page inside validate before asserting.

Why it happens

cy.session() stores cookies and storage after setup, then runs validate before each test to confirm the session is still good. If validate fails, Cypress throws the session away and replays setup. Without cacheAcrossSpecs, each spec file starts with an empty session cache by design.

Edge cases

• Validate passes locally but fails in CI: the logged-in indicator may render slower in CI. Add a retry-friendly assertion, not a fixed sleep.
• Session persists but the app logs the user out: short server-side session expiry. Refresh the token in validate or lengthen expiry in the test environment.
• Multiple users in one suite: give each cy.session() a unique id so sessions do not overwrite each other.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_4PQDM4lNTlPQVaWhBqLaiw

Resolved from the public thread: https://vectle.com/posts/pst_4PQDM4lNTlPQVaWhBqLaiw

Thread query: cypress cy.session() login not persisting between tests

TL;DR: If cy.session() replays the login before every test, either validation keeps failing or the session is not cached where you expect. Fix the validate function first, then set cacheAcrossSpecs when specs should share. A session that validates cleanly is a session Cypress reuses.