You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RELEASE_ID is a string representing the “version” of the build you are about to distribute. This can be the SHA of your Git repository’s HEAD. It can also be a semantic version number (e.g. “1.1.2”), pulled from your project’s package.json file. More below.
33
+
RELEASE_ID is a string representing the “version” of the build you are
34
+
about to distribute. This can be the SHA of your Git repository’s HEAD. It
35
+
can also be a semantic version number (e.g. “1.1.2”), pulled from your
36
+
project’s package.json file. More below.
34
37
35
38
About Releases
36
39
--------------
37
40
38
-
Every time you build and distribute a new version of your React Native app, you’ll want to create a new release inside Sentry. This is for two important reasons:
41
+
Every time you build and distribute a new version of your React Native
42
+
app, you’ll want to create a new release inside Sentry. This is for two
43
+
important reasons:
39
44
40
45
- You can associate errors tracked by Sentry with a particular build
41
46
- You can store your source maps generated for each build inside Sentry
42
47
43
-
Unlike a normal web application where your JavaScript files (and source maps) are served and hosted from a web server, your React Native code is being served from the target device’s filesystem. So you’ll need to upload both your **source code** AND **source maps** directly to Sentry, so that we can generate handy stack traces for you to browse when examining exceptions trigged by your application.
48
+
Unlike a normal web application where your JavaScript files (and source
49
+
maps) are served and hosted from a web server, your React Native code is
50
+
being served from the target device’s filesystem. So you’ll need to upload
51
+
both your **source code** AND **source maps** directly to Sentry, so that
52
+
we can generate handy stack traces for you to browse when examining
53
+
exceptions trigged by your application.
44
54
45
55
46
56
Generating source maps
@@ -62,9 +72,8 @@ Then, in another tab, curl the packager service for your source map:
62
72
63
73
This will write a file index.ios.map to the current directory.
64
74
65
-
Lastly, you'll need to `create a new release and upload your source code files and source maps as release artifacts`_.
66
-
67
-
.. _create a new release and upload your source map as a release artifact: https://docs.getsentry.com/hosted/clients/javascript/sourcemaps/#uploading-source-maps-to-sentry
75
+
Lastly, you'll need to `create a new release and upload your source code files and source maps as release artifact
0 commit comments