No metadata available in React Native Directory #810

Closed
opened 2026-03-13 08:05:16 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @sangdth on GitHub (Mar 8, 2025).

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

Hi, thanks for the great library, I enjoy using better-auth so much!

Currently, while trying to setup the Expo project with New Architecture guide, I face this warning after running the npx expo-doctor@latest:

✖ [Validate packages against React Native Directory package metadata]
The following issues were found when validating your dependencies against React Native Directory:
No metadata available: @better-auth/expo, better-auth

I'm not expert in React Native world, so I wonder:

  • Is this issue minor and I can ignore it?
  • Will I have any potential issue in the near future if I keep using better-auth?

Thanks again.

Current vs. Expected behavior

Expected: Pass all checkings from npx expo-doctor@latest

What version of Better Auth are you using?

1.2.3

Provide environment information

- Next.js 15
- Expo SDK 52
- React Native 0.76

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

Client

Auth config (if applicable)

import { betterAuth } from "better-auth"
export const auth = betterAuth({
  emailAndPassword: {  
    enabled: true
  },
});

Additional context

Ref to New Architechture: https://docs.expo.dev/guides/new-architecture/#enable-the-new-architecture-in-an-existing-project

Originally created by @sangdth on GitHub (Mar 8, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce Hi, thanks for the great library, I enjoy using better-auth so much! Currently, while trying to setup the Expo project with New Architecture guide, I face this warning after running the `npx expo-doctor@latest`: ``` ✖ [Validate packages against React Native Directory package metadata] The following issues were found when validating your dependencies against React Native Directory: No metadata available: @better-auth/expo, better-auth ``` I'm not expert in React Native world, so I wonder: - Is this issue minor and I can ignore it? - Will I have any potential issue in the near future if I keep using better-auth? Thanks again. ### Current vs. Expected behavior Expected: Pass all checkings from `npx expo-doctor@latest` ### What version of Better Auth are you using? 1.2.3 ### Provide environment information ```bash - Next.js 15 - Expo SDK 52 - React Native 0.76 ``` ### Which area(s) are affected? (Select all that apply) Client ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" export const auth = betterAuth({ emailAndPassword: { enabled: true }, }); ``` ### Additional context Ref to New Architechture: https://docs.expo.dev/guides/new-architecture/#enable-the-new-architecture-in-an-existing-project
GiteaMirror added the bug label 2026-03-13 08:05:16 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Jun 12, 2025):

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

Issue Summary:

  • You reported a warning about missing metadata for @better-auth/expo and better-auth when running npx expo-doctor@latest.
  • The concern is whether this warning could affect the Better Auth library in your Expo project, especially with the New Architecture guide.
  • No comments or activity have been made on this issue yet.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of the better-auth repository. If it is, you can keep the discussion open by commenting here.
  • If there is no further activity, this issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jun 12, 2025): Hi, @sangdth. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - You reported a warning about missing metadata for `@better-auth/expo` and `better-auth` when running `npx expo-doctor@latest`. - The concern is whether this warning could affect the Better Auth library in your Expo project, especially with the New Architecture guide. - No comments or activity have been made on this issue yet. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of the better-auth repository. If it is, you can keep the discussion open by commenting here. - If there is no further activity, this issue will be automatically closed in 7 days. Thank you for your understanding and contribution!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#810