guardianproject / guardianproject/orbot-android

[BUG] Broken Functionality policy: Violation of Broken Functionality policy

Open
#1,412 2 comments 0 reactions 0 assignees View on GitHub
Bug
Dominant language
Kotlin
Stars
3.5k
Forks
485
Avg merge
2d 14h
Merged PRs (30d)
24

Description

**Describe the Bug**
Broken Functionality policy: Violation of Broken Functionality policy

Status
Fix to prevent your app from being removed (overdue)
Date sent 11 Aug 2025
Deadline 25 Aug 2025
Your app has the following functionality issue(s):
App contains icon(s) or button(s) that are not responsive or do not return content.

**To Reproduce**

Reported by Google Play

**Expected Behavior**
It loads!

**What Custom Configuration Do You Use?**
None

**Screenshots**

screenshots from Google Play

Image

**Smartphone (please complete the following information):**
App bundles with this issue are listed here. Some app bundles in the list may be from an older version of your app.
1750300201 (17.5.0-RC-2-tor-0.4.8.17)
17.5.0-RC-2 tor-0.4.8.17 (Production)
35
7 Jul 2025
1750300201 (17.5.0-RC-2-tor-0.4.8.17)
17.5.0-RC-2 tor-0.4.8.17 (Open testing)
35
7 Jul 2025

**Crash Logs (Advanced)**
None

**Additional Context**

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the reported issue on build 17.5.0-RC-2-tor-0.4.8.17 and inspect the attached Google Play screenshot. The issue names no failing screen, source file, entry point, or test, so identify which icon or button is unresponsive before tracing it. Done means the reported control responds and returns or loads its expected content.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.