I am having the same issue, no idea what's going on. I guess I’ll just wait to see if Apple finally fixes it?
It’s kinda frustrating because these kinds of issues seem to be happening all the time with CloudKit and the error messages are not helpful at all!
Again, this seems to be an issue:
The promo code for the following could not be generated. Try generating it again.
Just noticed that the last comment on this thread is also from me, 5 month ago.
It seemed to have fixed itself somehow, but now this issue is back!
Just updated to iOS 17.5.1, the issues still persists.
Would be great to get some communication from Apple on this:
Is this expected behavior or a bug????
I am seeing the exact same stuff, it’s very frustrating because it is super hard to debug. But glad to hear I’m not the only one.
I’ve filed a feedback report, hope that helps the screen time team to narrow this down: FB14082790
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...
I am having the same issue, no idea what's going on. I guess I’ll just wait to see if Apple finally fixes it?
It’s kinda frustrating because these kinds of issues seem to be happening all the time with CloudKit and the error messages are not helpful at all!
Again, this seems to be an issue:
The promo code for the following could not be generated. Try generating it again.
Just noticed that the last comment on this thread is also from me, 5 month ago.
It seemed to have fixed itself somehow, but now this issue is back!
Just updated to iOS 17.5.1, the issues still persists.
Would be great to get some communication from Apple on this:
Is this expected behavior or a bug????
I am seeing the exact same stuff, it’s very frustrating because it is super hard to debug. But glad to hear I’m not the only one.
I’ve filed a feedback report, hope that helps the screen time team to narrow this down: FB14082790
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...