10.6.6

Stable

April 02, 2024

Mendix Studio Pro is our low-code IDE for professional developers. It's a powerful visual model-driven development environment to build apps on the Mendix Platform. With Studio Pro you can easily create, change, integrate, test and deploy your applications, all in one place. Moreover, you can manage branch lines and security as well as extend your app with custom code using the built-in editors. Click 'Download Studio Pro' to get the installer for free (Windows OS required*). Learn more about the installation and the Studio Pro capabilities in our documentation. Not a professional developer? Learn How Mendix supports different developer profiles .Before installing, please read the Release Notes to learn about improvements, bug fixes, backwards compatibility, breaking changes and known issues. *If you are using a Mac, check out these instructions first.

Release Notes - **Release date: April 2, 2024** ### New Features #### WebSQL replacement We introduced an alternative for WebSQL with this release. After upgrading to this release, opening your offline PWA in your browsers automatically upgrades your WebSQL database to a new SQLite-based database. For this to function correctly, the browser must run in a Secure Context, which means either an HTTPS connection or by accessing your offline PWA via localhost. All functionality will remain functioning as is. ### Improvements * We have removed react-native-code-push dependency. We recommend migrating to Mendix OTA instead. * We improved the memory consumption in Studio Pro by resolving a memory leak caused by a rebase notification bar. ### Fixes * We restored the original functionality in Azure file storage, where a container name can be specified in `com.mendix.storage.azure.BlobEndpoint` runtime setting. This fixes a [known issue](#ki-runtime-settings). (Ticket 210679) * We fixed a [known issue](#ki-logic-editors-not-set) in the logic editors where sometimes the type of an output variable of an action showed as *(not set)*. (Tickets 205751, 207251) * We fixed an issue where a concurrency error happened when retrieving a session while optimistic locking was enabled. (Tickets 183769, 198138) * We fixed an issue where download file was not working on Android if the files encryption was enabled. (Tickets 204783, 204891, 211451) * We fixed an issue where the entered text does not get saved in the Text editor control. (Ticket 207346) * We fixed an issue when the text box has an invalid layout in the SQL query editor dialog box. (Ticket 209558) * We fixed an issue when the **Oops** pop-up window appeared when trying to move a remote entity with one-way navigable associations. (Ticket 210793) * We fixed an issue in the logic editors where sometimes the type of an output variable of an action showed as *(not set)*. * We improved Studio Pro general performance: simple object moves no longer trigger consistency checks in the logic editors. * We fixed some spurious foreign key constraint violation errors when using the built-in database (HSQLDB) and foreign key constraints. * We fixed the problem that anonymous user objects were kept in the database when their associated anonymous sessions were deleted on application startup after a model update. ### Known Issues * In some cases, even if you are already logged in to Studio Pro, you might still need to click **Sign in** under the **MendixChat** tab to make MendixChat available for use. * Fixed in [10.8.0](https://docs.mendix.com/releasenotes/studio-pro/10.8/#fix-sign-in). * Line endings in CSS files are not being handled properly, so when using [Revert All Changes](https://docs.mendix.com/refguide/using-version-control-in-studio-pro/) or performing other version-control operations, CSS files appear in the [Changes on Disk](https://docs.mendix.com/refguide/version-control-menu/#show-changes) dialog box. * Workaround: For details, see [this section](https://docs.mendix.com/refguide/troubleshoot-version-control-issues/#css-error) in *Troubleshooting Version Control*. * A finished parallel split path that is removed from a running workflow instance wrongly leads to a versioning conflict. Please note that "path" was called "branch" in earlier versions.