Get Ready! VertiGIS Studio Mobile 5.41 Release Candidate is Here!

Great news! The Release Candidate for VertiGIS Studio Mobile 5.41 is now ready, and our team has officially started the final regression testing phase.

We are targeting Wednesday, April 15th, 2026, for the General Availability (GA) release.

This release focuses on a major overhaul of Local Data Management and critical infrastructure updates to the ArcGIS Maps SDK, and includes over 30 bug fixes.

✨ Highlights in Studio Mobile 5.41 ✨

🚀 Core Engine & SDK Updates We have modernized the application's foundation to leverage the latest capabilities and meet evolving platform requirements.

• ArcGIS Maps SDK for JavaScript 200.8.1: This update includes critical stability improvements and memory leak fixes from Esri.
• Next-Gen iOS Pipeline: The build system has been upgraded to Xcode 26 and the iOS 26 SDK, ensuring full compatibility with the latest Apple hardware and App Store submission guidelines.

📂 Advanced Local Data Management We have significantly expanded the Local Data Manager to give our end-users more autonomy over their offline environment.

• Basemap Control: Users can now list and delete offline basemaps directly within the app, making it easier to manage device storage in the field.
• Search & Organize: We’ve added sorting and filtering capabilities within the Local Data Manager so users can quickly locate specific offline datasets.
• Improved Transparency: The UI now provides clear, actionable feedback when no offline data is present, reducing uncertainty during disconnected workflows.

🛠️ Reliability & Workflow Refinements We’ve squashed dozens of bugs to ensure a smoother experience for both the admin and the end-users.

• GNSS Shortcuts: The GNSS accuracy button now correctly launches the settings dialog, providing instant access to location configuration.
• Responsive Search: The UWP address search suggestions now dynamically resize and scroll, ensuring full accessibility on Windows tablets and small window sizes.
• Workflow Form Logic: We resolved several issues where form element properties -such as required field asterisks and default checkbox states- were not being respected.