Qt 6.10.3, QGIS 3.44.10 upgrade

[tomasMizera]

This PR combines all necessary upgrades to our dependencies. The major upgrades include

• Qt 6.10.3
• QGIS 3.44.10
• iOS 26

The full checklist:

• macOS

  • build
  • run
  • working CI (position test failing)

• iOS

  • build
  • run
  • working CI (upload to testflight failing)
  • problems detecting safe area on iOS

• Linux

  • build
  • run
  • working CI (position test failing)

• Android

  • build
  • run
  • working CI

• Windows

  • build
  • run
  • working CI

• double-check all the updated patches, especially positioning ones (some are not even used now)

[github-actions]

📦 Build Artifacts Ready

OS	Status	Build	Info	Workflow run
macOS Build	❌	Build failed or not found.		#6738
linux Build	❌	Build failed or not found.		#6749
win64 Build	❌	Build failed or not found.		#5933
Android Build	❌	Build failed or not found.		#8050
iOS Build	📬		Build number: 26.04.898911	#8989

[github-actions]

📦 Build Artifacts Ready

OS	Status	Build	Info	Workflow run
macOS Build	📬	Mergin Maps 67401 dmg	Expires: 22/07/2026	#6740
linux Build	❌	Build failed or not found.		#6751
win64 Build	❌	Build failed or not found.		#5935
Android Build	❌	Build failed or not found.		#8052
iOS Build	📬		Build number: 26.04.899111	#8991

[Withalion]

Missing things from SafeArea PR:

• Fix MMHighlight to render map sketches in real time and to highlight selected features on the map. currently it does not work
• Check if we should refactor how safe area is handled in QML components, we can keep it as it is, or maybe there is a better way to do it

[IvaKuklica]

Summary of testing:
🤖 Android:

🔴 NEW ISSUE:
`
1. Photo delete button appears unresponsive in feature edit mode
Summary: When editing a feature that has photos attached (added via camera or gallery), tapping the trash/delete button on a photo produces no visible feedback — the photo appears to remain in place. However, the deletion is actually being processed in the background, and an empty photo placeholder icon is shown in its place. The UI fails to reflect the deleted state immediately, making the action appear broken to the user.

Screen_Recording_20260513_092224.mp4

2. Camera opens with Front camera instead of back camera.
The camera previously opened with the back camera by default, but now it uexpectedly opens with the front/selfie camera instead.

3. Map sketches render with delay and eraser strokes not visible
Summary:
a. When drawing sketches on the map, there is a noticeable time delay before the strokes appear.
b. Additionally, when using the eraser tool, the expected red eraser lines are not displayed — the erasing action is not visually represented on the map in real time.

4. No visual indication of selected features during bulk delete
Project: tester-ws-1/tc04_recording
Summary: When attempting to delete multiple features at once, there is no visual feedback to indicate which features have been selected for deletion.

5. Add button non-functional when EDITING geometry of a multipoint feature
Project: tester-ws-1/tc04_recording
Summary: When editing an existing multipoint feature and attempting to add an additional point, the Add button does not respond and has no effect. As a result, it is not possible to extend a multipoint feature with new points through the edit geometry workflow.

Screen_Recording_20260513_111943.mp4

6. Add button unresponsive when capturing NEW polygon
Project: tester-ws-1/tc04_recording
Summary: When creating a new linestring or polygon feature, the Add button used to capture vertices is unresponsive and has no effect. As a result, it is not possible to record the geometry of new line or polygon features through the standard capture workflow.

Screen_Recording_20260513_113204.mp4

7. Polygon and linestring geometry not updated correctly when editing vertices
Project: tester-ws-1/tc04_recording
Summary:
a. When editing an existing polygon feature, the shape of the polygon does not adjust correctly to reflect the changes made. Additionally, vertices are not placed in their correct positions, resulting in inaccurate geometry after editing. Also all buttons on control panel are unresponsive or they have a time delay.

b. Similarly to the polygon issue, the vertices of linestrings are not correctly aligned with the actual line geometry — the handles do not correspond to the true positions of the line's nodes. The mismatch between the displayed line shape and the vertex handle positions indicates incorrect vertex placement during the edit geometry workflow.

8. First vertex not displayed and line shape missing until second point is added when recording a linestring
Project: tester-ws-1/tc04_recording
Summary: When recording a new linestring feature, tapping the Add button to place the first vertex does not display it at the starting point of the line. Additionally, the line shape is not rendered on the map until a second vertex is added, leaving no visual feedback for the initial point placement.

Screen_Recording_20260513_132743.mp4

9. Photo capture fails when photo is configured to save to a status-based subfolder
Project: tester-ws-1/test_subfolders
Summary: When a feature form is configured to save photos to a subfolder based on the status field default value (e.g. photos//<ddMMyy_hhmm>.jpg), attempting to take a photo with the camera or upload one from the gallery fails. An error message is displayed: "Failed to process the image, photo directory resolving failed".

10. Add feature button unresponsive when adding a new child record via relations
Project: tester-ws-1/tc05_relations
Summary: When attempting to add a new child record through a relation (via the child's list), tapping the Add feature button has no effect — the button is unresponsive and the new child feature form does not open.

Screen_Recording_20260513_154632.mp4

Existing issue:

• Coordinates not saved when photo is taken in portrait/landscape mode #4168
• “Delete” button unresponsive after uploading photo from gallery. #4164
• Reuse last value option doesn't work well with default values #1496
• Expression-based field not recalculated when value relation field changes on mobile (Apply default value on update) #4439