AdguardTeam / AdguardTeam/ContentBlocker
Compatibility issue with HopToDesk
- 主要言語
- Java
- スター
- 751
- フォーク
- 154
- 平均マージ
- 28分
- マージ済み PR(30日)
- 1
説明
### Prerequisites
Please answer the following questions for yourself before submitting an issue. **YOU MAY DELETE THE PREREQUISITES SECTION.**
- [x ] I am running the latest version
- [x] I checked the documentation and found no answer
- [x ] I checked to make sure that this issue has not already been filed
### Issue Details
- **AdGuard version:**
2.6.2
- **Browser:**
Chrome
- **Device model:**
Google Pixel 7
- **Operating system and version:**
Android 13
### Expected Behavior
Expect to be able to run HopToDesk and allow it to receive incoming connections on Android 13.
### Actual Behavior
While using Adguard, HopToDesk crashes on a new incoming connection.
### Additional Information
An Adguard user with this issue reported that removing HopToDesk from the Adguard routing solved the issue and that we should contact the Adguard team for whitelisting. Further details here:
https://gitlab.com/hoptodesk/hoptodesk/-/issues/43
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
調査の方向性
Start by reproducing the crash on a Google Pixel 7 running Android 13 with AdGuard 2.6.2 and HopToDesk, focusing on a new incoming connection while routing is enabled. Compare the behavior with HopToDesk removed from AdGuard routing; done means incoming connections work without the crash and the compatibility or whitelisting change is verified.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- android, java
- 領域
- mobile
- issue の種類
- バグ
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 30/100