`fid` field shown as empty instead of "* Mixed Values *" when editing multiple features

Open

#4,580 opened on Jul 2, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 55/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: cpp
Domain: mobile

Research direction

The issue does not identify a source file, test, or entry point. Reproduce the problem by editing multiple selected features with a visible fid field, then locate the form handling for mixed values and verify that fid displays "* Mixed Values *" consistently with other differing fields.

Written by the indexing model from the issue text.

Description

android 🤖 bug forms iOS 🍎

Description

When editing multiple selected features, fields with differing values correctly display * Mixed Values * as a placeholder. However, the fid field (when visible in the form) is shown as empty rather than displaying * Mixed Values *, which is inconsistent with the behaviour of all other fields.

Environment
[ ] Staging [x] PROD

Application (+ app version, build, operating system)

Mergin Maps mobile 2026.2.0, Android
Mergin Maps mobile 2026.2.0, iOS

Steps to reproduce

Open a project where the fid field is visible in the feature form (or create a new basic project with fid visible)
Select multiple features on the map
Tap Edit to open form for selected features**
Observe the form fields

Actual results

The fid field is displayed as empty. All other fields with differing values correctly show * Mixed Values *, and unsupported fields (e.g. photo) show Not available while editing multiple features.

Expected results

The fid field should display * Mixed Values * consistently with all other fields that contain differing values across the selected features.

Screenshots or logs

Conclusion
Created by Claude and supervised by a human test analyst.

Dominant language: C++
Stars: 388
Forks: 87
Avg merge: 4d 1h
Merged PRs (30d): 23

Contributor guide

Open 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.

Similar issues

Fix locale comparison when loading system translations Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

rizinorg/cutter#3664 · Opened Sep 23, 2026
Request headers and POST/PUT bodies silently corrupted once the wasm heap passes 2 GiB (signed pointers in http_wasm.cc) Open

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

duckdb/duckdb-wasm#2258 · Opened Sep 23, 2026
Dijkstra entry point crashes with ArrayIndexOutOfBoundsException when a vertex id exceeds the argument count Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

objectionary/eo-graphs#75 · Opened Sep 23, 2026
Coarray integration tests carry no LABELS, so run_tests.py silently skips them under every backend Open

coarray

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

lfortran/lfortran#13405 · Opened Sep 23, 2026
op-genesis-to-allocs.py: merge --rollup fork times per key instead of wholesale override Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

FISCO-BCOS/FISCO-BCOS#5642 · Opened Sep 23, 2026

More C++ issues