github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 07:18:56 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #4369] [MERGED] docs: hint to use credentials: 'omit' for authenticated requests #13583

New Issue
Closed
opened 2026-04-13 09:00:55 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 09:00:55 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/4369
Author: @hendrik-krebs
Created: 9/2/2025
Status: ✅ Merged
Merged: 9/2/2025
Merged by: @himself65

Base: canary ← Head: docs/expo-omit-credentials-hint

📝 Commits (1)

  • 04078f9 docs: hint to use credentials: 'omit' for authenticated requests

📊 Changes

1 file changed (+5 additions, -1 deletions)

View changed files

📝 docs/content/docs/integrations/expo.mdx (+5 -1)

📄 Description

Some requests return 401 because cookies are not sent when fetch is called without credentials: "omit". This PR gives a hint to set credentials: "omit" so auth cookies are included.

Related:

Summary by cubic

Update Expo docs to show using credentials: "omit" in fetch when you set the Cookie header manually. This prevents 401s caused by credentials: "include" interfering with the cookies you pass.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/4369 **Author:** [@hendrik-krebs](https://github.com/hendrik-krebs) **Created:** 9/2/2025 **Status:** ✅ Merged **Merged:** 9/2/2025 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `docs/expo-omit-credentials-hint` --- ### 📝 Commits (1) - [`04078f9`](https://github.com/better-auth/better-auth/commit/04078f9a4566bb1fee09a3935cef091a6107de78) docs: hint to use credentials: 'omit' for authenticated requests ### 📊 Changes **1 file changed** (+5 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/integrations/expo.mdx` (+5 -1) </details> ### 📄 Description Some requests return 401 because cookies are not sent when `fetch` is called without `credentials: "omit"`. This PR gives a hint to set `credentials: "omit"` so auth cookies are included. Related: - React Native issue: https://github.com/facebook/react-native/issues/23185 - Better Auth issues: #3180, #3034 (these might be related) <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Update Expo docs to show using credentials: "omit" in fetch when you set the Cookie header manually. This prevents 401s caused by credentials: "include" interfering with the cookies you pass. <!-- End of auto-generated description by cubic. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-13 09:00:55 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#13583
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?