[quote='815593022, Nickkk, /thread/764435?answerId=815593022#815593022, /profile/Nickkk'] Today I too was contacted by a user who updated from macOS 13 to 14.7.1 and was quite desperate since my app couldn't resolve or create bookmarks anymore. Restarting the Mac didn't help. Thankfully you already reported the same issue so I suggested to update to 15.1.1, which finally solved the issue. [/quote] So far it only seems to happen for users that update from macOS 13. Very strange! I've received multiple confirmations that any of these solutions resolve the issue: Create a new user account (old account will stay bugged) Reset the macOS keychain for the (bugged) user account Update to 15.1+ Resetting the keychain is a bit technical and may cause data loss, so I recommend users to contact Apple Support for help with that.

Does anyone see the same problem on macOS 14.7.1? I've received multiple reports from users that macOS 14.7.1 cannot create new bookmarks or resolve existing bookmarks. Same error message: Error Domain=NSCocoaErrorDomain Code=256 "Failed to retrieve app-scope key" UserInfo={NSDebugDescription=Failed to retrieve app-scope key} All users updated from macOS 13.* Ventura to macOS 14.7.1 Sonoma, which triggered the issue Restarting Mac does not fix the issue Clearing all app data does not resolve the issue One user reported that using bookmarks on a new macOS user account works correctly. This leads me to believe that the macOS keychain for their user account is broken. See also https://developer.apple.com/forums/thread/46583 Does upgrading from macOS 13 to macOS 14.7.1 break the keychain?

Yes, it shows 5/20 on App Store Connect as that was the last time I've changed the pricing, that was displaying correctly. I've changed the tier initially on 5/16, then again on 5/18 (because nothing changed) and again on 5/20, because nothing changed still. Exact dates and changes are available in the ticket. My though process was that perhaps the change didn't come through correctly, because App Store Connect was having issues on 5/17. I've validated the pricing by checking: https://apps.apple.com/us/app/<app-id> On the Mac App Store itself Using SKProduct in the production app (SKProduct.price was simply the old tier) All three showed the old pricing tier for 7 days after initial change. I've checked again today 5/24 and now it is correct on all three channels. Seems like I should've had patience to wait one more day. I don't think it will be helpful to provide the data returned from SKProductsResponse now that the pricing is correct again, but just in case, what kind of data are you expecting? The fields returned in SKProduct? I assume these were all equal to how they are now, except for the price field.