{"id":44819,"date":"2024-09-11T16:05:02","date_gmt":"2024-09-11T20:05:02","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=44819"},"modified":"2025-10-11T12:17:41","modified_gmt":"2025-10-11T16:17:41","slug":"group-container-names-in-sequoia","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2024\/09\/11\/group-container-names-in-sequoia\/","title":{"rendered":"Group Container Names in Sequoia"},"content":{"rendered":"

John Brayton<\/a>:<\/p>\n

On both macOS and iOS, sandboxed apps use group container folders to share data between the main app and extensions, such as the Subscribe in Unread<\/i> share extension and Unread’s widgets.<\/p>

[…]<\/p>

On beta releases of Sequoia (macOS 15) using the “group.” prefix results in the customer getting an alert with this text at every launch:<\/p>

“Unread.app” would like to access data from other apps.<\/p>

Keeping app data separate makes it easier to manage your privacy and security.<\/p><\/blockquote>

I fixed this by changing the group container identifier.<\/p><\/blockquote>\n\n

Martin Höller<\/a>:<\/p>\n

\n

I don’t like [how] Sequoia restricts how shared group containers can be named. So far I used “group.com.bluebanana-software.iyf”, which leads to a permission dialog each time the app is started. Now it needs to be “<TeamID>. com.bluebanana-software.iyf”.<\/p>\n

To migrate to the new container, the user needs to actively give permission to access the old file as now it is outside of the app’s sandbox.<\/p>\n<\/blockquote>\n\n

Adam Overholtzer<\/a>:<\/p>\n

\n

Thankfully it only seems to impact “native” Mac apps built for Sequoia. Existing apps and Catalyst apps (mine anyway, knock on wood) don’t seem to show the popup.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n