We’ve resolved an issue that caused Actions on the Table Component—such as External Link actions and Conditional Actions—to not complete consistently.

To apply this fix, you’ll need to rebuild any non-working Actions and publish a new build of your app. Once updated, the changes will take effect.

We've addressed an issue where the Secondary Button Action on the Form Component incorrectly triggered the Main Button Actions, especially when the main button had additional actions such as "Login" and "Link."

Please push a new build to see these changes reflected in your app.

You can now view Installed Components in the and navigate to them more easily within your app! To access this feature simply select the Components Icon on the Left hand side and scroll to the bottom. There you will see "Installed in App" which will show all Components that are currently being used in your app. From there you can select the Component and see which screens they are on which will allow you to navigate directly to the screen to view or make changes.

You can now search within your screens to navigate more easily within your app! To access this feature simply select the Screens Icon on the Left hand side and you will now see a Search bar at the top of the list of Screens.

Devices in selected regions were not showing "Relative Date" without formatting in Native builds. This has been resolved. You will need to run a new build to see the issue resolved.

Have you ever noticed that forms have a primary button to create a record but no easy way to add a cancel or back action? We've improved this by adding an optional secondary button to our form component. It's completely customizable and you can add whatever styles, text, and actions you like!

You would get a when saving an Airtable record with a Date to property using External Collections. This had to do with the way the properties were nested, and it is possible that this same improvement also fixes other 3rd Party Tools/Services that use a similar structure for their APIs.

You do not need to make any changes to your app for these changes to take effect.

They are now being correctly sent in ISO 8601 formatting. No action is needed in your custom actions for these changes to take effect.

Dates will look like this and DateTimes will look like this

Previously, the Date Picker component could only have a default date from a few predefined options, which made it difficult to have the correct date displayed for a detail screen that pulls from the current record. We've added Magic Text support so now your default date can be pulled from the database.

We refactored the code around how many of our components render to strip out duplicate refreshes and increase overall performance. This improvement affects lots of components, including Simple List, Map, Audio Player, and anything from the component marketplace. Both web apps and native apps will get the improved rendering, but a new build will be required for native apps.