Hey I'm experiencing the exact same thing, didReceiveRemoteNotification is never called on a iOS 16.2 Simulators despite all the Notification methods being called. Same code (and notifications) work flawlessly on device. So close yet so far... ;)
Sanvean
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
We just ran into the same issue pushing out our iOS15 update release. After 2 failed reviews (both using the same Apple ID for review) we responded referencing the error messages above as well as the fact that real user App Store logins were all operating normally atm as were any Apple IDs our development team had access to.
Before raising we a TSI we asked if it would be possible for the reviewer to attempt to login with a different Apple ID to isolate the account as the issue as the cause rather than our app and to our surprise (!) they did and subsequently approved the update.
So if you are confident in your Apple ID implementation (as we were) perhaps try this approach before have to waste a TSI on this issue.
Hi,We're seeing the exact same issue with some of our app's users using legacy .mac email addresses. Is there any update on this issue?Thanks
Hi Hoydor,Did you have any further luck on this? Or have you been restricted to testing with real live apple ids? Personally I've tried creating test users in App Store Connect but seem unable to sign in to devices using these sandbox Apple IDs to allow testing with Sign In With Apple.Is this a known limitation to developing and testing with Sign In With Apple at present?Thanks