Release history

TestFlight External · Google Play closed testing

Driving screens explain when McQueen is plugged in, animation labels leave controls in place, and landscape warnings and tabs fit more cleanly.

• Diagnostics explains that driving controls do not work while McQueen is connected to power; a warning appears above the driving touch areas when the car reports it is plugged in.
• Animation labels float over the warning without moving the driving controls or reserving extra vertical space.
• Landscape warnings are centered, use only the width their content needs, and have equal spacing above and below.
• Landscape tab bars keep buttons fully visible with even spacing. On iOS, the bar extends to the bottom edge without a red outline while the buttons keep their position.

iOS: Available in TestFlight for external testers. Android: Submitted to Google Play closed testing; checks and review are in progress. Tester availability is pending.

Testing focus at release: Connect to McQueen, check Diagnostics, then plug and unplug the car’s power cable. Rotate between portrait and landscape, trigger an animation while plugged in, and check that the warning and touch areas stay in place. Check both tab buttons and the iOS bar above the home indicator.

Known limitations at release: The power warning uses the car’s reported charging state and can lag a cable change until a new reading arrives. These are display changes; firmware data and repair behavior are unchanged.

Link to this build

Google Play closed testing

Adds the plugged-in driving warning, floating animation labels, and improved landscape spacing on Android.

• Diagnostics explains that driving controls do not work while McQueen is connected to power; a warning appears above the driving touch areas when the car reports it is plugged in.
• Animation labels float over the warning without moving the driving controls or reserving extra vertical space.
• Landscape warnings are centered, use only the width their content needs, and have equal spacing above and below.
• Android landscape tab buttons stay on screen with even spacing.

Android: Submitted to Google Play closed testing, then superseded by build 47 before tester availability was confirmed.

Testing focus at release: Check the plugged-in warning and animation labels in landscape, then switch tabs and rotate back to portrait.

Known limitations at release: The power warning uses the car’s reported charging state and can lag a cable change until a new reading arrives. These are display changes; firmware data and repair behavior are unchanged.

Link to this build

TestFlight External · Google Play closed testing

iOS Diagnostics buttons respond across their full area, repair agreements open more reliably, and both platforms help Support connect reports after an app reinstall.

• Fixed iOS Diagnostics panels and button artwork intercepting taps; the full button surface responds.
• Reinstall Core Software immediately shows its power check, and firmware agreements use one presentation with protection against repeated starts.
• iOS preserves the Diagnostics presentation as a firmware operation starts, preventing the enclosing screens from dismissing during the transition.
• Support reports on iOS and Android retain or link device history across reinstalls when available.

iOS: Available in TestFlight for external testers. Android: Available to selected testers, verified in Google Play Console on September 10, 2026.

Testing focus at release: Connect to McQueen, refresh Diagnostics, and tap buttons near their edges. Open and cancel a repair agreement, then try Send Diagnostics. On Android, send a report before clearing app data or reinstalling to link earlier reports. If Support asks for a firmware repair, send diagnostics immediately afterward.

Known limitations at release: Firmware data, transfer pacing, and success checks are unchanged. This build does not claim to fix incomplete Firmware B installation. iOS support-ID persistence across reinstalls is not guaranteed; Android must send a report before clearing data to link an older installation ID.

Link to this build

TestFlight External · Google Play closed testing

A plain link on the required update screen lets you continue for the current connection. Reconnecting brings the update prompt back if McQueen still needs it.

• Added a plain “Skip update for this connection” link at the bottom of the required firmware update screen.
• The skip remains in effect when you refresh Diagnostics and resets whenever the car disconnects or a new connection starts.
• Paused Firmware B verification offers the same choice once the car has returned to normal operation.
• Diagnostics records the skip while preserving firmware readings and unfinished update records.

iOS: Available in TestFlight for external testers. Android: Submitted to Google Play closed testing. Review status and device rollout are not yet verified.

Testing focus at release: When an update is required, choose Skip update for this connection, try the controls, and refresh Diagnostics. Then disconnect and reconnect without restarting the app: the update prompt should return if McQueen still needs it. Send Diagnostics with any unexpected behavior.

Known limitations at release: Skipping does not repair the car’s firmware or confirm that all controls will work. The link is available once the car is operational and its startup check has completed. An active update or verification must finish or stop before it can be skipped.

