Properties panel numeric field does not save when switching to Reading View on iOS

Bug reports
1

Once you’ve done the above, delete everything above this line.

Steps to reproduce

  1. Open any note with a numeric front-matter property (e.g. Calories: 410)
  2. Tap the property field and enter a new value (e.g. 1800)
  3. Without tapping outside the input field, tap the Reading View button

Did you follow the troubleshooting guide? [Y/N]

Yes

Expected result

The new value is saved to disk and appears in version history no matter where you click to exit the input box. If I click to change the view from editing to reading that should write the change (it currently does not), if I click somewhere on my note such as a heading that should also write the change (it currently does).

Actual result

The UI displays the new value, but the file on disk retains the old value. Confirmed by opening the file in the iOS Files app. No version history entry is created on any device and the change does not sync.

Environment

SYSTEM INFO:
Obsidian version: 1.12.7 (303)
API version: 1.12.7
Operating system: iOS 26.3.1 (Apple iPhone15,3)
Login status: logged in
Language: en
Catalyst license: none
Live preview: on
Base theme: dark
Community theme: none
Snippets enabled: 0
Restricted mode: on

RECOMMENDATIONS:
none

Additional information

image
image197×173 2.6 KB

image
image1290×1363 75.8 KB

image
image1290×761 50.9 KB

Example in source mode of the notes front-matter/properties. As well as a photo of the note in the Obsidian app (and the iOS files app) after I edit the calories number but press the button to change view as opposed to clicking somewhere on the note.

  • Workaround: tapping anywhere outside the input field (e.g. a heading) before switching to Reading View correctly commits the change and immediately creates a version history entry

  • Switching to Reading View dismisses the keyboard and updates the UI visually, creating a false impression the value was saved

  • This does not reproduce on desktop — any defocus of the input field reliably commits the value.

  • The apparent sync conflicts this caused over several months were downstream of this bug, the unsaved in-memory value on one device would conflict with a correctly saved value on another device

  • Affects numeric property types specifically; text properties were not tested