Sentry Logger [Warn]: SentryError: Native is disabled #243

tigar · 2022-03-08T01:10:28Z

Summary

The package sentry-expo is causing the SentryError written in the title above. I have tried uninstalling and reinstalling various packages, as well as the backlog of fixes in the closed issues tab of this repo.

I was able to reproduce the issue with a clean build of an expo project (linked below) also running expo 44.0 SDK and the latest version of sentry-expo. Has anyone else encountered this problem recently?

Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare!

managed

What platform(s) does this occur on?

Android, iOS, Web

SDK Version (managed workflow only)

44.0

Environment

Expo CLI 5.0.3 environment info:
System:
OS: macOS 11.6.3
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm
Watchman: 2021.08.23.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
Android SDK:
API Levels: 29, 30, 31
Build Tools: 28.0.3, 29.0.0, 31.0.0
System Images: android-30 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 4.2 AI-202.7660.26.42.7486908
Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
npmPackages:
expo: ~44.0.0 => 44.0.6
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
npmGlobalPackages:
expo-cli: 5.0.3
Expo Workflow: managed

Reproducible demo or steps to reproduce from a blank project

Here is a demo repository where I am encountering the same issue as on the app I am developing: https://github.com/tigar/sentry-test

The text was updated successfully, but these errors were encountered:

lavender16 · 2022-03-10T04:32:53Z

I experienced the same issue after upgrading SDK 41 to 44. How to fix it?

Sentry Logger [Warn]:, [SdkInfo] Native SDK Info retrieval failed...something could be wrong with your Sentry installation:
at node_modules\react-native\Libraries\LogBox\LogBox.js:118:10 in registerWarning
at node_modules\react-native\Libraries\LogBox\LogBox.js:64:8 in warnImpl
at node_modules\react-native\Libraries\LogBox\LogBox.js:37:4 in console.warn
at node_modules\expo\build\environment\react-native-logs.fx.js:18:4 in warn
at node_modules\tslib\tslib.js:130:20 in step
at node_modules\tslib\tslib.js:113:92 in rejected
at node_modules\tslib\tslib.js:129:40 in step
at node_modules\@sentry\react\dist\profiler.js:176:105 in Wrapped
at node_modules\regenerator-runtime\runtime.js:45:36 in tryCatch
at node_modules\regenerator-runtime\runtime.js:274:29 in invoke
at node_modules\moment\moment.js:5472:37 in humanize
at node_modules\promise\setimmediate\core.js:37:13 in tryCallOne
at node_modules\promise\setimmediate\core.js:123:24 in setImmediate$argument_0
at node_modules\react-native\Libraries\Core\Timers\JSTimers.js:123:14 in _callTimer
at node_modules\react-native\Libraries\Core\Timers\JSTimers.js:177:14 in _callImmediatesPass
at node_modules\react-native\Libraries\Core\Timers\JSTimers.js:437:30 in callImmediates
at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:388:6 in __callImmediates
at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:132:6 in __guard$argument_0
at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:365:10 in __guard
at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:131:4 in flushedQueue

Sentry Logger [Warn]:, [SentryError: Native is disabled]
at node_modules\react-native\Libraries\LogBox\LogBox.js:118:10 in registerWarning
at node_modules\react-native\Libraries\LogBox\LogBox.js:64:8 in warnImpl
at node_modules\react-native\Libraries\LogBox\LogBox.js:37:4 in console.warn
at node_modules\expo\build\environment\react-native-logs.fx.js:18:4 in warn
at node_modules\tslib\tslib.js:130:20 in step
at node_modules\tslib\tslib.js:113:92 in rejected
at node_modules\tslib\tslib.js:129:40 in step
at node_modules\@sentry\react\dist\profiler.js:177:28 in Wrapped
at node_modules\regenerator-runtime\runtime.js:45:36 in tryCatch
at node_modules\regenerator-runtime\runtime.js:274:29 in invoke
at node_modules\moment\moment.js:5472:37 in humanize
at node_modules\promise\setimmediate\core.js:37:13 in tryCallOne
at node_modules\promise\setimmediate\core.js:123:24 in setImmediate$argument_0
at node_modules\react-native\Libraries\Core\Timers\JSTimers.js:123:14 in _callTimer
at node_modules\react-native\Libraries\Core\Timers\JSTimers.js:177:14 in _callImmediatesPass
at node_modules\react-native\Libraries\Core\Timers\JSTimers.js:437:30 in callImmediates
at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:388:6 in __callImmediates
at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:132:6 in __guard$argument_0
at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:365:10 in __guard
at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:131:4 in flushedQueue

