Skip to main content

TBC App Discussion

App update — Core 1.3.6: version gating, push credentials, and a build-breaking fix

Two releases in one: what your members get, and what changes if you build your own app.

In the app — everyone

📱 Hold members on a minimum version, per platform. Raising it the day Google approved a release used to lock every iOS member behind a build Apple hadn't published yet. iOS and Android take their own values now, set in your WordPress admin.

⚡ One-tap restart when an update is ready. Opt-in and separate from the store gate: once a fix has downloaded in the background, members get a restart screen instead of waiting for their next cold start. It only appears after a download actually succeeds, so nobody gets stranded on it.

Fixed:

  • A post's 3-dot menu did nothing — Edit, Delete, Report, Pin, all of it, on every feed, since late June
  • Space groups collapse in the search scope picker, matching every other space list
  • Confirmation dialogs no longer fire into a closing sheet
  • Real-time events with no payload stopped erroring

In your WordPress admin — everyone

  • The Managed tab collects your Apple credentials in one sitting — App Store Connect key, APNs key, Team ID and Type — so you upload rather than email them
  • A dark splash image is finally possible on managed, where there was previously no way to supply one
  • An APNs Key ID that's really the App Store Connect Key ID is rejected on save. The two are indistinguishable by eye — same length, same character class, identical file format — and the mistake shows no symptom until iOS pushes silently never arrive

In the dashboard — if you build your own

🍏 Apple work no longer asks for an Apple ID. Registering identifiers, creating signing credentials and submitting builds all went through an interactive Apple ID, password and 2FA prompt. Everything Apple now authenticates with an App Store Connect key instead.

🔑 Somewhere to keep your push keys. The APNs key and FCM service account both get a slot. Apple lets you download an APNs key exactly once and nothing in your project references either file, so there was no record and no fallback copy. Storage, not delivery — the upload to EAS still has to happen.

Fixed:

  • White-labeled apps failed to bundle at all — the config required a login background the packager strips from every snapshot, while the dashboard reported the slot as satisfied
  • A blank Staging URL broke every build command, writing an empty value that invalidated eas.json
  • Generated commands now match your shell instead of assuming PowerShell

Also: EAS build-allowance meters so the Free plan's ceiling isn't a surprise, an optional dark splash slot, and separate Apple and Google submission cards.

Managed apps are handled on our side. Building your own? The app-side work is OTA-safe; the dashboard changes arrive with the core update.

Full changelog: https://www.twobirdscode.com/blog/item/tbc-community-app/

  • 3 likes