Product2 publishers2 min readPublished
Apple leaves AirPods testers waiting on a charging case for beta firmware 9B5042a
Apple is rolling out AirPods beta firmware 9B5042a, up from public build 9A348, to H2 models including AirPods Pro 3, Pro 2 and AirPods 4. For teams that test or support apps on AirPods, most of the practical work is keeping track of which pair runs which firmware.
The Product Desk · Product desk
What happened
- MacRumors lists AirPods 5 and AirPods Max 2 as recipients too, and says the build is going out to developers and public beta testers.
- Apple does not publish notes for AirPods beta releases, so what 9B5042a changes has not been disclosed.
- Testers opt in through a beta toggle in the AirPods settings screen, available when the earbuds connect to a device on iOS 26, iPadOS 26 or macOS 26 or later.
- Apple's routine for getting an update onto AirPods calls for the earbuds in a closed charging case on power, in Bluetooth range of a Wi-Fi-connected device.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
- contradiction 9to5Mac counts three models so far while MacRumors lists five, so an owner of AirPods 5 or AirPods Max 2 can confirm the build arrived only by reading the firmware version on the pair itself.
- constraint Because nobody can trigger the install by hand, a tester cannot line the update up with a planned test session; an enrolled pair switches builds whenever its case conditions happen to be met.
- exposure A bug seen on an enrolled pair has no change list to be checked against, so a support ticket missing the firmware version cannot be sorted into beta regression or shipping bug.
Apple's guidance says to wait at least 30 minutes for AirPods firmware to install once the earbuds are in their powered case [9]. MacRumors says it can take a few hours, because AirPods have no software update option like the one other Apple devices have [10]. Take a QA engineer who enrolled a pair of AirPods Pro 2 before lunch. The gap between those two estimates decides whether they test the new build this afternoon or tomorrow.
The pitch, according to 9to5Mac, is that the build lays groundwork for features coming in iOS 27.1 or 27.2 [6]. The same report says the update might instead be mostly bug fixes and performance improvements [6]. What testers are actually doing is running a build that 9to5Mac says has unknown changes, and finding the differences by using it [6].
A test pool can now hold three builds at once [1]. AirPods Pro 3, Pro 2 and AirPods Max 2 run public firmware 9A348, the just-launched AirPods 5 run 9A350, and enrolled pairs move to 9B5042a [2][1].
For a team that tests or supports software on AirPods, each pair can be sorted by two things: whether its beta toggle is on, and whether it is a reference device used to reproduce what customers see. Reference pairs with the toggle off stay on the build most customers have. Test pairs with the toggle on show what 9B5042a does before a wider release. A test pair left off adds nothing the reference pairs do not already cover. The fourth square, a reference pair switched on, carries the risk. The charging-case routine can move it to the beta overnight [9]. Both reports explain how to opt in and install, and neither describes a way back to public firmware [7][9].
I would keep reference pairs off the beta and enroll separate test pairs. The cost is a second pair for each supported model. A reference pair on public firmware also will not reproduce problems from customers who joined the public beta on their own [4].
What to watch
- Whether 9B5042a or a successor ships publicly alongside iOS 27.1 or 27.2, which would test 9to5Mac's groundwork theory against its bug-fix alternative.
- Whether testers report the build on AirPods 5 and AirPods Max 2 pairs, settling the split between 9to5Mac's three-model list and MacRumors' five.
- An Apple support document describing how to leave the AirPods beta and return a pair to public firmware.