"dependencies": {
"@nativescript-community/push": "^1.1.9",
"@nativescript-community/sentry": "^2.0.8",
"@nativescript/core": "~7.0.0",
"@nativescript/iqkeyboardmanager": "^2.0.0",
"@nativescript/localize": "^5.0.2",
"@nativescript/theme": "~2.3.0",
"@nota/nativescript-webview-ext": "^7.0.3",
"@nstudio/nativescript-pulltorefresh": "^3.0.1",
"nativescript-lottie": "^5.0.2",
"nativescript-sound-kak": "^1.2.0",
"nativescript-vibrate": "^4.0.1",
"nativescript-vue": "~2.8.0",
"vuex": "^3.6.0"
},
"devDependencies": {
"@babel/core": "~7.1.0",
"@babel/preset-env": "~7.1.0",
"@nativescript/android": "7.0.1",
"@nativescript/ios": "7.0.6",
"@nativescript/webpack": "~3.0.0",
"@sentry/webpack-plugin": "^1.14.0",
"babel-loader": "~8.0.0",
"dotenv": "^8.2.0",
"nativescript-vue-template-compiler": "~2.8.0",
"node-sass": "^4.14.1",
"vue-loader": "~15.9.3"
},
import * as Sentry from '@nativescript-community/sentry';
const dsn = "your Sentry dsn here";
Sentry.setRelease("Your custom release name");
Sentry.setDist("Your custom dist name");
Sentry.init({
dsn,
appPrefix: 'app:///',
});
Then cause the application to crash, and let the plugin catch and report the exception on its own (rather than try/catching it yourself manually).
The exception will get reported to Sentry, but you'll notice that your custom release and dist names were not used.
Which platform(s) does your issue occur on?
Please, provide the following version numbers that your issue occurs with:
Please, tell us how to recreate the issue in as much detail as possible.
Initialize the plugin like so:
Then cause the application to crash, and let the plugin catch and report the exception on its own (rather than try/catching it yourself manually).
The exception will get reported to Sentry, but you'll notice that your custom release and dist names were not used.