Tokens change without reason after updating to iOS 17.5.1

Some of our users encounter an issue after updating their iPhone/iPad to iOS 17.5.1.

The tokens passed in the Shield Configuration extension don't match the tokens they selected in my app using the FamilyPicker before updating to iOS 17.5.1. It seems the tokens changed for no reason. My app can't match the token from the ShieldConfigurationDataSource to any tokens stored on my end, causing my shield screens to turn blank. The same applies to tokens in the Device Activity Report extension.

The only workaround I've found is to tell affected users to unselect and reselect apps and websites to block in my app. This gets them new tokens from the FamilyActivityPicker, which solves the issue. However, for some users, the bug reoccurs a few days later. Tokens seem to change again, causing the same issue in the Shield Configuration extension.

I am not able to reproduce the issue on my test devices so I have no sysdiagnose to attach. However, this issue is affecting other screen time apps:

A change in iOS 17.5.1 must have triggered this behaviour. Could an Apple engineer give us any updates on this?

Answered by DTS Engineer in 847740022

Different DTS Engineer here, btw.

Unfortunately I don’t have anything particularly useful to share here. As far as we can tell this is a bug. There’s no code-level workaround, because tokens are opaque by definition. The user-level workaround was mentioned by thomas_maht in their original post. It’s annoying, but AFAICT it works.

We’re using FB14111223 to track this. I had a quick look through all the bugs mentioned here, and it seems that all but one [1] have been marked as a dup of that lead bug.

If you want to be notified if/when there’s a fix, feel free to file a bug and ask that it be dup’d to that bug.

Beyond that, I’m outta ideas )-:

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] And I’m working to fix the state of that last one.

We had multiple reports of this exact issue as well from Opal users, we didn't open a bug report because we weren't able to reproduce the issue on our own devices 😢

I would also be very interested if this is a bug on our side (using the API wrong) or if this is something on Apple’s side.

Seeing multiple reports on this makes me think it’s more related to an Apple bug instead of individual bugs on our ends...

How are you identifying which token belongs to which application as I'm not getting any bundle name or localName from the activity Picker selected in my FamilyActivityPicker.

Is there any update on this, Thomas?

Seems like a pretty serious issue, but no feedback / input from Apple so far!

We also have this issue and it's happening on iOS 17.6 too, so apparently it's not resolved with the OS update unfortunately.

Hello everyone, I wanted to get back to this, it’s October now and we’ve seen some new iOS betas.

Did anyone of you find a workaround for this issue? I’m on the latest iOS 18.1 beta and I can still reproduce this problem every day.

As suggested by Apple in June, I have:

  • Filed a radar
  • Created a sample project to reproduce
  • Filed a DTS ticket

Even after 5 months: no responses.

I am very frustrated by their non-existing help with this issue.

We have confirmed this bug is still present. Please follow up in your bug report.

We have confirmed this bug is still present. Please follow up in your bug report.

Hello, is there an update on this? I am carefully optimistic that this has been resolved on 18.3 or 18.4. But would be great to get official confirmation. No news on the bug reports yet :/

We have confirmed this bug is still present. Please follow up in your bug report.

Bug is still present in latest iOS 18.4 beta 4.

Hello, I am sad to announce that the bug is still present on iOS 18.5 beta 1.

when will this finally be addressed?

it’s been a year already since this bug has been introduced.

does anyone actually look at the Radars?

here is my feedback: FB14082790

We have confirmed this bug is still present. Please follow up in your bug report.

We have confirmed this bug is still present. Please follow up in your bug report.

Hello @Engineer!

It’s now 8 months later after you suggested we should follow up with our bug reports. Could you please check that my bug report is with the correct team? So far I have not received ANY feedback / commend / workaround / bug fix proposal which is concerning: FB15500649

Different DTS Engineer here, btw.

Unfortunately I don’t have anything particularly useful to share here. As far as we can tell this is a bug. There’s no code-level workaround, because tokens are opaque by definition. The user-level workaround was mentioned by thomas_maht in their original post. It’s annoying, but AFAICT it works.

We’re using FB14111223 to track this. I had a quick look through all the bugs mentioned here, and it seems that all but one [1] have been marked as a dup of that lead bug.

If you want to be notified if/when there’s a fix, feel free to file a bug and ask that it be dup’d to that bug.

Beyond that, I’m outta ideas )-:

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] And I’m working to fix the state of that last one.

As far as we can tell this is a bug. There’s no code-level workaround, because tokens are opaque by definition. The user-level workaround was mentioned by thomas_maht in their original post. It’s annoying, but AFAICT it works.

Hey Quinn!

Thanks a lot for the update and confirming that this indeed a bug and sharing a user-level workaround!

Do you have any more information about the workaround? Because, as @thomas_maht has mentioned, the bug re-appears after a couple of days and that’s just too much to ask users to re-select apps every couple of days.

They rather rage-delete out apps (and blame us 3rd party developers for being incompetent), and it’s just impossible to communicate that Apple has not fixed this bug that exists for more than 18 months.

