Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for

Since we started building our application on Tahoe, all NSPopupButtons in the UI stop truncating when the window they're in is moved to a different screen. Even though their frame is correct, if the selected item string is longer than what can fit, they just draw outside of their bounds, overlapping other neighbouring controls. This is reproducible only in our app target even though they are not subclassed or overridden in any way. The same window copied to a test app doesn't have the issue. Initially good After dragging to another screen Frame is correct in the View Hierarchy debugger, but the contents are incorrect. Very simple constraint setup, with content compression resistance set lower to allow resizing below the intrinsic content size. This is what happens on this simple test window. The rest of the popups in more complex windows are all bad right away, without requiring you to move them to a different screen. When built on Sequoia, all is well regardless of which OS the app is run o

Environment: macOS 26.2 (Tahoe) Xcode 16.3 Apple Silicon (M4) Sandboxed Mac App Store app Description: Repeated use of VNRecognizeTextRequest causes permanent memory growth in the host process. The physical footprint increases by approximately 3-15 MB per OCR call and never returns to baseline, even after all references to the request, handler, observations, and image are released. ` private func selectAndProcessImage() { let panel = NSOpenPanel() panel.allowedContentTypes = [.image] panel.allowsMultipleSelection = false panel.canChooseDirectories = false panel.message = Select an image for OCR processing guard panel.runModal() == .OK, let url = panel.url else { return } selectedImageURL = url isProcessing = true recognizedText = Processing... // Run OCR on a background thread to keep UI responsive let workItem = DispatchWorkItem { let result = performOCR(on: url) DispatchQueue.main.async { recognizedText = result isProcessing = false } } DispatchQueue.global(qos: .userInitiated).async(execute: workItem) } pr

So i and many other big youtubers out there use iphones for intense gaming such as callcof duty and fortnite. However apple never listens especially to those of us that have been your guys's clients since the early 2000's. Users have different guinsetups for their games and a lot of the time when in an intense conpetition and the the low battery animation pops up it blocks our screens and that 3 to 4 seconds it takes to disappear makes us lose a game. Apple needs to implement a feature that allows us to toggle the notification even if our phone dies or a more efficient route would be allow us to toggle or set it by default to show that your battery is low on the top of the screen where the black line expands when you start charging your phone so it doesn't affect my gameplay whatsoever. This is a crucial thing apple needs to do, many people won't report it because apple never listens. Another great feature would be if apple could make a charging port on the side for claw players.

Hi, I’m trying to understand the correct process for Apple Developer Program organization enrollment when identity verification cannot be completed due to an outdated passport photo. Based on our last communication, I believe the enrollment was paused/declined because my passport photo didn’t match my current appearance (I’m assuming this because the last communication we had was specifically about my passport photo). I have since obtained a new passport with an updated photo. Timeline for context: • Jan 9: My enrollment was put on hold / could not proceed after ID verification. • Jan 12: I applied for a new passport with an updated photo. • After receiving the new passport, I followed up to provide the updated ID, but I’m not sure what the correct next step is in the enrollment workflow. Could you please advise the recommended way to proceed? • Should I submit a new organization enrollment, or can the existing one be re-opened/continued? I couldn’t find a way to resubmit/continue the existing enrollment from

Summary: We are facing a serious issue on iPhone where multiple passkey authentication problems occur when accessing passkey-enabled login pages via shortcuts placed on the iPhone Home Screen. These issues may also occur when opening the same pages directly in a standard browser window. However, launching the login pages from a Home Screen shortcut appears to increase the likelihood of encountering these issues. Affected Services (examples, not exhaustive): Amazon GitHub Adobe Observed Issues: Issue 1: A passkey authentication dialog/popup shows two times without any user operation: What happens due to this issue: Login does not complete after the first passkey authentication. A second passkey authentication UI automatically appears. Completing or canceling the second authentication allows the login to proceed. Issue 2: Login remains stuck until the user manually invokes passkey again What happens due to this issue: The login page does not advance after the first authentication. The user must tap the ID/usern