[iOS] Diagnostic log: Mergin user info line isn't bold, unlike on Android
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
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
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
- Set up the state where the Mergin User Profile is not available, e.g. signed out / no connection
- Open Settings → Diagnostic log.
- 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]
- Dominant language
- C++
- Stars
- 389
- Forks
- 88
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MerginMaps/mobile
-
bluetooth bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MerginMaps/mobile#4741 ·
Maintainers usually reply within 1 day
-
bug ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
MerginMaps/mobile#4669 ·
Maintainers usually reply within 1 day
-
bug Good first issue ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MerginMaps/mobile#4665 ·
Maintainers usually reply within 1 day
-
bug ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MerginMaps/mobile#4647 · 1 comment ·
Maintainers usually reply within 1 day
-
android 🤖 bug ui/ux
Difficulty 3/5 Half a day Newbie friendliness 64/100
MerginMaps/mobile#4743 · 1 comment ·
Maintainers usually reply within 1 day
All issues in MerginMaps/mobile
Similar issues
-
8-membered-ring atrop stereo lost in 2026.09.1Possibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 Half a day Newbie friendliness 86/100
Maintainers usually reply within 2 days
-
thread safetyOpen1.0
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
libasr headers?Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Type: Bug :bug:
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
-
llvm-trunk
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day