Last but not least, we've yet to see the long been waiting feature of notification making it's appearance on bookmarks on Safari even on IOS 16.4 unlike other browsers like Edge so this may be another issue for investigation.

P.S: This doesn't happen with IOS dev provision but with App Store distribution that I need.

I am still getting this error despite being approved for family control. Anyone know what to do?

Worked! Thank you so much @kmart! Is is in anyway possible to do the same with websites? Aka hide instagram.com bookmark from the homescreen.

Appreciate the reply. @bweinstein. We've already issued couple months ago FB10020986. By removing the captivating, we make social media less addictive so that people can still stay connected, not distracted. In other words, joining Apple's mission to improve focus/screentime. You can check out our safari extension at: Mac Store. Our users are pleading us every day to extend our solution to mobile as that's where majority of social media distraction lies. As we can't modify a native app, the closest thing we can do is ask users to add the modified safari social media page to their homescreen which they're completely value as it still makes them still feel they're using the native app without the distraction. However, since safari extensions lose connection at standalone despite our users' intention, they can no longer live a life without distraction. As a result, we are forced to ask the user to also allow content blockers as a workaround which makes for a poor user experience for the following reasons.  The User is confused about why he has to install two extensions to do the job of one, hence creating a logical leap. Content ways are turned on in a completely different way than Safari Extension, the former is in iPhone’s setting the latter is in the Safari toolbar. Thereby, such poor user experience leaves the user frustrated given the simplicity a user expects from Apple’s product. Because the user has to install two Extensions to do the job of one, this can negatively impact the battery and performance of the user’s phone. As the name implies, content blockers only block content. Hence, we can't developer any feature aside blocking that users want. Even worse, content blockers are inefficient for blocking due to the fact that some HTML elements don’t have unique identifiers while others share IDs due to being SWA (making it impossible to make targeted blocking always work).