nativescript-community / nativescript-community/sentry
Custom release and dist not used for uncaught errors
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 18
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Which platform(s) does your issue occur on?
- Tested on iPhone 11 Xs Max
- iOS 14.3
Please, provide the following version numbers that your issue occurs with:
- CLI: 7.0.12
- Cross-platform modules: 7.0.13
- iOS Runtime: 7.0.6
- Plugin(s):
"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"
},
Please, tell us how to recreate the issue in as much detail as possible.
Initialize the plugin like so:
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Sentry.setRelease, Sentry.setDist, and Sentry.init entry points, then trace the uncaught-exception reporting path on iOS. Reproduce the crash described in the issue and verify that the resulting Sentry event uses the configured custom release and dist values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, typescript
- Domain
- mobile-dev, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100