Yep, looking back we received from June 7 to June 10 as well.
It would be very helpful if Apple's services kept a public log of incidents/temporary bugs like this so that we could determine definitively that we correctly understand the expected behavior.
I guess it must have been unintentional. So I've closed our internal issue about it.
willft
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
User for
From
Arizona, United States
Post
Replies
Boosts
Views
Activity
I found no solution. But we've seen no one else reproduce it. I do think that your issue might be a different thing, as our error has a different status code than yours. Also our code as posted above does work for everyone but this one user. You may wish to check that (1) the item in question is actually in the keychain; and that (2) the item in question was inserted by your app.
You should be able to look up the item in question in the "Keychain Access" app on your mac. If you double click the item & click on "Access Control" it should list your full bundle ID (with team ID prefix).
Just to clarify, when you say this:
Your app sets the data protection level to .complete...
that would be us manually setting the data protection level on the .shm file? That's almost definitely not it.
Your app is launched into the background ...
This doesn't seem like an impossible situation since we do use BGProcessingTaskRequest in some places.
Thanks @DTS Engineer ! I'll look into these avenues.