tigar · 2022-03-10T23:09:41Z

While using Expo SDK 44, I was able to get things working with sentry-expo v4.0.0 and @sentry/react-native v2.5.2

It's unideal since I'm losing some Sentry functionality but at least Sentry is able to capture native events now. Hopefully the latest version of sentry-expo will work with Expo SDK 44 soon

jimmihagenTrifecta · 2022-03-30T01:25:43Z

our stack traces look different from those by @lavender16 above, but the issue seems similar. I was sure to do the package install using "yarn expo install sentry-expo". Errors and messages do create new Sentry issues.
Sentry.Native.nativeCrash() generates these traces, as does an uncaught exception :

Sentry Logger [Warn]:, [SentryError: Native is disabled]
at node_modules/@sentry/utils/dist/logger.js:81:12 in consoleSandbox$argument_0
at node_modules/@sentry/utils/dist/logger.js:34:25 in consoleSandbox
at node_modules/@sentry/utils/dist/logger.js:79:22 in Logger.prototype.warn
at node_modules/@sentry/react-native/dist/js/integrations/sdkinfo.js:29:20 in __awaiter$argument_3
at node_modules/tslib/tslib.js:113:50 in rejected

Sentry Logger [Warn]:, [SdkInfo] Native SDK Info retrieval failed...something could be wrong with your Sentry installation:
at node_modules/@sentry/utils/dist/logger.js:81:12 in consoleSandbox$argument_0
at node_modules/@sentry/utils/dist/logger.js:34:25 in consoleSandbox
at node_modules/@sentry/utils/dist/logger.js:79:22 in Logger.prototype.warn
at node_modules/@sentry/react-native/dist/js/integrations/sdkinfo.js:28:20 in __awaiter$argument_3
at node_modules/tslib/tslib.js:113:50 in rejected

ajenkins · 2022-04-22T03:10:57Z

I'm seeing the same error. And I don't know if it's related, but I'm not seeing any stack traces in Sentry. I'm also using Expo SDK 44, and can confirm that this is still happening when you follow the directions for installing sentry-expo.

IIsijola · 2022-04-27T02:05:18Z

I am also in the exact same situation as @ajenkins . Can we please get some insight on this issue

grantmagdanz · 2022-04-30T21:59:45Z

We're running into the same issue. Would be great to have some update on this. Currently this is rendering sentry completely useless to us.

grantmagdanz · 2022-05-03T20:39:23Z

We found a solution for us. react-native-get-random-values looks to be a dependency so running yarn add react-native-get-random-values fixed the issue for us.

calboru · 2022-05-04T09:02:46Z

We found a solution for us. react-native-get-random-values looks to be a dependency so running yarn add react-native-get-random-values fixed the issue for us.

Same issue here despite having native-get-random-values package.

ajenkins · 2022-05-23T01:47:36Z

Manually installing react-native-get-random-values does not resolve the issue for me either. This is still happening on Expo 45 and sentry-expo@4.2.0.

Here's what gets logged when I start the app and debug is true:

 LOG  Sentry Logger [Log]: Integration installed: Release
 LOG  Sentry Logger [Log]: Integration installed: InboundFilters
 LOG  Sentry Logger [Log]: Integration installed: FunctionToString
 LOG  Sentry Logger [Log]: Integration installed: Breadcrumbs
 LOG  Sentry Logger [Log]: Integration installed: LinkedErrors
 LOG  Sentry Logger [Log]: Integration installed: Dedupe
 LOG  Sentry Logger [Log]: Integration installed: UserAgent
 LOG  Sentry Logger [Log]: Integration installed: EventOrigin
 LOG  Sentry Logger [Log]: Integration installed: SdkInfo
 LOG  Sentry Logger [Log]: Integration installed: DebugSymbolicator
 LOG  Sentry Logger [Log]: Unhandled promise rejections will be caught by Sentry.
 LOG  Sentry Logger [Log]: Integration installed: ReactNativeErrorHandlers
 LOG  Sentry Logger [Log]: Integration installed: ExpoManagedIntegration
 LOG  Sentry Logger [Log]: Integration installed: RewriteFrames

