Just tried building in Xcode 14 then switch back to Xcode 15, it didn't solve the issue on my side unfortunately.
thomas_maht
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
From
Paris
App Store
https://apps.apple.com/app/id1609960918
Post
Replies
Boosts
Views
Activity
The container app and the Device Activity Report extension can share an app group. However, the extension can only read from the app group due to the sandbox restrictions. Attempts to write in the shared app group from the app extension will fail. So I guess the app group can't be used to monitor the extension status.
@eskimo Do you know who is currently supporting FamilyControls?
A slight correction to my first answer: you would be better off saving a token for the same application to a JSON file on BOTH devices. Then, you would simply need to compare the contents of the files to see if they match up.
No, you can't get past this limit when using the Screen Time API. I don't know if it will be lifted in the future as I don't work at Apple. You can file an enhancement request to them about this.
In the meantime, you could maybe use a dedicated Safari content blocker to achieve what you want. For example, I know that 1Blocker makes extensive use of these content blockers and the app is pretty powerful: https://support.1blocker.com/en/articles/6436183-quick-access-to-content-blockers-in-safari.
In my case, my app entity was declared twice under the same name: once in my main app target and once in my app intents extension, where I used it for a focus filter.
I resolved the issue by renaming my app entity in the app intents extension. It appears there was a conflict between the two entities sharing the same name beginning with iOS 17.2; this was not an issue prior to that.
Thank you for contributing to this thread!
I saw in another thread that you were having issues with writing to UserDefaults from the Device Activity Monitor extension. I will check if I can reproduce the issue on my end. Have you filed a bug report with Apple regarding this? If so, could you please provide the report identifier (FBXXXXXXXX) so I can include it in my report?
Already did a few months ago > FB13548526. Can you please make this happen before iOS 18 public release? 🤞
No updates yet. I reproduced the issue on my device and attached a sysdiagnose to my bug report (FB14111223). Hopefully, this helps Apple's investigation...
Here are my bug reports. One was filed over a year ago but I never got an answer.
FB13551195 (includes a sysdiagnose with a precise timestamp of when the issue occurred)
FB12270644
It works like a charm, thank you! Have you noticed any side effects from using this method so far?