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 #444] [MERGED] docs: improve expo doc by including Expo client plugin setup #3292

New Issue
Closed
opened 2026-03-13 10:47:24 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 10:47:24 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/444
Author: @pakenfit
Created: 11/7/2024
Status: ✅ Merged
Merged: 11/7/2024
Merged by: @Bekacru

Base: main ← Head: docs/improve-expo-plugin-docs

📝 Commits (1)

  • 3dc1f30 docs: improve expo doc by including Expo client plugin setup

📊 Changes

1 file changed (+14 additions, -0 deletions)

View changed files

📝 docs/content/docs/integrations/expo.mdx (+14 -0)

📄 Description

This PR updates the Expo integration documentation to include important instructions for enabling social authentication using Better Auth. Specifically, it adds details on importing the client plugin from @better-auth/expo/client and passing it to the plugins array when initializing the auth client.

Changes Made:

In the "Initialize Better Auth Client" step:

  • I added instructions to import the client plugin from @better-auth/expo/client.

  • I included a code snippet demonstrating how to pass the plugin to the plugins array.

  • I provided a concise list explaining the importance of the client plugin:

    • Social Authentication Support: enables social auth flows by handling authorization URLs and callbacks within the Expo web browser.
    • Secure Cookie Management: Stores cookies securely and automatically adds them to request headers.

Reason for Changes:

The client plugin is essential for social authentication to function properly in Expo apps.
Some developers ( like myself ) may encounter issues with social auth and cookie management if they are unaware of the need to include the client plugin.

🔄 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/444 **Author:** [@pakenfit](https://github.com/pakenfit) **Created:** 11/7/2024 **Status:** ✅ Merged **Merged:** 11/7/2024 **Merged by:** [@Bekacru](https://github.com/Bekacru) **Base:** `main` ← **Head:** `docs/improve-expo-plugin-docs` --- ### 📝 Commits (1) - [`3dc1f30`](https://github.com/better-auth/better-auth/commit/3dc1f30d943f15cbc176bb185a520c57e881b8e4) docs: improve expo doc by including Expo client plugin setup ### 📊 Changes **1 file changed** (+14 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/integrations/expo.mdx` (+14 -0) </details> ### 📄 Description This PR updates the Expo integration documentation to include important instructions for enabling social authentication using Better Auth. Specifically, it adds details on importing the client plugin from `@better-auth/expo/client` and passing it to the plugins array when initializing the auth client. ### Changes Made: In the _"Initialize Better Auth Client"_ step: - I added instructions to import the client plugin from `@better-auth/expo/client`. - I included a code snippet demonstrating how to pass the plugin to the plugins array. - I provided a concise list explaining the importance of the client plugin: - **Social Authentication Support:** enables social auth flows by handling authorization URLs and callbacks within the Expo web browser. - **Secure Cookie Management:** Stores cookies securely and automatically adds them to request headers. ### Reason for Changes: The client plugin is essential for social authentication to function properly in Expo apps. Some developers ( like myself ) may encounter issues with social auth and cookie management if they are unaware of the need to include the client plugin. --- <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-03-13 10:47:24 -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#3292
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?