Link to this build

TestFlight External · Google Play closed testing

Adds diagnostic evidence for Firmware B repairs that transfer their pages but fail to complete verification.

• Support logs record each Firmware B page and enough detail to compare the transferred data with the bundled firmware.
• Reports capture the car’s finalization replies and reconnect timing to help explain where a repair stopped.
• Firmware repair commands, pacing, and success checks are unchanged.

iOS: Available in TestFlight for external testers. Android: Submitted to Google Play closed testing. Review status and device rollout are not yet verified.

Testing focus at release: Connect to McQueen, refresh Diagnostics, and test Send Diagnostics. If Support asks you to retry a firmware repair, keep the car charging and upload diagnostics immediately afterward. Include what happened and the report reference.

Known limitations at release: This is a diagnostics update, not a confirmed fix for failed repairs. Recovery on the affected iOS cars still needs verification. The additional raw-response capture is bounded and can end before every reconnect reading is recorded.

Link to this build

TestFlight External · Google Play closed testing

A failed repeat Firmware B check no longer creates a repair warning when B already replied on the same connection. Repair screens provide a clear way back after Bluetooth disconnects.

• Diagnostics remembers an earlier successful Firmware B reply for the current connection while keeping the latest reading separate.
• A missed repeat reply alone no longer locks controls for Firmware B repair. Explicit pending updates and outdated firmware still require their applicable repair.
• If Bluetooth disconnects while a repair agreement is open, Back to Connection lets you reconnect and run a fresh check before choosing repair again.
• Diagnostic messages and support logs distinguish a failed refresh from an earlier successful Firmware B reply.

iOS: Approved and available in the TestFlight External group. Android: Submitted to Google Play closed testing; quick checks and review are in progress. Device rollout is not yet verified.

Testing focus at release: Reconnect to McQueen, refresh Diagnostics, and try normal controls. If a repair agreement loses its connection, return to Connection and check again. Send diagnostics with what you tried, expected, and saw, especially if lights, sound, driving, or Bluetooth still fail.

Known limitations at release: We're still testing connection reliability and recovery on cars with lights, sound, or movement problems. Please send diagnostics if your car disconnects or doesn't respond as expected.

Link to this build

TestFlight External · Google Play closed testing

Firmware B repair follows the car’s restart and checks fresh firmware readings. Sending diagnostics to Support is now built into the app.

• After Firmware B finishes transferring, the app reconnects and checks the installed firmware before reporting success.
• If verification is interrupted, you can check again, retry the repair, or stop checking.
• Share Diagnostics uploads directly to Support with an optional email and a field for what you tried, expected, and saw happen.
• Your email is remembered for later sends, and a persistent support device ID helps Support find reports from the same app installation.
• Successful uploads show a support reference. If sending fails, you can retry, cancel, or save/share the diagnostics file.

iOS: Approved for external TestFlight testing. Android: Submitted to Google Play closed testing; review and device rollout are separate.

Testing focus at release: Test Firmware B recovery and the checks after the car restarts, then reconnect and try normal controls. Send diagnostics with any symptoms and expected behavior; email is optional. Check that the email and support device ID remain the same after restarting the app.

Known limitations at release: Recovery still needs confirmation on the affected physical cars. Clearing app data or reinstalling can create a new support device ID.

Link to this build

TestFlight External · Google Play closed testing

This build addresses a Bluetooth send stall that could leave Firmware B recovery at 0%, and makes it easier to understand which repair step your car needs.

• Firmware B transfers now have bounded waits so an interrupted Bluetooth send can stop with an error instead of waiting indefinitely.
• After a failed transfer, retries reconnect to the same car and restart the transfer from the beginning.
• Repair screens name Firmware B explicitly and explain when Firmware A has already been verified.
• More detailed recovery diagnostics help identify where a transfer stopped and what Bluetooth was waiting for.

iOS: Approved for external TestFlight testing. Android: Submitted to Google Play closed testing; review and device rollout are separate.

Testing focus at release: If you are testing recovery, follow the app’s charger, battery, and confirmation steps. Tell us whether Firmware B moves past 0% and completes, and include a diagnostics export if it stalls.

Known limitations at release: Successful Firmware B recovery on the affected physical car is still awaiting confirmation.

