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 #1645] All $fetch requests are prepended with /api/auth #26172

New Issue
Closed
opened 2026-04-17 16:39:14 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-17 16:39:14 -05:00
Owner
Copy Link

Originally created by @wharacembell on GitHub (Mar 2, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/1645

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

I am using better auth with expo and hono, and the authentication flow is working, but when trying to make fetch requests using the library's $fetch, the path of all requests are prepended with /api/auth .

Current vs. Expected behavior

When calling $fetch("/test") it should resolve to baseUrl/test not baseUrl/api/auth/test

What version of Better Auth are you using?

1.2 and the previous versions

Provide environment information

Expo dev build

Which area(s) are affected? (Select all that apply)

Client

Auth config (if applicable)

import { createAuthClient } from "better-auth/react";
import { expoClient } from "@better-auth/expo/client";
import * as SecureStore from "expo-secure-store";

export const authClient = createAuthClient({
  baseURL:
    process.env.EXPO_PUBLIC_API_URL /* base url of your Better Auth backend. */,
  plugins: [
    expoClient({
      scheme: "myapp",
      storagePrefix: "myapp",
      storage: SecureStore,
    }),
  ],
  storage: SecureStore,
});

Additional context

No response

Originally created by @wharacembell on GitHub (Mar 2, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/1645 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce I am using better auth with expo and hono, and the authentication flow is working, but when trying to make fetch requests using the library's $fetch, the path of all requests are prepended with /api/auth . ### Current vs. Expected behavior When calling $fetch("/test") it should resolve to baseUrl/test not baseUrl/api/auth/test ### What version of Better Auth are you using? 1.2 and the previous versions ### Provide environment information ```bash Expo dev build ``` ### Which area(s) are affected? (Select all that apply) Client ### Auth config (if applicable) ```typescript import { createAuthClient } from "better-auth/react"; import { expoClient } from "@better-auth/expo/client"; import * as SecureStore from "expo-secure-store"; export const authClient = createAuthClient({ baseURL: process.env.EXPO_PUBLIC_API_URL /* base url of your Better Auth backend. */, plugins: [ expoClient({ scheme: "myapp", storagePrefix: "myapp", storage: SecureStore, }), ], storage: SecureStore, }); ``` ### Additional context _No response_
GiteaMirror added the lockedbug labels 2026-04-17 16:39:15 -05:00
GiteaMirror commented 2026-04-17 16:39:19 -05:00
Author
Owner
Copy Link

@ahmedivy commented on GitHub (Mar 3, 2025):

Yes, same issue with me

<!-- gh-comment-id:2694050808 --> @ahmedivy commented on GitHub (Mar 3, 2025): Yes, same issue with me
GiteaMirror commented 2026-04-17 16:39:20 -05:00
Author
Owner
Copy Link

@awesomepandapig commented on GitHub (Mar 5, 2025):

Same issue here.

Notably it's also ignoring the baseURL entirely and sending requests to the wrong subdomain!
example.com/api/auth when it should be sending to api.example.com/auth

<!-- gh-comment-id:2700344057 --> @awesomepandapig commented on GitHub (Mar 5, 2025): Same issue here. Notably it's also ignoring the baseURL entirely and sending requests to the wrong subdomain! `example.com/api/auth` when it should be sending to `api.example.com/auth`
GiteaMirror commented 2026-04-17 16:39:21 -05:00
Author
Owner
Copy Link

@juan-altatech commented on GitHub (Mar 30, 2025):

still an issue

<!-- gh-comment-id:2764689684 --> @juan-altatech commented on GitHub (Mar 30, 2025): still an issue
GiteaMirror commented 2026-04-17 16:39:21 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Apr 12, 2025):

We're going to remove the recommendation to use $fetch. The /api/auth prefix is intentional - the real issue is that we're suggesting using $fech api in the docs

<!-- gh-comment-id:2799046499 --> @Bekacru commented on GitHub (Apr 12, 2025): We're going to remove the recommendation to use `$fetch`. The `/api/auth` prefix is intentional - the real issue is that we're suggesting using $fech api in the docs
GiteaMirror commented 2026-04-17 16:39:22 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Apr 12, 2025):

if you want to use better fetch check its docs https://better-fetch.vercel.app/

<!-- gh-comment-id:2799046698 --> @Bekacru commented on GitHub (Apr 12, 2025): if you want to use better fetch check its docs https://better-fetch.vercel.app/
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 bug 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#26172
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?