Skip to content
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

Third party frames are not symbolicated #3546

Closed
6 of 10 tasks
pax-k opened this issue Jan 23, 2024 · 24 comments
Closed
6 of 10 tasks

Third party frames are not symbolicated #3546

pax-k opened this issue Jan 23, 2024 · 24 comments
Labels
Expo Issues related to Sentry React Native Expo support Platform: React-Native

Comments

@pax-k
Copy link

pax-k commented Jan 23, 2024

OS:

  • Windows
  • MacOS
  • Linux

Platform:

  • iOS
  • Android

SDK:

  • "@sentry/react-native": "5.16.0"

SDK version: 5.16.0

react-native version: 0.73.2

Are you using Expo?

  • Yes
  • No

Are you using sentry.io or on-premise?

  • sentry.io (SaaS)
  • on-premise

If you are using sentry.io, please post a link to your issue so we can take a look:

[Link to issue]

Configuration:

(@sentry/react-native)

Sentry.init({
  enabled: ENV.APP_VARIANT !== 'development',
  dsn: ENV.SENTRY_DSN,
  debug: false,
  attachStacktrace: true,
  enableAutoSessionTracking: true,
  attachViewHierarchy: true,
  environment: ENV.APP_VARIANT,
  tracesSampleRate: 1.0,
  enableNdkScopeSync: true,
  _experiments: {
    profilesSampleRate: 1.0,
  },
  enableAppHangTracking: true,
  appHangTimeoutInterval: 5,
  enableAutoPerformanceTracing: true,
  enableTracing: true,
  enableCaptureFailedRequests: true,
  enableWatchdogTerminationTracking: true,
  sessionTrackingIntervalMillis: 10000,
  integrations: [new CaptureConsole({ levels: ['warn', 'error'] }), new HttpClient()],
  beforeBreadcrumb: (breadcrumb) => {
    if (
      ENV.APP_VARIANT === 'production' &&
      breadcrumb.category === 'console' &&
      breadcrumb.level === 'debug'
    ) {
      return null;
    }
    return breadcrumb;
  },
});

(app.config.js)

