Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[iOS] Diagnostic log: Mergin user info line isn't bold, unlike on Android

Open Beginner friendly
#4,744 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
ios, swift
Domain
mobile

Research direction

Start from the Settings → Diagnostic log screen on iOS and locate where the Mergin user info line is built or rendered (search the iOS-specific sources for 'Diagnostic log' / Mergin user profile text). Compare with the Android implementation of the same line to confirm the bold styling you need to mirror. Done means the line renders bold on iOS when the Mergin User Profile is unavailable (signed out / no connection), verified by reproducing the steps in the issue.

Written by the indexing model from the issue text.

Description

bug iOS 🍎 ui/ux

Description
The Mergin user info line in the Diagnostic log looks different on the two platforms. On Android it's bold, so it's easy to spot when the Mergin User Profile is not available.
On iOS the same line is in normal text, so it blends in with the rest of the log and is easy to miss.

Environment
Staging/ Production

Application (+ app version, build, operating system)
App version: 2026.5.0 - 26.10.962111
Device / OS: IPhone 15 / iOS 26

Steps to reproduce

  1. Set up the state where the Mergin User Profile is not available, e.g. signed out / no connection
  2. Open Settings → Diagnostic log.
  3. Find the Mergin user info line.

Actual results
The Mergin user info line is in normal text, the same as the rest of the log.

Expected results
The line is bold, as on Android, so it stands out.

Reference (Android): the line is bold ✅
Attachments: [screenshots from both platforms side by side]

Image Image
Dominant language
C++
Stars
389
Forks
88
Avg merge
1d 11h
Merged PRs (30d)
21

Getting set up

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.

More from MerginMaps/mobile

All issues in MerginMaps/mobile

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.