I’m wondering if they didn’t pull this one also? It’s been days! This isn’t normal.
And you know this as fact right?As I said in previous replies, it's being deployed to 10% of devices. It wasn't "pulled", and neither was the previous one.
And you know this as fact right?
<key>Build</key>
<string>1A291c</string>
<key>DeploymentList</key>
<array>
<dict>
<key>deploymentLimit</key>
<integer>10</integer>
</dict>
</array>
"Device cannot apply metered rollout as it doesn't fall under %d percent. Device is %d percent."
If this is fact then I don't feel comfortable with it. Rolling out to 10%? I feel like a guinea pig with no choice in the matter. I think I'm going to delete my 4 tags and get my battery usage back and just take a wait and see approach.The only difference between 1A291a and 1A291c is the deploymentLimit (raised from 1 to 10):
Code:<key>Build</key> <string>1A291c</string> <key>DeploymentList</key> <array> <dict> <key>deploymentLimit</key> <integer>10</integer> </dict> </array>
There's also this log message in the CoreUARP framework handling various updates (not just AirTags), after it checks the deploymentLimit property:"Device cannot apply metered rollout as it doesn't fall under %d percent. Device is %d percent."
Is that enough to call it "fact"? I don't know 🤷♂️
I agree, something dodgy going on, not heard one person with update ?The only difference between 1A291a and 1A291c is the deploymentLimit (raised from 1 to 10):
Code:<key>Build</key> <string>1A291c</string> <key>DeploymentList</key> <array> <dict> <key>deploymentLimit</key> <integer>10</integer> </dict> </array>
There's also this log message in the CoreUARP framework handling various updates (not just AirTags), after it checks the deploymentLimit property:"Device cannot apply metered rollout as it doesn't fall under %d percent. Device is %d percent."
Is that enough to call it "fact"? I don't know 🤷♂️