[GH-ISSUE #576] Resolve Sentry Issues #571

New issue

Open

opened 2026-03-03 19:51:23 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 19:51:23 +03:00

Owner

Originally created by @kics223w1 on GitHub (Feb 4, 2026).
Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/576

Originally assigned to: @kics223w1 on GitHub.

Description

We are seeing recurring crashes/exceptions in production. The goal of this task is to investigate, reproduce, and fix the Sentry issues listed below to improve application stability.

🎯 Target Issues

Issue ID	Sentry Link	Status
6735493331	View Issue ↗	🔴 Unresolved
6671732897	View Issue ↗	🔴 Unresolved
https://proxyman.sentry.io/issues/5681870948/?project=6673528&query=is%3Aunresolved&referrer=issue-stream

Acceptance Criteria

Identify the root cause of the exception.
Implement a fix or add necessary null-safety/error handling.
Verify the fix in the staging/development environment.
Mark the issue as Resolved in Sentry once the fix is deployed.

Originally created by @kics223w1 on GitHub (Feb 4, 2026). Original GitHub issue: https://github.com/ProxymanApp/proxyman-windows-linux/issues/576 Originally assigned to: @kics223w1 on GitHub. ## Description We are seeing recurring crashes/exceptions in production. The goal of this task is to investigate, reproduce, and fix the Sentry issues listed below to improve application stability. ## 🎯 Target Issues | Issue ID | Sentry Link | Status | | :--- | :--- | :--- | | **6735493331** | [View Issue ↗](https://proxyman.sentry.io/issues/6735493331/?project=6673528&query=is%3Aunresolved&sort=freq) | 🔴 Unresolved | | **6671732897** | [View Issue ↗](https://proxyman.sentry.io/issues/6671732897/?project=6673528&query=is%3Aunresolved&sort=freq) | 🔴 Unresolved | https://proxyman.sentry.io/issues/5681870948/?project=6673528&query=is%3Aunresolved&referrer=issue-stream ## Acceptance Criteria - [x] Identify the root cause of the exception. - [x] Implement a fix or add necessary null-safety/error handling. - [ ] Verify the fix in the staging/development environment. - [ ] Mark the issue as **Resolved** in Sentry once the fix is deployed.