- JourneyApps Product Team
The Legacy App Editor (build.journeyapps.com) is being deactivated next week
We are deactivating the Legacy App Editor (build.journeyapps.com) for all developers next week , the week of 21 February. Developers will no longer be able to access build.journeyapps.com from then onwards, and all apps that have not been migrated to be compatible with OXIDE will be deleted from JourneyApps by 18 March 2022.
Please migrate apps that you intend on using before 18 March 2022.
How to migrate your app
For your app to be compatible with OXIDE, you need a version 4 syntax app which is using a supported version control system.
Version 1 and version 3 syntax apps will need to be migrated manually to the version 4 syntax. Please see our guide which covers some of the changes between version 1 and version 4.
Your apps need to be migrated to be compatible with OXIDE. Do this by going to the Admin Portal, and clicking Migrate for each app.
Once you’ve migrated your app successfully, you can edit your app and deploy changes using OXIDE.
How do I know whether my app has to be migrated?
Apps that cannot be edited in OXIDE need to be migrated. In the Admin Portal a legacy app’s Version Control will be listed as “Revisions (Legacy)” and you will only be able to migrate your app from there.
What happens to apps that have not been migrated to OXIDE by 18 March 2022?
The app’s source code will be deleted, and the app’s deployments will also be deleted. Users will no longer be able to access the app.
Do I need to use Github to be able to use OXIDE?
No. If you want to use a git-based workflow, you can opt to use our JourneyApps Git version control system or the basic revisions system.
I cannot migrate my app to OXIDE by the date you have communicated. Can you extend the dates?
Unfortunately, these dates are final and have been communicated in advance. Please speak to us about specific blockers that prevent you from adopting OXIDE by the above dates.