export default {
  expo: {
    name: getVariantConfigs()[APP_VARIANT].name,
    slug: 'xxx',
    owner: 'zzz',
    version: '0.1.7',
    orientation: 'portrait',
    icon: './assets/icon.png',
    userInterfaceStyle: 'light',
    scheme: 'xxx',
    jsEngine: 'hermes',
    sdkVersion: '50.0.0',
    splash: {
      image: './assets/splash.png',
      resizeMode: 'contain',
      backgroundColor: '#ffffff',
    },
    assetBundlePatterns: ['**/*'],
    ios: {
      supportsTablet: true,
      infoPlist: {
        NSFaceIDUsageDescription: 'Authentication with TouchId or FaceID',
      },
      bundleIdentifier: getVariantConfigs()[APP_VARIANT].ios.bundleIdentifier,
      buildNumber: '145',
    },
    android: {
      package: getVariantConfigs()[APP_VARIANT].android.package,
      adaptiveIcon: {
        foregroundImage: './assets/adaptive-icon.png',
        backgroundColor: '#FFFFFF',
      },
      versionCode: 145,
    },
    web: {
      favicon: './assets/favicon.png',
    },
    plugins: [
      'expo-updates',
      'expo-secure-store',
      [
        '@sentry/react-native/expo',
        {
          project: 'xxx',
          organization: 'yyy',
        },
      ],
    ],
    hooks: {},
    ...
  }

(`metro.config.js)

const { getSentryExpoConfig } = require('@sentry/react-native/metro');
const {
  createSentryMetroSerializer,
} = require('@sentry/react-native/dist/js/tools/sentryMetroSerializer');
const { mergeConfig } = require('metro-config');
const customConfig = require('./metro-custom.config.js');

const config = getSentryExpoConfig(__dirname);

const { resolver } = config;

config.resolver = {
  ...resolver,
  sourceExts: [...resolver.sourceExts, 'cjs', 'mjs'],
  serializer: {
    customSerializer: createSentryMetroSerializer(),
  },
};

module.exports = mergeConfig(config, customConfig);

I have the following issue:

  • I expect to see the source code of an error in Sentry (based on uploaded sourcemaps)

Steps to reproduce:
a) Run EAS Build => it should upload sourcemaps automatically. EAS Build XCode logs:

+ BUNDLE_FILE=/Users/expo/Library/Developer/Xcode/DerivedData/PrevFeatKin-aimsbvhikjjxnbexkicuzygwdefv/Build/Intermediates.noindex/ArchiveIntermediates/PrevFeatKin/BuildProductsPath/Release-iphoneos/PrevFeatKin.app/main.jsbundle
+ [[ false != true ]]
+ [[ ! -f /Users/expo/Library/Developer/Xcode/DerivedData/PrevFeatKin-aimsbvhikjjxnbexkicuzygwdefv/Build/Intermediates.noindex/ArchiveIntermediates/PrevFeatKin/BuildProductsPath/Release-iphoneos/PrevFeatKin.app/main.jsbundle ]]
Using Hermes bundle and combined source map.
Processing react-native sourcemaps for Sentry upload.
> Analyzing 2 sources
> Rewriting sources
> Adding source map references
> Bundled 2 files for upload
> Bundle ID: 40de2ff6-40ed-56a4-a641-311a063a1ee5
> Uploaded files to Sentry
> File upload complete (processing pending on server)
> Organization: xxx
> Project: zzz
> Release: None
> Dist: None
> Upload type: artifact bundle

Source Map Upload Report
  Minified Scripts
    ~/main.jsbundle (sourcemap at main.jsbundle.map, debug id 8426621a-1d1d-4ae8-a24f-1fd9763d933c)
  Source Maps
    ~/main.jsbundle.map (debug id 8426621a-1d1d-4ae8-a24f-1fd9763d933c)
+ '[' -z '' ']'
++ /Users/expo/.nvm/versions/node/v18.16.0/bin/node --print 'require('\''path'\'').dirname(require.resolve('\''@sentry/react-native/package.json'\''))'
+ SENTRY_RN_PACKAGE_PATH=/Users/expo/workingdir/build/node_modules/@sentry/react-native
+ '[' -z '' ']'
+ SENTRY_COLLECT_MODULES=/Users/expo/workingdir/build/node_modules/@sentry/react-native/scripts/collect-modules.sh
+ '[' -f /Users/expo/workingdir/build/node_modules/@sentry/react-native/scripts/collect-modules.sh ']'
+ /bin/sh /Users/expo/workingdir/build/node_modules/@sentry/react-native/scripts/collect-modules.sh
+ [[ Release = *Debug* ]]
+ [[ -z /Users/expo/Library/Developer/Xcode/DerivedData/PrevFeatKin-aimsbvhikjjxnbexkicuzygwdefv/Build/Intermediates.noindex/ArchiveIntermediates/PrevFeatKin/BuildProductsPath/Release-iphoneos ]]
+ [[ -z PrevFeatKin.app ]]
+ [[ -z /Users/expo/Library/Developer/Xcode/DerivedData/PrevFeatKin-aimsbvhikjjxnbexkicuzygwdefv/Build/Intermediates.noindex/ArchiveIntermediates/PrevFeatKin/IntermediateBuildFilesPath/PrevFeatKin.build/Release-iphoneos/PrevFeatKin.build/DerivedSources ]]
+ nodePath=node
+ [[ -n /Users/expo/.nvm/versions/node/v18.16.0/bin/node ]]
+ nodePath=/Users/expo/.nvm/versions/node/v18.16.0/bin/node
++ dirname /Users/expo/workingdir/build/node_modules/@sentry/react-native/scripts/collect-modules.sh
+ thisFilePath=/Users/expo/workingdir/build/node_modules/@sentry/react-native/scripts
+ collectModulesScript=/Users/expo/workingdir/build/node_modules/@sentry/react-native/scripts/../dist/js/tools/collectModules.js
+ destination=/Users/expo/Library/Developer/Xcode/DerivedData/PrevFeatKin-aimsbvhikjjxnbexkicuzygwdefv/Build/Intermediates.noindex/ArchiveIntermediates/PrevFeatKin/BuildProductsPath/Release-iphoneos/PrevFeatKin.app
+ modulesOutput=/Users/expo/Library/Developer/Xcode/DerivedData/PrevFeatKin-aimsbvhikjjxnbexkicuzygwdefv/Build/Intermediates.noindex/ArchiveIntermediates/PrevFeatKin/BuildProductsPath/Release-iphoneos/PrevFeatKin.app/modules.json
+ [[ -z '' ]]
+ sourceMap=/Users/expo/Library/Developer/Xcode/DerivedData/PrevFeatKin-aimsbvhikjjxnbexkicuzygwdefv/Build/Intermediates.noindex/ArchiveIntermediates/PrevFeatKin/IntermediateBuildFilesPath/PrevFeatKin.build/Release-iphoneos/PrevFeatKin.build/DerivedSources/main.jsbundle.map
+ [[ -z '' ]]
+ modulesPaths=/Users/expo/workingdir/build/ios/../node_modules
+ type /Users/expo/.nvm/versions/node/v18.16.0/bin/node
+ /Users/expo/.nvm/versions/node/v18.16.0/bin/node /Users/expo/workingdir/build/node_modules/@sentry/react-native/scripts/../dist/js/tools/collectModules.js /Users/expo/Library/Developer/Xcode/DerivedData/PrevFeatKin-aimsbvhikjjxnbexkicuzygwdefv/Build/Intermediates.noindex/ArchiveIntermediates/PrevFeatKin/IntermediateBuildFilesPath/PrevFeatKin.build/Release-iphoneos/PrevFeatKin.build/DerivedSources/main.jsbundle.map /Users/expo/Library/Developer/Xcode/DerivedData/PrevFeatKin-aimsbvhikjjxnbexkicuzygwdefv/Build/Intermediates.noindex/ArchiveIntermediates/PrevFeatKin/BuildProductsPath/Release-iphoneos/PrevFeatKin.app/modules.json /Users/expo/workingdir/build/ios/../node_modules
Sentry Logger [info]: Reading source map from /Users/expo/Library/Developer/Xcode/DerivedData/PrevFeatKin-aimsbvhikjjxnbexkicuzygwdefv/Build/Intermediates.noindex/ArchiveIntermediates/PrevFeatKin/IntermediateBuildFilesPath/PrevFeatKin.build/Release-iphoneos/PrevFeatKin.build/DerivedSources/main.jsbundle.map
Sentry Logger [info]: Saving modules to /Users/expo/Library/Developer/Xcode/DerivedData/PrevFeatKin-aimsbvhikjjxnbexkicuzygwdefv/Build/Intermediates.noindex/ArchiveIntermediates/PrevFeatKin/BuildProductsPath/Release-iphoneos/PrevFeatKin.app/modules.json
Sentry Logger [info]: Resolving modules from paths /Users/expo/workingdir/build/ios/../node_modules
Sentry Logger [info]: Modules collected and saved to: /Users/expo/Library/Developer/Xcode/DerivedData/PrevFeatKin-aimsbvhikjjxnbexkicuzygwdefv/Build/Intermediates.noindex/ArchiveIntermediates/PrevFeatKin/BuildProductsPath/Release-iphoneos/PrevFeatKin.app/modules.json

b) OR manual upload:

npx expo export
npx sentry-expo-upload-sourcemaps dist

logs:

🐕 Fetching SENTRY_PROJECT from expo config...
SENTRY_PROJECT resolved to kin-mobile from expo config.
⬆️ Uploading dist/_expo/static/js/android/index-1d0e26178998181e88bb42e95947390a.hbc bundle and sourcemap...
> Found 1 file
> Analyzing 1 sources
> Analyzing completed in 0.781s
> Rewriting sources
> Rewriting completed in 0s
> Adding source map references
> Bundling completed in 0.001s
> Bundled 1 file for upload
> Bundle ID: 123a1a0a-4f62-50b8-98eb-8a5c852fb8a4
> Optimizing completed in 0.001s
> Uploading completed in 0.236s
> Uploaded files to Sentry
> Processing completed in 0.243s
> File upload complete (processing pending on server)
> Organization: xxx
> Project: zzz
> Release: None
> Dist: None
> Upload type: artifact bundle

Source Map Upload Report
  Minified Scripts
    ~/index-1d0e26178998181e88bb42e95947390a.hbc (no sourcemap ref)
      - warning: could not determine a source map reference (Could not auto-detect referenced sourcemap for ~/index-1d0e26178998181e88bb42e95947390a.hbc)
⬆️ Uploading dist/_expo/static/js/ios/index-6d01582c3b9b7fa2a5803a5431f9fecd.hbc bundle and sourcemap...
> Found 1 file
> Analyzing 1 sources
> Analyzing completed in 0.779s
> Rewriting sources
> Rewriting completed in 0s
> Adding source map references
> Bundling completed in 0.002s
> Bundled 1 file for upload
> Bundle ID: 5cd92359-70a3-5e29-8917-25b3696199a7
> Optimizing completed in 0s
> Uploading completed in 0.208s
> Uploaded files to Sentry
> Processing completed in 0.272s
> File upload complete (processing pending on server)
> Organization: xxx
> Project: zzz
> Release: None
> Dist: None
> Upload type: artifact bundle

Source Map Upload Report
  Minified Scripts
    ~/index-6d01582c3b9b7fa2a5803a5431f9fecd.hbc (no sourcemap ref)
      - warning: could not determine a source map reference (Could not auto-detect referenced sourcemap for ~/index-6d01582c3b9b7fa2a5803a5431f9fecd.hbc)
✅ Uploaded bundles and sourcemaps to Sentry successfully.

Contents of dist/:

❯ tree dist
dist
├── _expo
│   └── static
│       └── js
│           ├── android
│           │   └── index-1d0e26178998181e88bb42e95947390a.hbc
│           └── ios
│               └── index-6d01582c3b9b7fa2a5803a5431f9fecd.hbc
├── assets
│   ├── 026491af08d90496accb275e49e4c63e
│   ├── 02bc1fa7c0313217bde2d65ccbff40c9
│   ├── 0ea69b5077e7c4696db85dbcba75b0e1
│   ├── 35ba0eaec5a4f5ed12ca16fabeae451d
│   ├── 376d6a4c7f622917c39feb23671ef71d
│   ├── 5223c8d9b0d08b82a5670fb5f71faf78
│   ├── 629a55a7e793da068dc580d184cc0e31
│   ├── 6ee4be30a6bb3c31bc333d88da8cdbb5
│   ├── 778ffc9fe8773a878e9c30a6304784de
│   ├── 7d40544b395c5949f4646f5e150fe020
│   ├── 95d6a6037f694266d9b31763e5d6f099
│   ├── a132ecc4ba5c1517ff83c0fb321bc7fc
│   ├── c79c3606a1cf168006ad3979763c7e0c
│   ├── cdd04e13d4ec83ff0cd13ec8dabdc341
│   ├── e4fe68503ab5d004deb31e43636a0a7c
│   └── f5b790e2ac193b3d41015edb3551f9b8
└── metadata.json

Actual result:

I cannot see the source code which triggered an error

Expected result:

I expect to see the source code which triggered an error

Screenshot 2024-01-23 at 15 38 08
@krystofwoldrich
Copy link
Member

krystofwoldrich commented Jan 23, 2024

Hi @pax-k,
thank you for the message, the logs, and the links.

I see a small issue in the metro.config.js, the sentryMetroSerializer is designed for bare React Native configurations, I removed it from your example.

const { getSentryExpoConfig } = require('@sentry/react-native/metro');
const { mergeConfig } = require('metro-config');
const customConfig = require('./metro-custom.config.js');

const config = getSentryExpoConfig(__dirname);

const { resolver } = config;

config.resolver = {
  ...resolver,
  sourceExts: [...resolver.sourceExts, 'cjs', 'mjs'],
};

module.exports = mergeConfig(config, customConfig);

Could you share what is in metro-custom.config.js, from what I can see the source maps only resolve node_modules, but your application code is missing.

For the Expo Updates (expo export), the command needs to emit the source maps:

npx expo export --dump-sourcemaps
npx sentry-expo-upload-sourcemaps dist

Are you using continuous code generation or do you maintain the native project your self? (If the latter can you share your Bundle React Native and Images build phase?)

Let us know if this helps.

@krystofwoldrich krystofwoldrich moved this from Needs Discussion to Needs More Information in Mobile & Cross Platform SDK Jan 23, 2024
@getsantry getsantry bot moved this to Waiting for: Community in GitHub Issues with 👀 2 Jan 23, 2024
@pax-k
Copy link
Author

pax-k commented Jan 23, 2024

Hey @krystofwoldrich ,

Could you share what is in metro-custom.config.js, from what I can see the source maps only resolve node_modules, but your application code is missing.

Sure, this is it:

const currentDir = process.cwd();

const config = {
  resolver: {
    sourceExts: ['ts', 'tsx', 'js', 'jsx', 'json', 'cjs', 'mjs'],
    resolveRequest: (context, moduleName, platform) => {
      // provide the omitted entrypoints
      if (moduleName === 'jsonrepair') {
        return {
          filePath: `${currentDir}/node_modules/jsonrepair/lib/esm/index.js`,
          type: 'sourceFile',
        };
      }

      // fallback to the default resolver
      return context.resolveRequest(context, moduleName, platform);
    },
  },
};

module.exports = config;

For the Expo Updates (expo export), the command needs to emit the source maps

Thanks! Actually I would never export the project manually if not necessary; I provided the manual step for brevity. But if necessary, I will implement it in our CI/CD.

Are you using continuous code generation or do you maintain the native project your self? (If the latter can you share your Bundle React Native and Images build phase?)

I'm not using continuous code generation (or I don't think I'm doing it). The project is prebuilt/ejected (i have /ios and /android) and only maintain my native expo modules by upgrading their NPM deps by hand.

share your Bundle React Native and Images build phase

Can you please instruct me what do you mean exactly? I'm happy to provide anything useful.

Thanks!

@getsantry getsantry bot moved this from Waiting for: Community to Waiting for: Product Owner in GitHub Issues with 👀 2 Jan 23, 2024
@krystofwoldrich krystofwoldrich changed the title Expo 50: source maps seem to be uploaded, but still not usable in Sentry Expo: source maps seem to be uploaded, but still not usable in Sentry Jan 23, 2024
@krystofwoldrich krystofwoldrich added the Expo Issues related to Sentry React Native Expo support label Jan 23, 2024
@mrljsh
Copy link

mrljsh commented Jan 26, 2024

npx expo export --dump-sourcemaps
npx sentry-expo-upload-sourcemaps dist

Hey @krystofwoldrich, I have same issue with source maps, and I've been trying to run npx sentry-expo-upload-sourcemaps dist, but I constantly get SENTRY_AUTH_TOKEN environment variable must be set. error. I do have SENTRY_AUTH_TOKEN set in .env, and expo prebuild script sees that variable normally, but for some reason this package doesn't see it.

@macksal
Copy link

macksal commented Jan 27, 2024

@krystofwoldrich @mrljsh how are you using the sentry-expo-upload-sourcemaps command? For me, trying to run it with npx just gives a 404, it isn't on the NPM registry and I can't find specific documentation anywhere.

Sentry's React Native docs and the Expo docs both imply that it can be run with npx sentry-expo-upload-sourcemaps but don't mention it any further. What is this command?

@mrljsh
Copy link

mrljsh commented Jan 27, 2024

For me, npx command works but pnpx command returns 404 error.

@macksal
Copy link

macksal commented Jan 27, 2024

Worked it out. It's a package.json bin registered by @sentry/react-native. For some reason, npx wasn't finding it for me. (does expo install not register binaries?).

Seems to be working after yarn installing again. It's now running OK with yarn sentry-expo-upload-sourcemaps dist. Forgive my off-topic

@JuanRdBO
Copy link

I also have the same error that @pax-k has. I think the issue here is that the release and dist variables are not set.

How can I set them? In both examples he has

> Release: None
> Dist: None

@krystofwoldrich
Copy link
Member

Hey @krystofwoldrich, I have same issue with source maps, and I've been trying to run npx sentry-expo-upload-sourcemaps dist, but I constantly get SENTRY_AUTH_TOKEN environment variable must be set. error. I do have SENTRY_AUTH_TOKEN set in .env, and expo prebuild script sees that variable normally, but for some reason this package doesn't see it.

@mrljsh Hi, thank you for the message, the script currently doesn't read .env files, but it's a valid feature, would you mind opening a separate issue for it?

@getsantry getsantry bot moved this from Waiting for: Community to Waiting for: Product Owner in GitHub Issues with 👀 2 Feb 5, 2024
@pax-k
Copy link
Author

pax-k commented Feb 6, 2024

@krystofwoldrich

here is the build phase script:

if [[ -f "$PODS_ROOT/../.xcode.env" ]]; then
  source "$PODS_ROOT/../.xcode.env"
fi
if [[ -f "$PODS_ROOT/../.xcode.env.local" ]]; then
  source "$PODS_ROOT/../.xcode.env.local"
fi

# The project root by default is one level up from the ios directory
export PROJECT_ROOT="$PROJECT_DIR"/..

if [[ "$CONFIGURATION" = *Debug* ]]; then
  export SKIP_BUNDLING=1
fi
if [[ -z "$ENTRY_FILE" ]]; then
  # Set the entry JS file using the bundler's entry resolution.
  export ENTRY_FILE="$("$NODE_BINARY" -e "require('expo/scripts/resolveAppEntry')" "$PROJECT_ROOT" ios relative | tail -n 1)"
fi

if [[ -z "$CLI_PATH" ]]; then
  # Use Expo CLI
  export CLI_PATH="$("$NODE_BINARY" --print "require.resolve('@expo/cli', { paths: [require.resolve('expo/package.json')] })")"
fi
if [[ -z "$BUNDLE_COMMAND" ]]; then
  # Default Expo CLI command for bundling
  export BUNDLE_COMMAND="export:embed"
fi

# Source .xcode.env.updates if it exists to allow
# SKIP_BUNDLING to be unset if needed
if [[ -f "$PODS_ROOT/../.xcode.env.updates" ]]; then
  source "$PODS_ROOT/../.xcode.env.updates"
fi
# Source local changes to allow overrides
# if needed
if [[ -f "$PODS_ROOT/../.xcode.env.local" ]]; then
  source "$PODS_ROOT/../.xcode.env.local"
fi

/bin/sh `"$NODE_BINARY" --print "require('path').dirname(require.resolve('@sentry/react-native/package.json')) + '/scripts/sentry-xcode.sh'"` `"$NODE_BINARY" --print "require('path').dirname(require.resolve('react-native/package.json')) + '/scripts/react-native-xcode.sh'"`

Seems like this script sources the NODE_BINARY var from .xcode.env.local. Worth noting that I have to delete this file each time it reappears, because it sets NODE_BINARY to some path that doesn't exist, causing the build to fail. This started happening once I upgraded to Expo 50 and started using the new Expo + Sentry integration (but I don't know which one of these two is the cause).

@krystofwoldrich
Copy link
Member

@pax-k The build phase looks correct, also your original log from the build showed the source maps uploaded correctly.

When you build the app could you bump the application version to something you haven't yet used so we can rule out that there is a collision of already uploaded source maps and the newly created ones?

@pax-k
Copy link
Author

pax-k commented Feb 22, 2024

@krystofwoldrich we bump the app's version automatically, so it's safe to rule this out.

Actually the problem is this:

  • source maps of our expo app are uploaded and can be seen in Sentry
  • but source maps of our node_modules are ignored by Sentry. This is what we're interested in.

Our 3rd party dependency we're interested in has it's own .map file. Also the .map produced by yarn expo export -s contains this 3rd party .map. But for some reason, Sentry fails to process it.

Tried adding this to metro.config.js:

config.transformer = {
  ...config.transformer,
  minifierConfig: {
    ...config.transformer.minifierConfig,
    sourceMap: {
      includeSources: true,
    },
  },
};

config.serializer = {
  ...config.serializer,
  isThirdPartyModule: (module) => {
    if (module.path.includes('node_modules/our-dep/dist/main.mjs')) {
      return false;
    }
    return true;
  },
};

But seems it doesn't affect the generated .map anyway

@getsantry getsantry bot moved this from Waiting for: Community to Waiting for: Product Owner in GitHub Issues with 👀 2 Feb 22, 2024
@krystofwoldrich
Copy link
Member

@pax-k Thank you for the message.

To avoid misunderstanding, do I understand correctly that only the third-party frames are not symbolicated, but application frames are? Is that the current issue?

When you try to symbolicate the minified stack trace manual using metro-symbolicate and the created source map are the third-party frames symbolicated?

https://reactnative.dev/docs/debugging-release-builds#using-metro-symbolicate

@getsantry getsantry bot moved this to Waiting for: Community in GitHub Issues with 👀 2 Feb 23, 2024
@krystofwoldrich krystofwoldrich changed the title Expo: source maps seem to be uploaded, but still not usable in Sentry Third party frames are not symbolicated Mar 8, 2024
@krystofwoldrich
Copy link
Member

Closing this due to inactivity. If this is still an issue feel free to comment here or open a new issue if the context changed.

@krystofwoldrich krystofwoldrich closed this as not planned Won't fix, can't repro, duplicate, stale Mar 15, 2024
@github-project-automation github-project-automation bot moved this from Needs More Information to Done in Mobile & Cross Platform SDK Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Expo Issues related to Sentry React Native Expo support Platform: React-Native
Projects
Archived in project
Archived in project
Development

No branches or pull requests

7 participants