Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Exceptions must be explicitly caught and reported for source mapping to work

未关闭
#2 0 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
ios, typescript

调研方向

首先,跟踪插件在 iOS 上的自动异常处理,并将其与报告中描述的手动 Sentry.captureException(error) 路径进行比较。验证未捕获的崩溃生成的是经过源映射的 JavaScript 帧,而不是纯文本堆栈,并且其行为与手动报告的异常一致。

由索引模型根据 Issue 内容生成。

描述

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.init({
  dsn, 
  appPrefix: "app:///",
  release: "Your custom release name",
  dist: "Your custom dist name",
});

Then cause the application to crash, and let the plugin catch and report the exception on its own (rather than try/catching and manually reporting it using Sentry.captureException(error)).

The exception will get reported to Sentry, but the JS stack trace will appear as a plain text string and source mapping will not occur. If instead you manually catch and report the exception source mapping will work. Presumably, stack trace frame rewriting only occurs when exceptions are manually caught and reported. This is problematic because you don't know in advance where exceptions will occur, and wrapping all code in try/catch blocks is unfeasible.

主要语言
TypeScript
星标
18
派生
12
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

nativescript-community/sentry 的其他 Issue

查看 nativescript-community/sentry 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。