Thanks for your response Kmart! While profiling the extension in Xcode, it maxes out at around 10MB on my device. I've also ensured that I'm looking at the extension target and not the host app. Could the memory usage vary that widely on other users devices that it could exceed 100MB while my device maxes out at 10? Or might there be something else going on?

Thanks for the response! A few questions: 1. Is there an estimated release date for the iOS version when this should be fixed? 2. By "deauthorize and re-authorize" the app, I assume you mean have the user revoke Screen Time access in the app's settings. This worked for some users, but did not work on my device (which is developer enabled). Is this a sure fix? 3. Since revoking Screen Time access is supposed to fix this, should this be a problem for new users?

There are other apps that use DeviceActivityReport that are never laggy, like Jomo for instance. I wonder if there is some general performance guidance on how to leverage DeviceActivityReport's implementation and fit its use into an app with best possible performance?

Thanks for the response! I'm not familiar with that rule or what it means - could you link to any documentation?

Thanks for your response! It helps a lot but still is not ideal. I made a reply to this post with my further struggles and code examples (since the comment only allowed me so many characters). Would love to hear any additional thoughts you have!

I've experienced the same thing consistently in my application. @foijodsf let me know if you've filed the bug and please link it here! It seems like there are apps that have been able to get around the lag (like Jomo for example, which never lags at all) - so there seems to be an existing way to anticipate the lag and re-render Scene. Kmart, could you shed any light on how to get around the frequent lag of DeviceActivityReport?