Then when my app hits an uncaught exception, I see these warnings:

 WARN  Sentry Logger [Warn]: [SdkInfo] Native SDK Info retrieval failed...something could be wrong with your Sentry installation:
 WARN  Sentry Logger [Warn]: [SentryError: Native is disabled]

I'm still not seeing stack traces in Sentry.

hodgln · 2022-05-25T16:31:17Z

Same here using Expo SDK 45

ajenkins · 2022-06-01T13:44:03Z

Not sure if this will help other people, but when I switched from Expo Go to using expo-dev-client these warnings went away for me. Not saying that that's the right fix though. I still think there's an issue here though – I don't think people should have to use expo-dev-client to fix this problem.

Also, the reason I wasn't getting stack traces was actually because I wasn't wrapping my error objects in an Error() constructor before calling captureException().

I had to change my code from this:

Sentry.Native.captureException(error);

to this:

Sentry.Native.captureException(new Error(error));

manuelxaguilar · 2022-06-07T22:44:53Z

Same issue here with:

expo: 45.0.5
sentry-expo: 4.2.0

Any ideas aside from switch from Expo Go to expo-dev-client?

pettomartino · 2022-06-09T11:48:00Z

Same here

"expo": "~45.0.4",
"sentry-expo": "4.2.0"
"@sentry/react-native": "3.4.3",

I've tried with and without @sentry/react-native, different versions. Nothing works.

ragasjohn · 2022-06-10T17:56:15Z

Hello,

same here. Started unexpactably

sarahaoun · 2022-06-13T16:06:41Z

Any update on this?

danielyaa5 · 2022-06-15T23:09:52Z

Same

platramos · 2022-06-23T16:39:38Z

My team and I are experiencing the same issues. Here is our stack trace with the following versions:

@sentry/react-native 4.0.1
sentry-expo 4.0.0 
expo 44.0.0


Sentry Logger [Warn]:, [SdkInfo] Native SDK Info retrieval failed...something could be wrong with your Sentry installation:
Sentry Logger [Warn]:, [SentryError: Native is disabled]

kbrandwijk · 2022-07-17T06:22:23Z

