getsentry / getsentry/sentry-java
Pure tombstone events duplication
- 主要语言
- Kotlin
- 星标
- 1.4k
- 派生
- 478
- 平均合并
- 2 天 22 小时
- 30 天内合并 PR
- 69
描述
### Integration
sentry-android
### Build System
Gradle
### AGP Version
8.14.0
### Proguard
Enabled
### Other Error Monitoring Solution
No
### Version
8.44.1
### Steps to Reproduce
Unfortunately, I was unable to reproduce this problem on local devices.
### Expected Result
Tombstone events are not duplicated.
### Actual Result
I see duplicate events in the reports received from users:
I downloaded two event's jsons and compared:
```
E:\work\tmp>diff "l.txt" "r.txt"
2c2
< "event_id": "b4a16e59fd854caaa8ebae2ea2828dd0",
---
> "event_id": "5716230e7f254ec9b3bcfe13d562bde2",
6893,6894c6893,6894
< "nodestore_insert": 1788397282.7622,
< "received": 1788397276.54076,
---
> "nodestore_insert": 1788358349.59206,
> "received": 1788358346.52165,
```
All content is identical, except from id and received time.
Therefore, I assume there is a bug when same tombstone may be reported twice.
P.S. Ignore the fact that the "Release" field is missing from the events - that's another issue I started to address, but noticed duplicates. For some reason, pure tombstone events don't have custom tags, breadcrumbs and attachment. If someone knows the reason, please advice, any hints are highly appreciated.
贡献指南
调研方向
Start with the sentry-android tombstone reporting path and compare the two supplied event JSONs, focusing on why identical content is received twice. Reproduce the reported Android and Gradle setup if possible; done means a single tombstone produces one event, with the duplicate-event behavior covered by an appropriate test.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- android, java, kotlin
- 领域
- mobile-dev
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 活跃
- 描述清晰度
- 需要澄清
- 新手友好度
- 38/100