Thank you so much for this!!!

Thank you so much!!!! I spent hours trying to find this and the my other question. Even used AI (boy did it send me down the wrong path) with no luck. Thanks again!!!

OK thank you!! I was able to test with 15.1 via Test Flight and it worked! (That is, no alert). I can live with development issue by using a team identifier for my dev builds. And group ID is registered, Thanks again! //Ray

So I am still struggling with this issue. My issue is slightly different than most people in that I am not as much worried about Mac/iOS interoperability but just that when a user launches the next version of my app, they don't get the alert to allow the app to have access to the data. My shipping Mac app stores it's data in an app group so that my internal extensions can also access the same data. This app group is named group... This has been done for years and works great. It also works fine on Sequoia (for currently shipping version). However, when I build the app with Xcode 16, I am now getting the alert. The alert happens even before my app delegate is loaded so it appears by just having the app group listed in my entitlements (or info.plist) is causing the alert. Therefore, even if I wanted to migrate the user's data to a new location, they would still get the alert until all users migrated and I could do a new release removing the entitlement. To be clear, on Sequoia 15.0.1 and using released Xcode 16, I am still getting this alert when building for the App Store (Test Flight) or direct distribution. @colink, it sounds like you might have solved this for Test Flight builds but unclear what you did to do this. Any help on this would be greatly appreciated!!! //Ray

I am having this issue as well. Has been working for years (background notifications) but in last few months or so has stopped working. I am also getting the same errors in the Console.

+1. I've been trying for a week and I just get the glitch message.

Thank you! I totally missed that.

Sorry, I guess I was just too impatient. After about 6 hours, the notarized build finally came through. //Ray

So I somewhat have figured out my situation. In the new release, I added keychain sharing and added a new identifier in the Keychain Groups in the Keychain Sharing entitlements. This appears to remove access from the keychain item that was stored using my bundle ID. According to the documentation, it says that using keychain sharing would still allow access to my private keychain. However, if I don't put my app's bundle ID in the Keychain Groups entitlement, the app can't see it. Since the apps that I need to share the keychain with are just smaller apps within my bundle and only need access to one keychain item, I think the solution is to just have my bundle ID in Keychain Groups and use that as the shared ID. I do want the upgraded app and it's new components to have access to the previously stored keychain item as well.

Thanks Eskimo! For anyone hitting this issue, Eskimo discovered that this is a bug with TestFlight for Mac. I've filed a bug report on this (FB9836675). He also suggested to use iOS style keychains to work around the issue.