Link to this build

TestFlight External

Fixes an iOS recovery stall where the car accepted setup but the firmware transfer stayed at 0%.

• Firmware A recovery sends small, bounded batches and waits for the car’s receipt before continuing.
• Added transfer diagnostics while retaining the interrupted-recovery timer fix.

iOS: Approved for external TestFlight testing. No Android store upload was included in this release.

Testing focus at release: Try Firmware A recovery, then reconnect and check fresh firmware readings.

Known limitations at release: This build was distributed through TestFlight only. A later support report confirmed Firmware A recovery on the affected car; Firmware B needed separate follow-up.

Link to this build

TestFlight External · Google Play closed testing

Prevents an old wake timer from cancelling firmware recovery after it has taken over the connection.

• Ordinary connection and wake deadlines no longer interrupt active recovery.
• Transfer diagnostics distinguish queued bytes from bytes acknowledged by the car and record timeout and retry details.

iOS: Approved for external TestFlight testing. Android: Submitted to Google Play closed testing; review and device rollout are separate.

Testing focus at release: Resume an interrupted repair and export diagnostics if the transfer stalls.

Known limitations at release: The initial bootloader transfer stall was still under investigation at release; physical recovery was not yet confirmed.

Link to this build

TestFlight External · Google Play closed testing

Adds clearer evidence for cars that connect but do not respond to controls.

• Diagnostics trace control actions through Bluetooth submission, car responses, and timeouts.
• Light, screen, and sound checks record what you saw and heard.
• Firmware and battery readings show their age, and recent logs remain available when a log fills.

iOS: Approved for external TestFlight testing. Android: Submitted to Google Play closed testing; review and device rollout are separate.

Testing focus at release: Try the physical output checks and share diagnostics for controls that do not respond.

Known limitations at release: Physical recovery on affected cars remained unverified at release.

Link to this build

TestFlight External · Google Play closed testing

Improves firmware recovery, uses fresh car readings, and corrects the headlight and taillight commands.

• Recovery and update retries handle interrupted connections more reliably.
• Firmware checks use fresh readings instead of old cached values.
• Driving restrictions while charging are handled by the car; firmware-update power requirements remain in place.

iOS: Approved for external TestFlight testing. Android: Submitted to Google Play closed testing; review and device rollout are separate.

Testing focus at release: Check reconnecting, light controls, firmware readings, and recovery retries.

Known limitations at release: Physical recovery on affected cars remained unverified at release.

Link to this build

TestFlight · Beta approved

Detailed release notes are not available for this build.

Approved for external testing; tester availability at the time is not recorded.

Link to this build

TestFlight beta

Improved error handling around firmware updates.

Released to external testers.

Link to this build

TestFlight beta

Firmware diagnostics and repair.

Released to external testers.

Link to this build

TestFlight · Beta approved

Added firmware diagnostics and repair.

Approved for external testing; tester availability at the time is not recorded.

Link to this build

TestFlight · Beta approved

Additional logging.

Approved for external testing; tester availability at the time is not recorded.

Link to this build

TestFlight · Beta approved

Added additional logging.

Approved for external testing; tester availability at the time is not recorded.

Link to this build

TestFlight · Beta approved

Added charger diagnostics.

Approved for external testing; tester availability at the time is not recorded.

Link to this build

TestFlight · Beta approved

Added charger test.

Approved for external testing; tester availability at the time is not recorded.

Link to this build

TestFlight · Beta approved

Battery diagnostics.

Approved for external testing; tester availability at the time is not recorded.

Link to this build

TestFlight · Beta approved

Added diagnostics link for Bluetooth debugging.

Approved for external testing; tester availability at the time is not recorded.

Link to this build

TestFlight · Beta approved

Diagnosing bluetooth connection issues.

Approved for external testing; tester availability at the time is not recorded.

Link to this build

App Store

The first public App Store release of Red Thunder Remote.

Public store release.

Link to this build

Google Play · Open testing

Detailed release notes and the original release date are not available in the retained record.

Verified in the Google Play open testing track on September 8, 2026.

Link to this build

Google Play · Production

Detailed release notes and the original release date are not available in the retained record.

Verified in the Google Play production track on September 8, 2026.

Link to this build