Usually , when Apple releases an AirTag update , it roll it out in waves over several weeks to poise the loading on its server . One of those firmware update was supposed tobegin revolve out on Wednesdaywith the rendering 2.0.73 update attain 100 percent of users by April 9 .
But that gradual rollout did n’t bechance – instead , it pop off to all alive AirTags in the wild at the same sentence . And the reason why is kind of funny . Over on X ( officially Twitter)@iSWUpdatesspilled the beans : Apple enter the dates wrong in the system , do the update to be free to all AirTags at once .
attend like Apple unintentionally set the deployment date for the 2.0.73 AirTag microcode to " m / d/24 " alternatively of " m / d/2024 " that has used in previous versions and which the AirTag update scheme apply as date format . As a result , AirTags think the deployment particular date are in the class 24…pic.twitter.com/dH5s0FrgTy
In the screenshots provided by @iSWUpdates , the dates for a previous update , 2.0.61 , are entered in mm / Doctor of Divinity / yyyy format . However , the dates for the unexampled 2.0.73 update are entered as mm / dd / yy , which meant that Apple ’s system render the year as 24 , not 2024 – and since we ’re well past the year 24 , Apple ’s scheme exit ahead and issued the update all at once .
The only event to the user is that it ’s possible that it adopt a bit longer than usual for an AirTag to update due to a logjam . Users ca n’t verify when an update occurs ; it normally happens when the controlling iPhone is in stove . However , chances are you did n’t even notice the update installed .
As for what ’s in the update , no one really knows outside of Apple . The companionship has yet to update itsAirTags update financial backing documentwith information on version 2.0.73 . If you really want to know , check back at a previous clock time .
