Welcome!
This is where we announce new releases on JourneyApps.
You can subscribe for updates by clicking the button on the top right.
For older release notes, please go here.
Container 21.2.1
We're happy to announce that 21.2.1 of the JourneyApps Container has been released.
Added:
- The Broadcast API can now ignore events when the container is in the background using options.background. Compatible with 4.78.2 of the runtime. Read more in the docs here.
Notice: We’re deprecating the App Editor in favor of OXIDE
After the successful launch of OXIDE in September 2020, we are deprecating the App Editor (build.journeyapps.com) and will be removing it from JourneyApps in 2021.
This notice describes the timeline for the removal of App Editor, guides you through the steps you may need to take if you are affected by the deprecation, and answers questions you may have.
What you can expect
As of 15 February 2021 JourneyApps will only provide support for critical issues in the App Editor. You will only be able to manage developer access using the Admin Portal. You will also no longer be able to create new apps in the App Editor.
As of 15 March 2021 we will be removing the capability to make and deploy changes to apps from the App Editor. After this date, the App Editor will only be able to migrate your app to be compatible with OXIDE, and cannot be used for building apps, or managing users.
No later than 1 December 2021, the App Editor will no longer be accessible.
How to migrate your app
To ensure that you can continue to make code changes to your app, you need to migrate your app to be compatible with OXIDE. To do this you a version 4 syntax app which is integrated with Github or our OXIDE revisions source control system:
1. Version 1 and version 3 syntax apps will need to be migrated to the version 4 syntax.
- You can do that by accessing the Version Management menu under App Settings and following the steps to migrate your app.
- There are some code changes required to ensure that the app works as intended with the version 4 syntax. Please see our guide.
2. Your apps need to be migrated to be compatible with OXIDE. Do this by going to the Admin Portal, and clicking Migrate.
Once you’ve migrated your app successfully, you can edit and deploy changes using OXIDE.
Summary of dates
1. Deprecation: 15 February 2021
2. Removing support to manage developer access: 15 February 2021
3. App editing capability removal: 15 March 2021
4. Complete removal: Latest 1 December 2021
Common questions
What happens to apps that have not been migrated by 15 March 2021?
You will no longer be able to edit or deploy your app, but it will still be accessible in the App Editor. App users will be able to use the app without any interruption, though you will not be able to deploy updates to them until the app is migrated. Please migrate your app by going to the Admin Portal, and clicking Migrate. You can find the Admin Portal by clicking on the OXIDE logo on the top left when in OXIDE
What happens to apps that have not been migrated by December 2021?
App users will no longer be able to use the app. We will place the source code of your app in cold storage. If you wish to reactivate the app and edit it in OXIDE, there will be a cost involved.
Do I need to use Github to be able to use OXIDE?
Your app needs to be integrated with Github, or use our new OXIDE-compatible JourneyApps revisions system.
What are the biggest changes for using OXIDE above the App Editor?
You can read more about OXIDE here. It is designed to be a more productive app editing IDE, saving you precious time during development, and giving you more control over your app editing environment. To get the most out of JourneyApps, you should use OXIDE.
I cannot use OXIDE by the date you have communicated. Can you extend the dates?
Unfortunately, these dates are final. Please speak to us about specific blockers that prevent you from adopting OXIDE by the above dates.
How do I deploy my OXIDE app programmatically?
We have APIs that allow you to deploy your app if it is OXIDE-compatible. Contact us for more information.
Runtime 4.78 (latest stable)
We are excited to announce that 4.78 of the JourneyApps Runtime has been released. 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.
4.78.1
Added:
All input components with on-change will now report oldValue and newValue if specified as parameters, e.g.
on-change="$:handleChange(oldValue, newValue)"
Fixed:
An issue with the date picker's year not updating correctly when using keyboard shortcuts.
An issue where Object Table 3's typeahead did not correctly handle null values.
A regression where the hardware back buttons (Android) would break the app on Action sheets and Dialogs.
Improved:
Loading performance on web.
4.78.0
Added:
- Support for opening TCP Socket connections from the app. You can read the docs for more information.
Improved:
- We've implemented performance improvements for apps running on iOS, specifically focused on improving memory usage over time.
Runtime 4.77
We are excited that v4.77 of the JourneyApps Runtime has been released. 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.
4.77.3
Fixed:
- single-choice-dropdown now correctly indicates its validation error when used inside a dialog.
- A regression with icon alignment in object-table.
4.77.2
Fixed:
- A regression with single-choice-radio that incorrectly handled values when bound to an integer variable.
- A regression on text-input, where text:paragraph and text:address fields would not be correctly capitalized on mobile keyboards.
4.77.1
Fixed:
- An issue where show-if and hide-if would not hide card components in the view.
- An issue where on-long-press would not close consecutive dialogs.
- An issue with dialog not validating all its children components.
- A regression on text-input, where text:name fields would not be correctly capitalized on mobile keyboards.
- A regression where the hardware back buttons (Android) would break the app on Action sheets and Dialogs.
4.77.0
Added:
- Support for in and not in query operators. E.g.:
- Generate a PDF from HTML on the desktop JourneyApps Container.
Improved:
- Better .explain() output for app queries to help with performance analysis (only apps with the JSON1 app flag enabled).
- Faster lookups of related objects via .include() with OnlineDB.
- The info UI component has been refreshed, adding support for align-text.
- The display-signature and capture-signature UI components have been updated visually.
- Improved stack traces for TypeScript apps.
Fixed:
- Issue where the confirmation dialog was displayed behind splash screen when the app updated.
- Issue where the dialog component would attempt to validate all its child components although they were hidden.
- Issue with some Portuguese translations.
- Issue where re-registering the same callback on the html component would throw an exception.
New CloudCode scheduler interface
We're excited to release that you can now quickly configure CloudCode to run on a schedule with only a few clicks:
For more granular control you can still configure the schedule using a CRON string in Advanced scheduling mode.
Reminder: Backend API rate limits for all apps by 1 February 2021
We'd like to remind all developers that request rate limits to our backend APIs will be enabled on 1 February 2021.
Please refer to our previous notice for an explanation of how our rate limits work, and what you can do to handle rate limits in your app.
Please contact JourneyApps Support for questions, raising limits, or extensions.