User Profile

We develop SDKs that are distributed as XCFramework to our clients. We seek clarification regarding the necessity of attaching a Privacy Manifest, especially in instances where our SDK does not interact with data that would typically be covered under such a manifest. Additionally, in the scenario where our SDK's primary function is the transmission and reception of data, which may potentially include personal data, are we required to declare in the Privacy Manifest that we handle personal information? This query persists even when all personal data processing is executed on the server side. From our current understanding, based on the information available at https://developer.apple.com/support/third-party-SDK-requirements/, it appears that SDKs are only obligated to have a signature, and incorporating a Privacy Manifest may not be compulsory. We would appreciate further insight or confirmation on this matter.

I am experiencing an issue with the search functionality in Xcode 15 RC's editor. Specifically, I am unable to search for Japanese characters (Kanji, Hiragana, and Katakana) using the Command+F search bar. Steps to Reproduce: Open any project in Xcode 15 RC. Open a file that contains Japanese characters. Press Command+F to bring up the search bar. Attempt to input Japanese characters into the search field. Example: Problematic Input and Output: nyuuryoku → にゅうryおkう Expected Input and Output: nyuuryoku → にゅうりょく Expected Behavior: The search bar should allow for the input of Japanese characters, and the search should return appropriate results. Actual Behavior: I am unable to input Japanese characters correctly into the search bar, making it impossible to search for lines of code or comments written in Japanese. System Information: macOS version: [Your macOS version] Xcode version: 15.0 Keyboard input source: Japanese I hope this issue will be addressed soon, as it significantly hampers the workflow for developers who work with Japanese text.

The following code works fine on iOS 12, but on iOS 13.4.1, the variable is freed and It will crash."The behavior of NSLayoutConstraint.deactivate has been changed. Is it?Remove weak or NSLayoutConstraint.deactivate, the problem is gone. Which is appropriate in this case?class ViewController: UIViewController { @IBOutlet private weak var constraint: NSLayoutConstraint! override func viewDidLoad() { NSLayoutConstraint.deactivate([constraint]) constraint.constant = 100 NSLayoutConstraint.activate([constraint]) } }