My personal device is affected by this as well, I’m happy to fly to Cupertino and reproduce the issue for the engineers if that would help. This has to be fixed with iOS 26!

Thanks a lot for your help!

the bug re-appears after a couple of days

Oh, I missed that. Yeah, that’d be annoying.

My personal device is affected by this as well

So, just be clear, the problem is reoccurring every couple of days on your personal device?

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Thanks for getting back to me on this!

So, just be clear, the problem is reoccurring every couple of days on your personal device?

Yes, I can temporarily fix this by re-selecting apps / tokens from the FamilyActivityPicker, but then after a couple of days the tokens change again and the problems come back (it’s very inconsistent in that regard: sometimes it’s just a couple of minutes / hours / days until the problems resume).

In my feedback request I have a minimal sample project and a video that shows the bug in action on my personal device: FB15500649

OK.

I see a bunch of sysdiagnose logs attached to your bug. Can you highlight one that’s most relevant? Specifically:

  • That was taken shortly after you saw the problem reoccur.
  • Is on a reasonably modern version of iOS.

Feel free to either reply here with the sysdiagnose log name, or just update your bug and then reply here letting me know that you’ve done so.

Oh, if none of your existing sysdiagnose logs meet the above criteria, wait for the bug to reproduce, then grab a new sysdiagnose log, attach it to your bug, and then reply here.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

I see a bunch of sysdiagnose logs attached to your bug. Can you highlight one that’s most relevant?

For sure!

Here’s a feedback request on this from iOS 26 beta two: FB18353106

FB18353106

Looking at that bug report from our side, your sysdiagnose_2025.06.24_18-19-38-tttt_iPhone-OS_iPhone_bbbbbbbb.tar.gz attachment [1] shows as “File has failed to upload from user's device”. Can you check it from your side?

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] Note that I redacted bits of the file name somewhat.

File has failed to upload from user's device

Sorry about that! I was under the impression that the feedback assistant is fetching & uploading the sysdiagnose in the background.

I don’t find that exact sysdiagnose file anymore, but you can find another recent sysdiagnose from iOS 26 beta 1 in this radar: FB17844364

(I checked, and for this one you can actually download the sysdiagnose)

Thanks a lot for your help on this!

File has failed to upload from user's device

Actually the daily ApplicationToken reset just happened to me again, this time on iOS 26 beta 3.

Please find a fresh sysdiagnose here: FB18764644

Hope that helps to narrow down the bug!

After we wrote yesterday, I re-selected all my apps / ApplicationTokens within my app, and just now the tokens provided into the ShieldConfigurationDataSource are all different and unknown to my app.

I really really really would love to know how I can prevent this from happening for myself & my users 🥺🥺🥺

Previously it has been indicated that changes in iCloud Family can trigger this – while this might be true, this can’t be the only trigger for changing ApplicationTokens. Nothing is changing in my iCloud family on a regular basis.

As offered before, I am more than happy to run any kinds of tests or collect additional debugging material / logs / etc in case that would be helpful (or even travel to Cupertino with my iPhone if nobody there can reproduce the issue).

Please find a fresh sysdiagnose here: FB18764644

Thanks.

I’ve confirmed that that bug has the right info and it’s landed in the right place. That’s about all I can do here. I’ve set myself a remember to come back and check on this in a week.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

If this can be of any help, I also included a sysdiagnose in my feedback FB14111223.

About a year ago, I reproduced the issue: my app blocked a website, but the web domain token in my store didn’t match the one provided by the ShieldConfigurationDataSource.

I indicated the timestamp at which the issue occurred and attached a sysdiagnose from that time. I just checked — the sysdiagnose is downloadable on my end, so it seems correctly uploaded.

It was recorded on iOS 17, so it might be slightly outdated.

Hope that helps. Thanks!

I’ve set myself a remember to come back and check on this in a week.

Thanks a lot, Quinn! I’m super grateful for your help on this <3

I’ve set myself a remember to come back and check on this in a week.

Hey Quinn!

I just wanted to let you know that I was still able to reproduce this on iOS 26 beta 4 which came out on Tuesday.

To further help narrow down the bug, I have collected another sysdiagnose on that latest beta and attached it to this feedback: FB18764644 (Filename: sysdiagnose_2025.07.26…)

Hope that helps!

Also, I’m really curious if you’ve heard anything back from the team!

Do they need any additional help reproducing this issue?

My offer still stands: if any additional help to reproduce this is required, I’ll fly all the way to Cupertino to help them out wherever I can!

I’ve confirmed that that bug has the right info and it’s landed in the right place. That’s about all I can do here. I’ve set myself a remember to come back and check on this in a week.

Hey Quinn!

Hope you’re having a great summer! Maybe you’re on vacation and haven't had a chance to check back on this, but I’d appreciate an update whenever you have a moment 🙏

Thanks a lot and have a great day!

Tokens change without reason after updating to iOS 17.5.1
 
 
Q