JourneyApps Product Team

Runtime 4.85.12

AUTHOR: JourneyApps Product Team

We are excited to announce that runtime version 4.85.12 stable has been released.

Version 4.85 introduces the grid UI component, device accelerometer support, and more detailed performance profiling for apps. Additionally, app digest cycles have been made more consistent across UI components and are now batched to improve app performance.

You can use this version of the runtime by selecting it from the list of stable runtime versions under App Settings/Runtime Version in OXIDE.



  • A "No enrolled user" error when opening the container after the user session has been locked.



  • A regression affecting pagination controls (e.g. on a paginated list), where the next button stopped functioning after navigating away from and back to a view.



  • An issue affecting the on() method when communicating with the html component, where the registered callbacks were not consistently cleared when dismissing or replacing a view.

    • Note: Registering a callback for a command using the on() method will now clear any callback already registered for that command on the specific component and view. Previously, subsequent callbacks registered for a command on a specific component and view were ignored.



  • An issue where floating action buttons sometimes failed to load upon navigating to or refreshing a view.

  • An issue affecting RealWear devices, where scrolling within the App Help screen sometimes incorrectly scrolled the underlying view.



  • A regression where certain keyboard shortcuts registered via the shortcut component deregistered unexpectedly.

  • A bug where an active object-dropdown in a dialog was not highlighted correctly in a voice controlled app.

  • An issue affecting devices running Android 5, where the GPS timed out when the device had no network/carrier connection.



  • An issue affecting Android devices, where the sidebar component did not overlay the map of the display- and capture-coordinates components as expected.

  • A bug with the dialog component, where validation was not performed when a dialog was submitted via a voice command.

  • Another bug with the dialog component, where auto voice commands failed to register within the body tag after opening the dialog more than once.

  • An issue affecting devices running Android 5, where images in the list component images showed as green squares.

  • A bug affecting NFC tag reading where active listeners were not first stopped before starting a new read session.

  • A bug where the close icon is not correctly shown when a view is set to mode="close".

  • An issue where users where unable to save a captured signature on devices with older browser capabilities.



  • journey.env which returns information about the deployment and backend environment that a user is currently enrolled in. Please note that journey.env has replaced journey.server. See its details here.


  • A regression affecting the scan-barcode component, where the label was undefined if it wasn't explicitly set.

  • A regression affecting a button-group within dialog component, where split buttons threw an error.

  • A regression affecting a marker-query of the capture-coordinates and display-coordinates components, where the icon-color and color attributes were not correctly applied.

  • An issue where the on-long-press action of the back button did not report the dismissed parameter correctly.

  • An issue where an infinite sync was triggered when data was uploaded on an mobile device while it is offline.


  • journey.server has been deprecated and should be replaced with journey.env to ensure that your app remains compatible with the JourneyApps Runtime. Please see its documentation for details. Note that journey.env is also available in runtime versions 4.84.16 and 4.83.7.



  • An issue affecting Android and iOS where the app could crash when querying a multiple-choice field using contains.



  • A regression with the search field in the dialog of the optionList component losing focus while typing.

  • An issue with object-table edit-select causing an internal error when the value of the cell was set to a DB object.

  • An issue with object-table pagination controls, where they could trigger another table's actions in certain scenarios.

  • An issue with the capture- and display-coordinates components causing attributes like icon and icon-color not evaluating correctly when specified using a $: function.

  • An issue affecting older containers, where users receive an error which prevents them from closing the capture-signature dialog.

  • An issue with object-list causing a validation error when require is set to true even if the user has selected an option.

  • An issue where triggering from a dialog with composable body would cause the app to freeze.

  • An issue with the shortcut component where a shortcut would incorrectly trigger a function on another view after navigating away.

  • An issue affecting iOS devices where the orientation sensor would request permissions on app startup if a recent crash was detected.



  •  A clearer error message when a Promise is being serialized. Previously an "Unsupported object type" error was thrown in these cases.


  • A regression affecting child components within the columns UI component, where they did not update as expected when the parent column's visibility changed.



  • A regression with the capture-coordinates UI component, where the loading spinner spun indefinitely when a device's location access was denied. Note that JourneyApps container version 22.9.3 or greater is also required for this fix.

  • A regression where the GPS status in the Diagnostics view incorrectly showed "GPS Not Supported on Desktop" for mobile devices. 

  • A regression affecting devices on JourneyApps container version 22.9.1, where the device's sensors could no longer be accessed when using journey.sensors.



  • A regression with edit- cells on an object-table, where the displayed value did not always update correctly.

  • A regression affecting the columns UI component, where show-if/hide-if did not show or hide columns as expected.



  • The grid UI component, which offers more advanced layout options for UI components on a view. See its official documentation here.

  • journey.sensors which returns a device's accelerometer, compass and orientation data (supported on Android and iOS). See its official documentation here.

  • journey.profiling to enable more detailed performance profiling for apps, accessible via the developer debug console on Desktop and Web. See more information here.

  • The following operators to query multiple-choice and multiple-choice-integer fields: =, !=, contains, in and not in. Previously, no query operations were supported on these field types.


  • App digest cycles (i.e. when the app recalculates values on the screen) have been made more consistent across UI components and are now batched to improve app performance.


  • An issue where the on-scan event on the scan-barcode component did not produce a blocking spinner when the function took some time to complete.

  • "Watch not present" errors that were caused when an object was referenced that is no longer available in a view after a digest cycle/update.

  • An app startup performance issue for apps with large amounts of data and indexes.

  • A build issue for TypeScript apps, where the build would fail if the app has a view.config.json file.

Please Note: We'd like to retrospectively announce a new feature that was released as part of runtime version 4.84.0:


  • The ability to bind an array to an object-dropdown. This will allow the user to select multiple options, where previously they could only select a single option. See an example here.

Powered by LaunchNotes