Split geometry displays incorrect color when editing unsaved feature

Open

#4,632 opened on Jul 29, 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: 57/100

Issue type: Bug
Clarity: Clearly specified
Activity status: Quiet
Tech stack: ios
Domain: mobile-dev

Research direction

Start by reproducing the issue through Add, Record, Edit geometry, and the Split tool on an unsaved polygon or multipolygon with custom layer symbology. Trace how the geometry editor assigns colors before and after splitting, then verify that both saved parts use the configured layer color rather than yellow.

Written by the indexing model from the issue text.

Description

bug map tools

Description
When a new polygon/multipolygon feature is recorded and the user proceeds directly to Edit geometry without saving first, splitting the geometry results in the split part being displayed in an incorrect color (yellow) instead of the symbology color configured for the layer.

Environment
[ x ] Staging [

Application (+ app version, build, operating system)
Mergin Maps iOS 2025.6.0 / iOS 26.0 / iPhone 15

Steps to reproduce

Open a project with a polygon or multipolygon layer with a custom symbology color defined
Tap the Add button and select the polygon/multipolygon layer
Tap on the map to create a polygon geometry
Tap Record to confirm the geometry — do not save the feature
Immediately tap Edit geometry
Use the Split tool to split the geometry
Save the result

Actual results
The split part of the geometry is displayed in yellow, not in the layer's configured symbology color.

Expected results
Both parts of the split geometry are displayed in the symbology color configured for the layer.

Screenshots or logs

https://github.com/user-attachments/assets/78652a59-060d-4f28-99e6-ce9e2711a495

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

An automatic array with a negative run-time extent has a negative size instead of zero Open

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

lfortran/lfortran#13475 · Opened Sep 24, 2026
Use ament_cmake_ros_core::ament_ros_defaults instead of setting CMAKE_C_STANDARD or CMAKE_CXX_STANDARD Open

good first issue

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

ros2/message_filters#338 · Opened Sep 24, 2026
Needs documentation update: Qt6 install or build instructions are not provided Open

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

subsurface/subsurface#4984 · Opened Sep 24, 2026
[Bug] Desktop: DataChannel onBufferedAmountLow / onBufferedAmountChange never fires — missing C++ OnBufferedAmountChange override Open

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

flutter-webrtc/flutter-webrtc#2206 · Opened Sep 24, 2026
litertlm-android AAR ships no consumer ProGuard rules → "mid == null" SIGABRT in minified apps Open

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

google-ai-edge/LiteRT-LM#3739 · Opened Sep 24, 2026

More C++ issues