RepoJournal
Mobile platforms

Mobile platforms

Flutter, Swift, and Kotlin - the mobile platforms developers ship on

Keep up with Mobile platforms in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: Mobile Full archive →

The Wire · Showcase

FLUTTER FIXES GPU RENDERING RACE, SWIFT TACKLES OPAQUE VALUE CRASHES

By RepoJournal · Filed · About Mobile platforms

Flutter's Impeller renderer shipped a critical fix for a concurrent buffer upload race that could silently drop rendering commands, while Swift's compiler is wrestling with stack state verification failures in opaque value mode.

The Impeller dirty-range race [2] is the priority fix this morning: DeviceBufferGLES was reading dirty ranges on the reactor thread while UI threads were writing to them, causing uploads to silently clear ranges mid-flush and lose rendering data. Flutter also shipped a new GPU surface API [3] that lets the framework present rendered textures back through the engine, completing the Flutter GPU feature set for custom rendering pipelines. On the tooling side, flutter doctor now detects multiple adb installations [1] that conflict with device detection, addressing a longstanding developer pain point during Android setup. Swift's compiler landed index store support [4] enabled by default to power IDE features, but the team is actively debugging SIL verification crashes [5] in opaque values mode that break AsyncStream and Collection iteration. Kotlin's incremental compilation team is consolidating test infrastructure [7] [8] [9], moving duplicative tests down the stack, while Swift export gained cross-language interface conformance [6], letting Swift classes implement exported Kotlin protocols with proper dispatch.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] [flutter_tools] Add doctor validator warning for multiple adb installations (#186031) flutter/flutter
  2. [2] [Impeller] Fix dirty-range race in DeviceBufferGLES uploads (#187932) flutter/flutter
  3. [3] [Flutter GPU] Add surface API for framework presentation (#187358) flutter/flutter
  4. [4] build-script: Add --llvm-enable-index-store, defaulted ON ↗ apple/swift
  5. [5] Opaque Values: inconsistent stack states ↗ apple/swift
  6. [6] [Swift Export] KT-66890: Add interface discoverability to kotlin runtime for cross-language interface/protocol conformance ↗ JetBrains/kotlin
  7. [7] [BTA] Move class-visibility and Java-constant incremental scenarios to BTA JetBrains/kotlin
  8. [8] [Gradle] KQA-3101 Remove duplicate multiproject ABI-snapshot IC test JetBrains/kotlin
  9. [9] [Gradle] KQA-3101 Move KaptGenerateStubs compiler-args dedup check to functional test JetBrains/kotlin

Quick answers

What shipped in Mobile platforms on June 13, 2026?
Flutter's Impeller renderer shipped a critical fix for a concurrent buffer upload race that could silently drop rendering commands, while Swift's compiler is wrestling with stack state verification failures in opaque value mode. In total, 52 commits and 36 pull requests landed.
Who contributed to Mobile platforms on June 13, 2026?
3 developers shipped this update, including gottesmm, elsakeirouz, and glukianets.
What were the notable Mobile platforms updates?
[flutter_tools] Add doctor validator warning for multiple adb installations (#186031), [Impeller] Fix dirty-range race in DeviceBufferGLES uploads (#187932), and [Flutter GPU] Add surface API for framework presentation (#187358).

More from Mobile platforms

Daily updates, in your inbox

Follow Mobile platforms

Keep up with Mobile platforms in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?

We use privacy-friendly analytics (Google Analytics, IP-anonymized) to see which pages help readers. No ads, and we never sell your data. See our Privacy Policy.