From the reports above, this seems to happen when using an incompatible version of @sentry/react-native in your project. Version 4 is not supported yet (#266), neither is version 2 from another post in this thread. If you use @sentry/react-native@^3.1.1, you should not see this issue.

Closing this as I cannot reproduce this on a new project.

Rutvik17 · 2022-07-18T16:00:17Z

I am still seeing this issue using

"@sentry/react-native": "^3.1.1",
"expo": "~45.0.0",
"sentry-expo": "^4.2.0"

Maybe I need to downgrade sentry-expo ?

chakafasano88 · 2022-07-26T17:41:17Z

I too am receiving these errors:

Sentry Logger [warn]:, [SdkInfo] Native SDK Info retrieval failed...something could be wrong with your Sentry installation:
Sentry Logger [warn]:, [SentryError: Native is disabled]

"expo": "^45.0.0" , 
"sentry-expo": "^4.2.0",
"@sentry/react-native": "^3.1.1",

hooks: {
  postPublish: [
    {
      file: 'sentry-expo/upload-sourcemaps',
      config: {
        organization: 'org',
        project: 'proj',
        authToken: process.env.SENTRY_AUTH_TOKEN,
      },
    },
    {
      file: './src/utils/sentry-post-operations',
    },
  ],
},

Could this be related to my config setup?

helloanil · 2022-08-03T08:22:45Z

I also have this issue although I use @sentry/react-native@^3.1.1.

calebguy · 2022-08-10T02:20:47Z

Also still seeing with updated packages - no sentry event is being triggered:

@sentry/react-native@^4.1.3
expo@^46.0.0
sentry-expo@~5.0.0

kbrandwijk · 2022-08-10T03:23:20Z

If you have a reproducible example, then please open a new issue, and provide the requested information. If I initialize a new project with the correct versions (expo@46, sentry-expo@5.0.2, @sentry/react-native@4.2.2) then it works for me. If it doesn't work for you, we'll need a reproducible example. Commenting on a closed ticket does not help.

CursedMun · 2022-08-16T11:22:49Z

If you have a reproducible example, then please open a new issue, and provide the requested information. If I initialize a new project with the correct versions (expo@46, sentry-expo@5.0.2, @sentry/react-native@4.2.2) then it works for me. If it doesn't work for you, we'll need a reproducible example. Commenting on a closed ticket does not help.

https://github.com/CursedMun/Expo-Test - versions you mentioned still don't work

calebguy · 2022-08-16T13:10:58Z

If you have a reproducible example, then please open a new issue, and provide the requested information. If I initialize a new project with the correct versions (expo@46, sentry-expo@5.0.2, @sentry/react-native@4.2.2) then it works for me. If it doesn't work for you, we'll need a reproducible example. Commenting on a closed ticket does not help.

https://github.com/CursedMun/Expo-Test - versions you mentioned still don't work

are you running in Expo Go @CursedMun? If so - sentry-expo will be disabled regardless

#230 (comment)

gregdburns · 2022-08-31T20:56:40Z

@kbrandwijk I've opened a new ticket with a repro Snack here: #285.

Even with this very basic configuration I can confirm that Expo 46 and the latest sentry-expo version are not writing to Sentry, and are showing the warning discussed in this ticket.

Thanks in advance for any help!

wilfredmulenga · 2022-09-22T10:38:39Z

Experiencing the same issue as many others above on Expo SDK 46. I don't know why this ticket was closed.

nlaffey · 2022-09-22T16:48:26Z

Also experiencing the same issue:

"sentry-expo": "~5.0.0",
"react-native": "0.69.5",
"expo": "^46.0.0",

Grahamcraker · 2022-10-12T20:44:17Z

@BatDroid's solution worked for me as well. Expo 46 and Sentry 4.2.0 doesn't throw the warning and errors are properly received by Sentry.

Si3r4dz · 2022-10-13T08:15:30Z

on expo 46, sentery-expo 4.2.0 it works. though it shouldn't be a compatible version. (normally it installs 5.x for expo 46 which doesn't work and facing this issue)

It also worked for me. Expo 46 and sentry-expo 4.2.0.

BrianLi101 · 2022-10-19T22:19:31Z

I had the exact same errors when running Sentry in the Expo Go app. The errors went away when running it on native devices and simulators. Try using expo run:ios or expo run:android and it should work.

stesvis · 2022-11-14T16:07:06Z

What was the final solution?
I am still getting this in "expo": "^47.0.0" and "sentry-expo": "~5.0.0"

josecarneiro · 2022-11-24T23:46:30Z

Still getting this issue, even with:

"expo": "~47.0.8",
"sentry-expo": "~6.0.0",
"@sentry/react-native": "~4.8.0",

To add to that, I see these warnings when developing app on expo go:

Sentry Logger [warn]: [SdkInfo] Native SDK Info retrieval failed...something could be wrong with your Sentry installation:

as well as

Sentry Logger [warn]: Unable to symbolicate stack trace: newStack.filter is not a function

stesvis · 2022-11-25T02:28:19Z

For now i have to stick to version 4. Seems to be the last one that worked.

rahmanharoon · 2023-01-18T08:36:04Z

any update on this..am facing this issue now

    "expo": "~46.0.16",
    "react-native": "0.69.6",
    "sentry-expo": "~5.0.0",
    "@sentry/react-native": "4.2.2",

Jake-Mulhern · 2023-01-25T17:44:03Z

