MerginMaps / MerginMaps/mobile
Incorrect step value behavior in numeric field - increments by +1 instead of 0
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
**Description**
When a numeric field is configured with following conditions: (Min:-10,Max10,Step 0, Prec 0), the value should not change, since the step is set to 0. However, the field incorrectly increments/decrements by +1 instead of remaining unchanged. **The configuration works correctly in the QGIS, the issue occurs only in mobile application**
**Environment**
Staging
**Application (+ app version, build, operating system)**
App version: 2025.7.0 (build 814011)
iOS version: iOS 26.0
**Steps to reproduce**
1. Open MerginMaps application on the mobile device
2. Open **the project tester-ws-1/tc05_decimals**
3. Click on Add button and Record a new feature
4. Open the feature form and **in the tab Range Edit - Min/Max** scroll down to the last field
5. Click on the “+” or “-” buttons next to the input field
6. Observe how the field behaves according to the description in the name
**Actual results**
The field value increases or decreases by 1
**Expected results**
The field value should stay the same when step = 0.
https://github.com/user-attachments/assets/9a61253c-a7b3-4031-bd82-b610c5981d50
Contributor 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.
Research direction
Reproduce the behavior in the Mergin Maps mobile application using project tester-ws-1/tc05_decimals on the stated iOS environment. Start with the Range Edit - Min/Max field and compare the + and - button behavior when the configured step is 0 against the expected unchanged value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, ios
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100