React Native @clerk/clerk-expo is not working as expected

Question

React Native @clerk/clerk-expo is not working as expected

SherifMoShalaby opened this issue 8 months ago · 22 comments

SherifMoShalaby commented 8 months ago

Preliminary Checks

I have reviewed the documentation: https://clerk.com/docs
I have searched for existing issues: https://github.com/clerk/javascript/issues
I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)
This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.

Reproduction

https://github.com/Galaxies-dev/whatsapp-clone-react-native

Publishable key

pk_test_cG93ZXJmdWwtcGVnYXN1cy0yNi5jbGVyay5hY2NvdW50cy5kZXYk

Description

Steps to reproduce:

Clone the provided Repo
add .env file & add EXPO_PUBLIC_CLERK_PUBLISHABLE_KEY={the one provided in the issue from the "Publishable key"}
npm install
npx expo run:ios

Expected behavior:

The application to work as before adding the ``````

Actual behavior:

After adding

<ClerkProvider publishableKey={process.env.clerkPublishableKey}>

The application is now giving me: "cannot find native module ExpoApplication"

Environment

System:
    OS: macOS 14.4.1
    CPU: (12) arm64 Apple M2 Max
    Memory: 5.13 GB / 64.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.20.2 - ~/.nvm/versions/node/v18.20.2/bin/node
    npm: 10.5.0 - ~/.nvm/versions/node/v18.20.2/bin/npm
    Watchman: 2024.04.22.00 - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 124.0.6367.119
    Safari: 17.4.1

Answer 1 · 2024-05-08T15:51:43.000Z

Just keep installing the packages. Seems like the @clerk/clerk-expo package doesn't declare all the native expo packages needed. Every time you see the error, run npx expo install expo-application (or expo-xxxx), rebuild and repeat until errors disappear

Answer 2 · 2024-05-08T16:31:18.000Z

Get the same error and to fix it I added different packages, but then I get:

Error: Not a valid base64 encoded string length

This error is located at:
    in ClerkProvider (created by RootLayoutNav)
   ...

Probably Expo 51 isn't supported yet for Clerk (?)

Answer 3 · 2024-05-08T17:38:20.000Z

Possibly related, but no idea: expo/expo#26570 (comment)

Answer 4 · 2024-05-08T19:29:10.000Z

Get the same error and to fix it I added different packages, but then I get:
Error: Not a valid base64 encoded string length

This error is located at:
    in ClerkProvider (created by RootLayoutNav)
   ...
Probably Expo 51 isn't supported yet for Clerk (?)

Right after upgrading the Expo from 50 to 51
I'm receiving the same error Error: Not a valid base64 encoded string length

No code changes besides following Expo steps to upgrade that is, installing latest and install --fix

Answer 5 · 2024-05-08T19:46:01.000Z

If you're getting Error: Not a valid base64 encoded string length, it seems to be related to Expo v51. The Clerk team is aware of it and working on a fix. Current discussion is on Discord here: https://discord.com/channels/856971667393609759/1234973673946087534

Answer 6 · 2024-05-09T19:45:59.000Z

If you're getting Error: Not a valid base64 encoded string length, it seems to be related to Expo v51. The Clerk team is aware of it and working on a fix. Current discussion is on Discord here: https://discord.com/channels/856971667393609759/1234973673946087534

@statico I am not able to see this discussion, does it still exist?

Answer 7 · 2024-05-10T08:59:13.000Z

Any updates on this? I would really like to be able to use my app again with sdk 51

Answer 8 · 2024-05-10T17:23:05.000Z

Any update here?

Answer 9 · 2024-05-10T18:38:23.000Z

@statico I am not able to see this discussion, does it still exist?

@vflorrez1 @leo-mangold You have to be a member of the Clerk Discord to see it. There doesn't appear to be a fixed invite URL (thanks, Discord) but Googling found me this: https://discord.com/invite/b5rXHjAg7A

There's a PR in progress: #3354

Answer 10 · 2024-05-10T20:46:29.000Z

I'm having very similar problems like this just submitted an issue aswell

Answer 11 · 2024-05-10T21:41:49.000Z

I'm facing the same problem as well

Answer 12 · 2024-05-10T22:17:20.000Z

Potentially resolved by #3326, which removes expo-application as a peer dependency.

Answer 13 · 2024-05-11T19:22:24.000Z

I can confirm that this resolves the issue!

Answer 14 · 2024-05-13T05:56:50.000Z

This should be fixed by #3326 and was published with @clerk/clerk-expo@1.1.0.

Please install the latest version of @clerk/clerk-expo in order to fix your issue:

npm install @clerk/clerk-expo@latest

Answer 15 · 2024-05-14T14:08:58.000Z

This issue is not yet resolved as of today 14may2024 if any one find the solution please help here

Answer 16 · 2024-05-14T14:14:25.000Z

This issue is not yet resolved as of today 14may2024 if any one find the solution please help here

It was fixed on the latest version.

Answer 17 · 2024-05-14T14:27:49.000Z

This issue is not yet resolved as of today 14may2024 if any one find the solution please help here

It was fixed on the latest version.

Thanks for reply i will check and inform you

Answer 18 · 2024-05-15T09:09:43.000Z

run: npm install @clerk/clerk-expo@latest
its fixed now

Answer 19 · 2024-05-23T20:12:05.000Z

run: npm install @clerk/clerk-expo@latest its fixed now

It didn't actually :)

Answer 20 · 2024-05-23T20:12:34.000Z

This should be fixed by #3326 and was published with @clerk/clerk-expo@1.1.0.

Please install the latest version of @clerk/clerk-expo in order to fix your issue:
npm install @clerk/clerk-expo@latest

Still not working

Answer 21 · 2024-10-10T16:41:39.000Z

run: npm install @clerk/clerk-expo@latest its fixed now

Still not working

Answer 22 · 2024-10-10T20:11:45.000Z

I'm sorry to hear that! I haven't used clerk-expo in over 4 months idk if the issue is new or not but at the time it was fixed i recommend creating a new issue on there official repo like i did at the time