net6.0-windows net6.0-windows was computed. net6.0-maccatalyst net6.0-maccatalyst was computed. net6.0-android net6.0-android was computed. net5.0-windows net5.0-windows was computed. If you're using an older version of the SDK (version 3.2.12 or lower) or sentry-cli (version 1.71.Versions Compatible and additional computed target framework versions. An easy way to do this is to include the platform name in the dist value. To associate the correct bundle and sourcemap to each platform, you will need a unique release/dist combination for each platform. Your app could have different bundles for each platform that it supports, such as iOS and Android. Different Bundles for Different Platforms Source Maps With HermesĪlthough the build script should already handle this for you most of the time, you may need to perform some extra steps when using the source maps with the Hermes engine. Checking that you're not disabling the RewriteFrames default integration by overwriting it, filtering it out, or setting defaultIntegrations: false.įor more details, please read the guide on React Native source maps.For example, if your stack frames say app:///index.bundle, the artifacts must be named index.bundle and respectively. Make sure that the name of the bundle in the stack trace matches exactly with the name in the source map.If you set a custom release and dist, confirming that you manually uploaded the sourcemaps since our automatic source map upload script will not detect the custom values.They must match for source maps to upload correctly. Checking that source maps are correctly uploaded with the exact same release and dist values as the event.Checking that both the release and dist and are set on the event by setting it in the call to init.There was 1 problem processing this event: Source code was not found When there is an issue with source maps on your event, there will usually be an error dialog at the top of the Issue Details page in sentry.io : If the fix is successful, our SDK will no longer display the above warning and will indicate that promise rejections will be caught.If you use npm, you can use a third-party package called npm-force-resolutions to achieve this. Package resolutions are currently only supporred by yarn. You can do this by going into node_modules/react-native/package.json and checking the version there, for example we find that it uses ^8.0.3: Check the version of promise that your version of react-native uses.You'll need to ensure that the version of promise that you use matches exactly with the version that React Native uses. You don't need to perform the steps below if you don't disable auto patching. Note that if you disable our auto patching, to ensure that unhandled rejections are still caught, you will need to manually force a package resolution. You can disable the global promise patching by passing patchGlobalPromise: false in either Sentry.init or the ReactNativeErrorHandlers integration. Your linter might throw some errors here, but this step is necessary. shim ( ) // Separate core-js example import "core-js/stable/promise/all-settled" init ( ) // Any Promise polyfilling must occur AFTER Sentry.init // This step globally patches Promise.ĪllSettled. Import allSettled from "promise.allsettled" If you use a polyfilling library that patches the global Promise instance, you'll need to make sure you run the polyfill after Sentry.init is called. Auto Patching (Default Behavior)īy default we will patch the global Promise instance to ensure it matches exactly with the version that React Native uses. Unhandled promise rejections will be caught by Sentry. Otherwise, we will let you know that the handler is attached: Read about how to fix this on our troubleshooting docs. WARN: Unhandled promise rejections might not be caught by Sentry. If the promise rejection handler was not correctly attached, our SDK might issue a warning: Unhandled Promise Rejectionsĭue to an issue with React Native's dependencies, unhandled promise rejections might not be correctly caught by Sentry. Please update to this version or a later one.įor more details, see the troubleshooting page for the iOS SDK. This issue was fixed in version 4.1.1 of the SDK. IOS 15 introduced a feature called pre-warm that affected the calculations the Sentry SDK does. App Start Numbers Are Too High To Be Accurate
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |