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

[GH-ISSUE #1495] Enable multiple client ids for google provider #8789

New Issue
Closed
opened 2026-04-13 03:59:34 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-04-13 03:59:34 -05:00
Owner
Copy Link

Originally created by @samducker on GitHub (Feb 19, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/1495

Is this suited for github?

  • [Y] Yes, this is suited for github

Is your feature request related to a problem? Please describe.

Currently you can only add one client ID for google, unlike other providers like clerk and supabase where you can add a comma seperated list. This is so you can use the native sdks on an android device, ios, and web.

Describe the solution you'd like

Ability to add multiple client ids for google provider, and also add skip nonce checks as an option.

Describe alternatives you've considered

Using web only login approach, but then you lack the beautiful native mobile login!

Additional context

No response

Originally created by @samducker on GitHub (Feb 19, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/1495 ### Is this suited for github? - [Y] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. Currently you can only add one client ID for google, unlike other providers like clerk and supabase where you can add a comma seperated list. This is so you can use the native sdks on an android device, ios, and web. ### Describe the solution you'd like Ability to add multiple client ids for google provider, and also add skip nonce checks as an option. ### Describe alternatives you've considered Using web only login approach, but then you lack the beautiful native mobile login! ### Additional context _No response_
GiteaMirror added the lockedenhancement labels 2026-04-13 03:59:34 -05:00
GiteaMirror commented 2026-04-13 03:59:35 -05:00
Author
Owner
Copy Link

@matheusmichels commented on GitHub (May 1, 2025):

+1 to this, I can't get Google sign in working on web + iOS/Android because of this limitation

<!-- gh-comment-id:2845588890 --> @matheusmichels commented on GitHub (May 1, 2025): +1 to this, I can't get Google sign in working on web + iOS/Android because of this limitation
GiteaMirror commented 2026-04-13 03:59:36 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Jul 31, 2025):

Hi, @samducker. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested support for multiple Google client IDs in the provider configuration to enable native SDK usage across Android, iOS, and web.
  • Currently, only a single client ID is supported, limiting Google sign-in functionality across platforms.
  • You also suggested adding an option to skip nonce checks.
  • A contributor agreed this limitation affects cross-platform sign-in and noted alignment with other providers like Clerk and Supabase.
  • The issue remains unresolved with no recent updates.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of better-auth by commenting here.
  • If I don’t hear back within 7 days, this issue will be automatically closed.

Thanks for your understanding and contribution!

<!-- gh-comment-id:3140514318 --> @dosubot[bot] commented on GitHub (Jul 31, 2025): Hi, @samducker. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested support for multiple Google client IDs in the provider configuration to enable native SDK usage across Android, iOS, and web. - Currently, only a single client ID is supported, limiting Google sign-in functionality across platforms. - You also suggested adding an option to skip nonce checks. - A contributor agreed this limitation affects cross-platform sign-in and noted alignment with other providers like Clerk and Supabase. - The issue remains unresolved with no recent updates. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of better-auth by commenting here. - If I don’t hear back within 7 days, this issue will be automatically closed. Thanks for your understanding and contribution!
GiteaMirror commented 2026-04-13 03:59:36 -05:00
Author
Owner
Copy Link

@li-kai commented on GitHub (Aug 1, 2025):

I believe this issue is still relevant.

<!-- gh-comment-id:3143461660 --> @li-kai commented on GitHub (Aug 1, 2025): I believe this issue is still relevant.
GiteaMirror commented 2026-04-13 03:59:37 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Oct 31, 2025):

Hi, @samducker. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested support for multiple Google client IDs in the provider configuration to enable native SDK sign-in on Android, iOS, and web.
  • Currently, only one client ID is supported, which limits cross-platform Google sign-in functionality.
  • You also suggested an option to skip nonce checks.
  • Other users, including matheusmichels and li-kai, have confirmed this issue remains relevant.
  • The issue was previously marked as stale pending further feedback.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of better-auth by commenting below to keep the discussion open.
  • If I do not hear back within 7 days, this issue will be automatically closed.

Thank you for your understanding and contribution!

<!-- gh-comment-id:3473846384 --> @dosubot[bot] commented on GitHub (Oct 31, 2025): Hi, @samducker. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested support for multiple Google client IDs in the provider configuration to enable native SDK sign-in on Android, iOS, and web. - Currently, only one client ID is supported, which limits cross-platform Google sign-in functionality. - You also suggested an option to skip nonce checks. - Other users, including matheusmichels and li-kai, have confirmed this issue remains relevant. - The issue was previously marked as stale pending further feedback. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of better-auth by commenting below to keep the discussion open. - If I do not hear back within 7 days, this issue will be automatically closed. Thank you for your understanding and contribution!
GiteaMirror commented 2026-04-13 03:59:38 -05:00
Author
Owner
Copy Link

@A-Boudi commented on GitHub (Nov 2, 2025):

I think this is still relevant.

<!-- gh-comment-id:3477865799 --> @A-Boudi commented on GitHub (Nov 2, 2025): I think this is still relevant.
GiteaMirror commented 2026-04-13 03:59:38 -05:00
Author
Owner
Copy Link

@better-auth-agent[bot] commented on GitHub (Nov 2, 2025):

This feature is still valid and actively under consideration. The recommended next steps are:

• Verify you’re using the latest version of the package since work has been done toward supporting an array of Google client IDs and a skip-nonce option for native mobile logins.

• Check your GitHub issue tracker and pull request list for the progress on the multi‑client ID support, as similar enhancements have received discussion and preliminary implementation.

• If you’re a contributor or have the ability to test experimental builds, try the latest beta that incorporates these changes and provide feedback via GitHub. This ensures that the proper client selection is working across iOS, Android, and web while confirming that the nonce skipping behaves securely.

By following these steps you can help move the feature forward toward full integration into the main release [1][2].

Diagram • Discord • GitHub

Diagram Join Star

<!-- gh-comment-id:3477865943 --> @better-auth-agent[bot] commented on GitHub (Nov 2, 2025): This feature is still valid and actively under consideration. The recommended next steps are: • Verify you’re using the latest version of the package since work has been done toward supporting an array of Google client IDs and a skip-nonce option for native mobile logins. • Check your GitHub issue tracker and pull request list for the progress on the multi‑client ID support, as similar enhancements have received discussion and preliminary implementation. • If you’re a contributor or have the ability to test experimental builds, try the latest beta that incorporates these changes and provide feedback via GitHub. This ensures that the proper client selection is working across iOS, Android, and web while confirming that the nonce skipping behaves securely. By following these steps you can help move the feature forward toward full integration into the main release [[1]](https://github.com/better-auth/better-auth/issues/1495)[[2]](https://github.com/better-auth/better-auth/issues/2546). <!-- bot:webhook reply v1 --> [Diagram](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) • [Discord](https://discord.gg/better-auth) • [GitHub](https://github.com/better-auth/better-auth) [![Diagram](https://img.shields.io/badge/Diagram-2b3137?style=flat-square)](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) [![Join](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&style=flat-square)](https://discord.gg/better-auth) [![Star](https://img.shields.io/badge/star-181717?logo=github&logoColor=white&style=flat-square)](https://github.com/better-auth/better-auth)
GiteaMirror commented 2026-04-13 03:59:39 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Feb 1, 2026):

Hi, @samducker. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested support for configuring multiple Google client IDs to enable native SDK sign-in across Android, iOS, and web.
  • You also asked for an option to skip nonce checks to improve flexibility.
  • Other users have confirmed this limitation still affects cross-platform Google sign-in functionality.
  • The better-auth-agent mentioned ongoing work toward supporting multiple client IDs and nonce skipping.
  • Users are encouraged to test the latest beta versions and provide feedback to help move this feature forward.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of better-auth by commenting here.
  • If I don’t hear back within 7 days, this issue will be automatically closed to keep the backlog manageable.

Thanks for your understanding and contribution!

<!-- gh-comment-id:3831313121 --> @dosubot[bot] commented on GitHub (Feb 1, 2026): Hi, @samducker. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested support for configuring multiple Google client IDs to enable native SDK sign-in across Android, iOS, and web. - You also asked for an option to skip nonce checks to improve flexibility. - Other users have confirmed this limitation still affects cross-platform Google sign-in functionality. - The better-auth-agent mentioned ongoing work toward supporting multiple client IDs and nonce skipping. - Users are encouraged to test the latest beta versions and provide feedback to help move this feature forward. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of better-auth by commenting here. - If I don’t hear back within 7 days, this issue will be automatically closed to keep the backlog manageable. Thanks for your understanding and contribution!
GiteaMirror commented 2026-04-13 03:59:39 -05:00
Author
Owner
Copy Link

@maxvaljan commented on GitHub (Mar 25, 2026):

relevant

<!-- gh-comment-id:4127162542 --> @maxvaljan commented on GitHub (Mar 25, 2026): relevant
GiteaMirror commented 2026-04-13 03:59:39 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 2, 2026):

This issue has been locked as it was closed more than 7 days ago. If you're experiencing a similar problem or you have additional context, please open a new issue and reference this one.

<!-- gh-comment-id:4173718709 --> @github-actions[bot] commented on GitHub (Apr 2, 2026): This issue has been locked as it was closed more than 7 days ago. If you're experiencing a similar problem or you have additional context, please open a new issue and reference this one.
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 enhancement locked
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#8789
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?