I am also facing this issue and have tried multiple versions of each package. Currently on this

"expo": "46.0.17",
"sentry-expo": "4.2.0",
"@sentry/react-native": "3.1.1",

stesvis · 2023-01-25T18:46:49Z

I use

"expo": "^47.0.8",
"sentry-expo": "^4.2.0",
"@sentry/react-native": "^3.1.1",

Jake-Mulhern · 2023-01-25T19:57:23Z

@stesvis I tried those versions and they didn't work.

trevorallred · 2023-01-27T21:13:04Z

I'm on and it does not work.

    "expo": "~47.0.12",
    "@sentry/react-native": "4.9.0",
    "sentry-expo": "~6.0.0"

I get the same error everyone else does.

 LOG  Sentry Logger [log]: Unhandled promise rejections will be caught by Sentry.
 LOG  Sentry Logger [log]: Integration installed: ReactNativeErrorHandlers
 LOG  Sentry Logger [log]: Integration installed: Release
 LOG  Sentry Logger [log]: Integration installed: InboundFilters
 LOG  Sentry Logger [log]: Integration installed: FunctionToString
 LOG  Sentry Logger [log]: Integration installed: Breadcrumbs
 LOG  Sentry Logger [log]: Integration installed: LinkedErrors
 LOG  Sentry Logger [log]: Integration installed: Dedupe
 LOG  Sentry Logger [log]: Integration installed: HttpContext
 LOG  Sentry Logger [log]: Integration installed: EventOrigin
 LOG  Sentry Logger [log]: Integration installed: SdkInfo
 LOG  Sentry Logger [log]: Integration installed: DebugSymbolicator
 LOG  Sentry Logger [log]: Integration installed: RewriteFrames
 LOG  Sentry Logger [log]: [ReactNativeTracing] Native frames instrumentation initialized.
 LOG  Sentry Logger [log]: [ReactNativeTracing] Not instrumenting route changes as routingInstrumentation has not been set.
 LOG  Sentry Logger [log]: Integration installed: ReactNativeTracing
 LOG  Sentry Logger [log]: Integration installed: ExpoManagedIntegration
 LOG  Sentry Logger [log]: [TouchEvents] Touch event within element: View
 WARN  Sentry Logger [warn]: [SdkInfo] Native SDK Info retrieval failed...something could be wrong with your Sentry installation:
 WARN  Sentry Logger [warn]: [SentryError: Native is disabled]
 WARN  Sentry Logger [warn]: Event was skipped as native SDK is not enabled.

So I downgraded to:

"expo": "^47.0.8",
"sentry-expo": "^4.2.0",
"@sentry/react-native": "^3.1.1",

And I get this warning at startup.

Some dependencies are incompatible with the installed expo version:
  @sentry/react-native@3.4.3 - expected version: 4.9.0
  sentry-expo@4.2.0 - expected version: ~6.0.0
Your project may not work correctly until you install the correct versions of the packages.
Install individual packages by running npx expo install @sentry/react-native@4.9.0 sentry-expo@~6.0.0

And it still doesn't work of course.

 WARN  Sentry Logger [Warn]: [SdkInfo] Native SDK Info retrieval failed...something could be wrong with your Sentry installation:
 WARN  Sentry Logger [Warn]: [SentryError: Native is disabled]

jonasguerra · 2023-03-16T13:38:26Z

Still facing the same issue

sergioisidoro · 2023-03-16T16:55:18Z

Same here. This issue is closed. Is there any hopes of getting this forward?

bencollinsuk · 2023-03-25T10:27:49Z

I had the exact same errors when running Sentry in the Expo Go app. The errors went away when running it on native devices and simulators. Try using expo run:ios or expo run:android and it should work.

This fixed my problem and my first Sentry issues have been logged :-D

Pous17 · 2023-07-10T09:50:27Z

Still facing the same issue
"expo": "~48.0.18", "@sentry/react-native": "4.15.2", "sentry-expo": "~6.2.0",

stesvis · 2023-07-27T22:43:09Z

I had the exact same errors when running Sentry in the Expo Go app. The errors went away when running it on native devices and simulators. Try using expo run:ios or expo run:android and it should work.

