Exciting Update: QField 4.0 Release Candidate is Here!
Hello everyone,
I hope you’re doing well and gearing up for a joyful end of the year! We’re thrilled to share some exciting news: QField 4.0 is almost ready, and we’re aiming for a release date of December 15th, 2025.
We are excited to share this news with you and invite you to try out the release candidate build. This is a great opportunity to ensure your workflows remain smooth and free from unexpected regressions.
You can access the test build here: QField 4.0 Release Candidate. This version is feature-complete, with the final release only differing by any bugs we fix together.
Areas to Focus On
QFieldCloud Enhancements: We’ve made significant improvements, including updates to the cloud projects list and the cloud project panel. Check out the new "cloudification" of pre-existing projects that were manually imported.
Feature Form Updates: The feature form has been revamped with a new dedicated read mode, and nearly all editor widgets have been redesigned. Testing your complex feature forms against this build would be valuable.
User Interface Polishing: The user interface has received numerous refinements. Be on the lookout for any visual regressions. A new location pie menu is available when tapping on your location marker, which is worth trying.
Project Creation Wizard: The new project creation wizard has undergone extensive testing, but additional stress testing would be beneficial.
For a detailed list of changes worth testing, check out the draft release notes here: Draft Release Notes.
Please don’t feel pressured to test if you’re short on time. We’re just very excited about this new version and can’t wait for December 15th!
I dont know if it’s the good place…but i paste what i write as answer to the link you have posted
Good job!
Could we have an option to show feature form list on half screen by default ?
Could we theme position border color with this version ?
There are few left words that not translated (in french)
Thanks for your hard work
If you meant ‘not translated’ as in not translatable, that’s different If you are aware of such issue, let us know, we’ll make the string translatable!
@Mathieu_Pellerin , for example,
here what is not translatable
Return home
Home, Favorites and Folders in Local Projects & Datasets
edit:
and there are some where translate words are here but they don’t work
like in Project Folder : Project Folder, Folders, Projects.
In fact nothing is translated in Project Folder
@Mathieu_Pellerin
In Process feature and in algorithms, when i’m on attributes form, there many words that not translatable
And in algorithms themself + and - buttons seems to do nothing
Edit :
And another thing, if i choose to not use algorithm and tap on X, it send me to feature list and not back to the entity
For the missing translation, that’s a limitation we have ATM whereas we don’t ship QGIS translation due to massive increase in APK size if we do so. It’s on a TODO list, but its priority is not too high at the moment.
@Mathieu_Pellerin, two more things, sorry…
I have an entity form with several tabs. Some attributes have constraints, and as soon as the last constraint is met, it automatically returns to the first tab.
However, other elements could be entered after the constrained elements.
Also, when using a list of values with the toggle button option in the form, enclosing the values in boxes would improve their readability.
I’ve been struggling with relative filenaming i 3.7.9, and the problem seems to exist in 4.0 as well (provided that my expression is written correctly)? A naming expression usingattribute(@current_parent_feature,'<fieldname>')to include fieldname in the saved image filename fails, see also 6862. It should work according to 5327.
If you are aware of such issue, let us know, we’ll make the string translatable!