Hello everyone We are preparing an update to our app and I have questions regarding Sign-In With Apple. In older versions of our app we allowed users to sign up to our service with their LinkedIn or Xing account while also offering our own sign-up that doesn't require any socials. We can remotely control our Onboarding flow, so we have disabled creating new accounts with either of the two options (Xing was removed a while ago after they ceased offering their public API). What I was wondering now is that if we have to offer Sign-In With Apple if the branch of our Onboarding for existing users still offers the options to log in using Xing and or Linkedin (Xing resets the password and changes their profile from a Xing one to one of ours, we are thinking of doing the same for LinkedIn). If that is the case that would involve a lot of work for us, and in the current situation we are a bit strained in regards to resources, as well as the situation that I'll be leaving the company at the end of November. I hope some of you have either had experiences with the same kind of offering, or if someone from Apple could give an answer here. Also, as an off question.. Sign in With Apple is an iOS 13 feature, so how should this be done on earlier versions of iOS? Would it be OK to not offer it there?

Hello! Encountered a potential bug in iOS 14 but wanted to cross-check here before creating a feedback on Feedback Assistant. I have a mixed ObjC/Swift project, with the majority of ViewControllers currently written in ObjC. There are a few extensions/categories in Swift/ObjC that add convenience methods to various UI elements, such as UIButton. One such extension on UIButton looks like this: extension UIButton {     @objc func setTitle(_ title: String?) {         self.setTitle(title, for: .normal)         self.setTitle(title, for: .highlighted)         self.setTitle(title, for: .selected)     } } Now, I'm not sure if this somehow shadows a (upcoming?) method on UIButton, but this worked on iOS 13. Calling this method, both from Swift or Objective-C, however does not set the title on iOS 14. It stays blank/on the default. If I set a breakpoint inside that setTitle() method, it won't get hit either. Removing the @objc from the method seems to fix the issue (for Swift-based VCs), but makes it impossible to call from Objective-C. Moving the @objc to the top of the extension doesn't help either. Is this a regression, or am I missing something? Would appreciate everyone's advice here. If it is a bug I will of course file a feedback on Feedback Assistant and link it here.

HelloCurrently, when checking reviews of our app (and others, in general) the App Store shows old (or oldest) reviews first.This sometimes happened on the old App Store too, but with the new App Store and the more prominent reviews, this seems like a regression and could cause harm to apps that, maybe due to an earlier, but by now old update, got bad reviews that have been addressed in new updates.Is this a bug or is this expected behavior for the App Store?