-
-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to resolve plugin for module "@sentry/react-native/expo" #4283
Comments
I got the same error |
Facing the same issue with trying to upgrade to Expo SDK 52 |
as a matter of fact, implimented sentry in my 49 expo SDK and it worked, but i think its just a bug that hasnt yet brrn fixed by sentry |
Worked only on SDK 51 but I got the error when I upgrade to SDK 52 |
Hello everyone, thank you for letting us know, sadly we have not reproduced this yet, can you check if the |
When i try installing the @sentry/react-native/expo app, it is displayed as
undefined in my package. Json and the error passists until i edit the app.
Json plugin object and change the @sentry/react-native/expo to
sentry/react-native then the error wont show up again
…On Tue, Nov 19, 2024, 3:27 PM Krystof Woldrich ***@***.***> wrote:
Hello everyone,
thank you for letting us know, sadly we have not reproduced this yet,
can you check if the ***@***.***/react-native/expo.js exists in
your node_modules?
—
Reply to this email directly, view it on GitHub
<#4283 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7KDUX3EDOUTDKFJJOFOU732BMVCJAVCNFSM6AAAAABR5XNPAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBVGU2TGOJXGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I think the @sentry/react-native/expo library has a bug that needs to be
fixed or its just not compatible with the expo-doctor Library
…On Tue, Nov 19, 2024, 3:33 PM Gaming Harzad ***@***.***> wrote:
When i try installing the @sentry/react-native/expo app, it is displayed
as undefined in my package. Json and the error passists until i edit the
app. Json plugin object and change the @sentry/react-native/expo to
sentry/react-native then the error wont show up again
On Tue, Nov 19, 2024, 3:27 PM Krystof Woldrich ***@***.***>
wrote:
> Hello everyone,
>
> thank you for letting us know, sadly we have not reproduced this yet,
>
> can you check if the ***@***.***/react-native/expo.js exists in
> your node_modules?
>
> —
> Reply to this email directly, view it on GitHub
> <#4283 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A7KDUX3EDOUTDKFJJOFOU732BMVCJAVCNFSM6AAAAABR5XNPAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBVGU2TGOJXGM>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
I'm having this problem on Windows, but it works fine on Linux in WSL2 |
@krystofwoldrich in my case |
Issue created on the Expo repo with reproduction: expo/expo#33054 |
…n Windows (#33106) # Why Fixes #33054, getsentry/sentry-react-native#4283 # How When using nested module specifiers as config plugin, we need to use the forward slash (even on Windows) -- as we are resolving module specifiers, not actual file paths. This fixes that to properly resolve `@sentry/react-native/expo` references on Windows. # Test Plan - `git clone https://github.com/jerone/expo-doctor-sentry` - `cd expo-doctor-sentry` - `npm ci` - `npx expo config` - Should work on Windows # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). --------- Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
Hello, when will it be released please ? |
Thank you @jerone for opening the Expo issue and supplying the repro. @Abdeldmh The fix was merged in expo/expo#33106 and likely will be in the next Expo SDK hotfix release. At the moment you can use Note: |
Waiting for release of expo/expo#33106 before closing this issue. |
The changes were released in https://www.npmjs.com/package/expo/v/52.0.9 |
What React Native libraries do you use?
Expo (mobile only) (52.0.7)
Are you using sentry.io or on-premise?
sentry.io (SaS)
@sentry/react-native SDK Version
6.1.0
How does your development environment look like?
(node:14112) [DEP0040] DeprecationWarning: The
punycode
module is deprecated. Please use a userland alternative instead.(Use
node --trace-deprecation ...
to show where the warning was created)info Fetching system and libraries information...
System:
OS: Windows 10 10.0.19045
CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1145G7 @ 2.60GHz
Memory: 16.51 GB / 31.69 GB
Binaries:
Node:
version: 22.11.0
path: C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm:
version: 10.9.0
path: C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: Not Found
Visual Studio: Not Found
Languages:
Java: Not Found
Ruby: Not Found
npmPackages:
"@react-native-community/cli":
installed: 15.1.2
wanted: ^15.1.2
react:
installed: 18.3.1
wanted: 18.3.1
react-native:
installed: 0.76.2
wanted: 0.76.2
react-native-windows: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: Not found
newArchEnabled: Not found
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Sentry.init()
Sentry.init({
dsn: "https://ae458ee624bf9a970fdc32e7634a536b:f43243fb1d8e637a71e7125ca4fa7b22@o4506953980444672.ingest.us.sentry.io/4506953985753088",
tracesSampleRate: 0.2,
enabled: !DEV,
});
Steps to Reproduce
Expected Result
Successful build
Actual Result
Starting project at xxx
env: load .env.local
env: export SENTRY_AUTH_TOKEN
PluginError: Failed to resolve plugin for module "@sentry/react-native/expo" relative to xxx
The text was updated successfully, but these errors were encountered: