MerginMaps / MerginMaps/mobile

Last line of diagnostic log report is hidden by "Send to developers" button

Open
#4,381 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

android 🤖 bug Good first issue
Dominant language
C++
Stars
388
Forks
87
Avg merge
2d 7h
Merged PRs (30d)
20

Description

**Description**
When viewing a diagnostic log report, scrolling to the bottom causes, that "Send to developers" button overlap the last line of the log.
As a result, the final line of the report is hidden and cannot be read.

**Environment:**
Staging

**Application (+ app version, build, operating system)**
App version: 2026.1.2 (build 780651)
Device/OS: Samsung Galaxy A53 5G, Android 15

**Steps to reproduce:**

1. Open a project and click on the "More" option
2. Select Settings and scroll down
3. Select Diagnostic Log and scroll to the bottom of the report
4. Observe the last lines of the log.

**Actual results**
The "Send to developers" button olverlaps and hides the last line of the log.

**Expected results**
The full log content should be visible, when scrolling to the bottom.

**Screen-record**

https://github.com/user-attachments/assets/786d3a63-d2ac-46c0-80ea-7166db44a3ba

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Diagnostic Log screen reached through More, Settings, and Diagnostic Log, and reproduce the issue on the stated Android environment by scrolling to the bottom. Trace the mobile UI implementation responsible for the log content and the "Send to developers" button. Done means the final log line remains fully readable at the bottom of the report.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, cpp
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.