This fixed my problem and my first Sentry issues have been logged :-D

This didn't work for me. I am starting to feel like Sentry abandoned Expo support...

bradydowling · 2023-08-03T15:02:22Z

Bummer to see this. Glad I noticed it at the beginning of my project though so I can try out a different tool!

stesvis · 2023-08-03T15:26:15Z

Bummer to see this. Glad I noticed it at the beginning of my project though so I can try out a different tool!

It started working again, but you have to upgrade to Expo 49 and get the right version of sentry-expo, i believe v7.0

fredrikburmester · 2024-03-03T14:39:42Z

Still facing the same issue in Expo 50 when debug: true.

Curtis-iac · 2024-03-04T01:38:11Z

Still facing the same issue in Expo 50 when debug: true.

Same.
This alongside - Sentry Logger [warn]: [SdkInfo] Native SDK Info retrieval failed...something could be wrong with your Sentry installation:

Any resolution to this ?

z1haze · 2024-03-14T01:42:08Z

2 years later and this issue is still occurring.

miso-belica · 2024-03-14T07:03:22Z

This package is deprecated and Expo 50 now uses native sentry package so it will stay like this probably. Best to migrate when updating Expo to v50+. But currently there are still some issues.

z1haze · 2024-03-14T13:28:14Z

This package is deprecated and Expo 50 now uses native sentry package so it will stay like this probably. Best to migrate when updating Expo to v50+. But currently there are still some issues.

We are on expo 50 and did follow the official docs for sentry with expo. We still have this issue. Is there different documentation to use because it says right in it for sdk 50, for which steps we followed.

miso-belica · 2024-03-14T14:14:31Z

https://docs.sentry.io/platforms/react-native/manual-setup/expo/
https://docs.expo.dev/guides/using-sentry/
https://github.com/expo/fyi/blob/main/sentry-expo-migration.md

Mainly note the experimental notice in Sentry docs 😀

z1haze · 2024-03-14T14:21:12Z

Sure, but you're pointing out that this is deprecated, and the new, supported version doesn't work but its okay because its marked "experimental"... what are folks supposed to do? Is there a different approach to using sentry for RN in expo?

miso-belica · 2024-03-14T15:35:09Z

I guess we are in the process of transition. Old library still works and new one is experimental. I assume the work moved to new one because it makes sense and this one is no longer maintained. It probably does not make sense to expect any bug fixes and new features here.

This is my opinion. I am not connected to expo nor sentry in any way but it makes sense imho.

angelxmoreno · 2024-04-22T21:01:42Z

fixed?
Looks to me like the instructions for the SDK 50 are missing 1 small piece:
enableNativeFramesTracking: Constants.appOwnership !== 'expo', // Only in native builds, not in Expo Go.
specifically when they mention integrating with expo router. They have:

Sentry.init({
  dsn: 'YOUR DSN HERE',
  debug: true, // If `true`, Sentry will try to print out useful debugging information if something goes wrong with sending the event. Set it to `false` in production
  integrations: [
    new Sentry.ReactNativeTracing({
      // Pass instrumentation to be used as `routingInstrumentation`
      routingInstrumentation,
      // ...
    }),
  ],
});

where is should be:

Sentry.init({
  dsn: 'YOUR DSN HERE',
  debug: true, // If `true`, Sentry will try to print out useful debugging information if something goes wrong with sending the event. Set it to `false` in production
  integrations: [
    new Sentry.ReactNativeTracing({
      // Pass instrumentation to be used as `routingInstrumentation`
      routingInstrumentation,
      enableNativeFramesTracking: Constants.appOwnership !== 'expo', // Only in native builds, not in Expo Go.
      // ...
    }),
  ],
});

1 line change and the error is gone for me. I made a PR to update the docs

sebastienlabine · 2024-09-02T18:13:44Z

Our error got fixed after creating a new development build. As you can see Sentry does need a new build for native modules to be bundled up.

Verify the configuration
Create a new release build of your app and verify that it uploads source maps correctly. You may want to add a button in your app to test that it is working and sourcemaps are wired up as expected, for example:

