Skip to main content

App update — Core 1.3.15: the app speaks Dutch, the system screens are yours, and the builder grows a screen tree

Core 1.3.15 is out, with the companion plugin at the same version. Read the two update-order notes at the end before you start — this release has them.

For members

  • The app speaks Dutch. A community translated the whole thing and sent it in, so it ships the way Spanish and Greek do: every screen, every add-on, and the plugin's own strings. It stays current as we add strings rather than drifting back to English. The picker and device detection pick it up.
  • The lock, maintenance and update screens now look like your community. They used to be three different shapes wearing colours nobody could reach, and a white logo drawn for a dark bar simply vanished on them. They share one shape now, wear your logo properly fitted, and each takes your own title, message and picture. Leave a box empty and members still read the app's own words in their own language.
  • Chats explain themselves. When you can't post, the chat says which reason: you blocked them, they blocked you, an admin quieted you here, you left, their account is gone. Moderators of a space or group chat can quiet a member from the member list and let them back in, and can remove any message. Member lists search and page properly.
  • Signing in lands where it should, in one move, and a link set to open in your browser goes straight there instead of stumbling through a blank screen.

For site owners

  • One Links widget instead of four. Tiles, List, Buttons and Chips are a single Links widget with a Layout choice, so changing your mind about the shape no longer means deleting the widget and retyping every link. A link can point at a community post now, not just a page.
  • A Screens explorer for widget screens. Every screen as a tree down the side, nest one under another to any depth, drag to reorder, rename inline, duplicate, search. Deleting moves a screen to a Trash you can restore from. App Screens gets the same column.
  • Move a widget to another screen, or duplicate it, from the widget's own header, carrying everything you set on it.
  • A setting sits on the screen it changes. Change Password moved to Password policy, the GIF picker and Scheduled Posts to Feed › Post box, Content Moderation to Profile.
  • The admin explains itself on request. The paragraphs beside every control are behind a ? now, across every plugin. Warnings and anything describing what's currently set stay visible.
  • Subscribers rows carry their history and say whether a purchase came from Apple or Google.

If you build your own app

This one needs a new build. Every Expo SDK 57 package moves to its current patch, and two icon fonts leave the binary, which is 1.3 MB lighter. IAP apps move to expo-iap 5.5.0; the dashboard re-pins it for you.

  • Core updates are fast now. The post-update dependency install ran a registry audit that took minutes and queued behind build uploads. Seconds now, and only when a dependency actually changed.
  • The build verdict is honest. A core update that changes a dependency always says "build", naming the packages, never "OTA-safe".
  • Builds is one card, newest five with a Show more. Every card is an accordion, one open per tab.
  • Fix icons and splash images in the preview — size, drag, Fit to safe zone, Centre — instead of a round trip through Photoshop.
  • Your own languages survive core updates, registered in a block the dashboard carries across each one.
  • An add-on names the core it needs, and can bring its own npm packages.

Two update orders that matter

Update the companion plugin before, or with, the core. The app now requires a plugin at least as new as itself and shows a "this community needs an update" screen otherwise. It clears itself the moment the plugin lands.

If you use TBC Automations, update it to 1.1.6 first, or in the same pass. Recipe notifications moved out of the app plugin into the add-on where they belong. Updating the app plugin alone leaves the older add-on sending to a row that no longer exists, so recipe pushes stop until it catches up. Settings and member opt-outs carry over either way.

Coming with your next app-store update.