AdguardTeam / AdguardTeam/ContentBlocker
Compatibility issue with HopToDesk
- Linguagem predominante
- Java
- Estrelas
- 751
- Forks
- 154
- Merge médio
- 28min
- PRs com merge (30d)
- 1
Descrição
### 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
Guia de contribuição
Nenhum guia de contribuição indexado para este repositório
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- android, java
- Domínio
- mobile
- Tipo de issue
- Bug
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Estagnada
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 30/100