jimmihagenTrifecta mentioned this issue Mar 30, 2022

Promise rejection: SentryError: Native is disabled #218

Closed

kbrandwijk closed this as not planned Won't fix, can't repro, duplicate, stale Jul 17, 2022

This was referenced Oct 28, 2022

Unable to send test event to Sentry from React Native using Expo #294

Closed

Does not work with Expo 46: Native SKD Info retrieval failed #285

Closed

Sentry Logger [Warn]: SentryError: Native is disabled #243

Sentry Logger [Warn]: SentryError: Native is disabled #243

Comments

tigar commented Mar 8, 2022

Summary

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

What platform(s) does this occur on?

SDK Version (managed workflow only)

Environment

Reproducible demo or steps to reproduce from a blank project

lavender16 commented Mar 10, 2022 • edited Loading

tigar commented Mar 10, 2022

jimmihagenTrifecta commented Mar 30, 2022

ajenkins commented Apr 22, 2022

IIsijola commented Apr 27, 2022

grantmagdanz commented Apr 30, 2022

grantmagdanz commented May 3, 2022

calboru commented May 4, 2022

ajenkins commented May 23, 2022

hodgln commented May 25, 2022

ajenkins commented Jun 1, 2022

manuelxaguilar commented Jun 7, 2022

pettomartino commented Jun 9, 2022

ragasjohn commented Jun 10, 2022

sarahaoun commented Jun 13, 2022

danielyaa5 commented Jun 15, 2022

platramos commented Jun 23, 2022 • edited Loading

kbrandwijk commented Jul 17, 2022

Rutvik17 commented Jul 18, 2022

chakafasano88 commented Jul 26, 2022 • edited Loading

helloanil commented Aug 3, 2022

calebguy commented Aug 10, 2022

kbrandwijk commented Aug 10, 2022

CursedMun commented Aug 16, 2022

calebguy commented Aug 16, 2022 • edited Loading

gregdburns commented Aug 31, 2022

wilfredmulenga commented Sep 22, 2022

nlaffey commented Sep 22, 2022

Grahamcraker commented Oct 12, 2022

Si3r4dz commented Oct 13, 2022

BrianLi101 commented Oct 19, 2022 • edited Loading

stesvis commented Nov 14, 2022

josecarneiro commented Nov 24, 2022

stesvis commented Nov 25, 2022

rahmanharoon commented Jan 18, 2023

Jake-Mulhern commented Jan 25, 2023

stesvis commented Jan 25, 2023

Jake-Mulhern commented Jan 25, 2023

trevorallred commented Jan 27, 2023

jonasguerra commented Mar 16, 2023

sergioisidoro commented Mar 16, 2023

bencollinsuk commented Mar 25, 2023 • edited Loading

Pous17 commented Jul 10, 2023

stesvis commented Jul 27, 2023

bradydowling commented Aug 3, 2023

stesvis commented Aug 3, 2023

fredrikburmester commented Mar 3, 2024 • edited Loading

Curtis-iac commented Mar 4, 2024

z1haze commented Mar 14, 2024

miso-belica commented Mar 14, 2024

z1haze commented Mar 14, 2024

miso-belica commented Mar 14, 2024

z1haze commented Mar 14, 2024

miso-belica commented Mar 14, 2024

angelxmoreno commented Apr 22, 2024 • edited Loading

sebastienlabine commented Sep 2, 2024

Managed or bare workflow? If you have `ios/` or `android/` directories in your project, the answer is bare!

lavender16 commented Mar 10, 2022 •

edited

Loading

platramos commented Jun 23, 2022 •

edited

Loading

chakafasano88 commented Jul 26, 2022 •

edited

Loading

calebguy commented Aug 16, 2022 •

edited

Loading

BrianLi101 commented Oct 19, 2022 •

edited

Loading

bencollinsuk commented Mar 25, 2023 •

edited

Loading

fredrikburmester commented Mar 3, 2024 •

edited

Loading

angelxmoreno commented Apr 22, 2024 •

edited

Loading