Search results for

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

186,345 results found

Post

Replies

Boosts

Views

Activity

Reply to Content Filter Permission Prompt Not Appearing in TestFlight
I’m glad to hear that you’re making progress. [quote='875219022, lilan, /thread/773414?answerId=875219022#875219022, /profile/lilan'] We still have to do a submission for NEURLFilter right? [/quote] Yes. Specifically, there’s a process for onboarding with the Oblivious HTTP relay. You can find a link to the submission form at the bottom of How to onboard with an Oblivious HTTP relay hosted by Apple. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
2w
App approved but still showing “In Review”
Hello, My app (App ID: 1616628950) was recently reviewed, and I received an email stating that the submission review was completed and that the build is eligible for distribution. In App Store Connect, In App review - IOS submission, the build shows Approved. However, when returning to the main Distribution page, the app version is still displayed as In Review, and I do not yet see a “Ready for Distribution” or release option. In previous submissions, once review was completed, the status usually transitioned to “Ready for Distribution” or “Pending Developer Release” fairly quickly, so this behavior seems unusual. I have tried refreshing the page and logging out/in, but the status has not changed so far. I just wanted to ask if this is a known synchronization delay between App Review and Distribution, or if there is anything else I should check on my side. Thank you very much for your time and assistance.
2
0
135
2w
Reply to Notarization submissions stuck in “In Progress” for >24 hours (CI / REST API) – production impact
I have a standard spiel about this which I’ve included at the end of this reply. Please read it through first. With that in mind, let’s come back to your specific questions: [quote='814841021, Jackson_Hsieh, /thread/814841, /profile/Jackson_Hsieh'] Is it expected behavior for notarization submissions to remain in “In Progress” for such a long period without logs? [/quote] Yes, assuming you’ve hit the “in-depth analysis” path. [quote='814841021, Jackson_Hsieh, /thread/814841, /profile/Jackson_Hsieh'] Is client-side timeout and re-submission the recommended handling for CI workflows? [/quote] I see two common patterns reported here on the forums: Developers hit this on their first notarisation attempt, or otherwise very early in their Mac development ‘journey’. Developers have been happily notarising for a while and then suddenly bump into this. In the first case my advice is to simply wait. That’s the focus of the boilerplate text that I included at the end of this reply. My understanding is that you fall into
2w
"Show on all spaces" toggles OFF after programmatically setting wallpaper via AppleScript
I'm building an automated wallpaper updater that fetches images from an API and sets them as desktop wallpaper on macOS Tahoe. The automation uses AppleScript combined with database manipulation to ensure wallpaper applies to all spaces. Current implementation (via Apple Shortcuts): wallpaper_path=$1 osascript -e tell application System Events to tell every desktop to set picture to POSIX file $wallpaper_path sqlite3 ~/Library/Application Support/Dock/desktoppicture.db UPDATE data SET space=NULL WHERE space IS NOT NULL; 2>/dev/null killall -HUP Dock Issue First run: Works perfectly - sets wallpaper on all spaces/desktops, Show on all spaces is ON After first run: Show on all spaces automatically toggles OFF in System Settings Second run onwards: New wallpaper only updates on the active space, inactive spaces show old wallpaper Expected: Show on all spaces should remain ON after programmatic wallpaper changes Actual: System Settings automatically disables it, breaking subsequent updates Tested work
0
0
117
2w
Abnormal Background Delivery Frequency of HealthKit on Specific watchOS Devices
1/ Issue Summary In our application, we use HKObserverQuery together with:HKHealthStore.enableBackgroundDelivery(for:frequency: .immediate) to enable HealthKit Background Delivery, allowing the system to wake our App Extension in the background to process health data updates. Under the same app build, identical HealthKit permission configuration, and the same watchOS version, we have observed significant differences in background delivery frequency across different devices. Specifically, on certain devices (e.g. Apple Watch Series 10, watchOS 26.2.1), the background delivery frequency is significantly reduced, behaving as if it is capped at approximately once per hour. On other control devices, under the same configuration, background delivery is triggered much more frequently and consistently, at approximately every 8–16 minutes. This behavior is consistently reproducible on the affected devices. **We would like to understand whether there are any officially recommended implementation patterns, best
1
0
167
2w
Reply to All notarization submissions stuck "In Progress" for 24+ hours — first-time Electron app
You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Code Signing SubTopic: Notarization Tags:
2w
Reply to UITab memory leak
Moff, I confirm that on my side the unreleased reference also comes from _UIFloatingTabBarItemView. Richard, as to why my hack didn't work for Moff, it is definitely related to the version of iPadOS. iPadOS 18.7.1 (physical iPad): there is an additional unreleased reference to the tab bar view controller from a _UIFloatingTabBarItemCell. However my hack works. iPadOS 26.2 (simulator): there's only one reference from a _UIFloatingTabBarItemView, exactly as you described (same memory graph as yours). And indeed my hack doesn't work I hope the issue will be fixed for both versions of iPadOS. Please keep us posted here.
Topic: UI Frameworks SubTopic: UIKit
2w
Reply to URGENT: Multiple Notarization Submissions Stuck "In Progress" 5+ Days - Blocking Release
You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
2w
iOS 26.0+: sceneDidBecomeActive / applicationDidBecomeActive fires during Lock button press while app is active
Hi all, I’m seeing a lifecycle behavior change on iOS 26.0 (and up). While my app is in the foreground and active, pressing the hardware Lock button triggers didBecomeActive callbacks/notifications even though the app is transitioning away from active state. I’m observing this sequence: willResignActive didBecomeActive willResignActive didEnterBackground This happens for: • UISceneDelegate.sceneDidBecomeActive(:) • UIApplicationDelegate.applicationDidBecomeActive(:) • UIApplication.didBecomeActiveNotification On iOS 18 (same app, same code) I do not see didBecomeActive in the middle of locking/backgrounding. Problem is reproduced on totally new project. I would expect a normal transition to background: • willResignActive → didEnterBackground …and no extra didBecomeActive between them. I have “became active” logic (refresh UI/state, resume timers, analytics). On iOS 26.0 this logic runs unexpectedly during locking, causing unnecessary work and incorrect state transitions. Is this cal
Topic: UI Frameworks SubTopic: UIKit Tags:
1
0
182
2w
macOS 26.3 RC breaks all borderless window interactions
After updating to macOS 26.3 Release Candidate, all interactions for borderless windows are no longer working. In macOS 26.3 Beta, borderless windows behaved correctly: • Mouse clicks were received normally • Window dragging worked as expected • Interaction logic was fully functional However, in macOS 26.3 RC, all of the above behaviors are broken: • Click events are not delivered • Windows cannot be moved or interacted with • The issue affects all borderless windows This is a regression from the Beta build and appears to be system-level, not app-specific. Environment: • macOS: 26.3 RC • Window type: borderless / frameless windows • Status in 26.3 Beta: working correctly • Status in 26.3 RC: completely broken Could Apple confirm whether this is a known issue or an intentional behavior change in 26.3 RC? If this is a , is there a recommended workaround before the final release? Thanks.
Topic: UI Frameworks SubTopic: AppKit
2
0
155
2w
Lighting disabled inside PortalComponent in Progressive/Full Immersion (visionOS 26.2)
Hello, I am experiencing an issue where lighting is disabled within a Portal Component specifically when using Progressive or Full Immersion styles in visionOS 26.2. [Steps to Reproduce] Create a scene in Reality Composer Pro with custom lighting (Directional Light, IBL, etc.) and load it as an Entity. Add a PortalComponent to this Entity. Observe the Entity in an ImmersiveSpace under different Immersion Styles. [Observed Behavior] Mixed Immersion: Lighting works as expected.Progressive / Full Immersion: Lighting is disabled, causing the content to render incorrectly. [Additional Context] Without PortalComponent: The same Reality Composer Pro scene renders lighting correctly across all Immersion Styles (Mixed, Progressive, and Full).Regression: In applications built with Xcode 16.4 / visionOS 2.5, lighting inside the Portal functioned correctly. This issue appears to have emerged with Xcode 26.2 and visionOS 26.2. [Questions] Is the disabling of lighting inside Portals during Full/Progressive Immersi
1
0
447
2w
Reply to Swift Student Challenge
Hello @itsakhand18 and thank you @lijiaxu ! Your submission must be an app playground that's built with and runs on Swift Playground 4.6 or Xcode 26 or later. At the moment, app playgrounds do not support watchOS. I know you asked a while ago but with the challenge beginning so soon, I wanted to confirm. Good luck!  Travis Trotto - DTS Engineer
2w
Reply to How does Xcode26.3 Agent know about the API Documentation for non Apple Intelligence
XcodeRead - Read files from the project XcodeWrite - Write files to the project XcodeUpdate - Edit files with str_replace-style patches XcodeGlob - Find files by pattern XcodeGrep - Search file contents XcodeLS - List directory contents XcodeMakeDir - Create directories XcodeRM - Remove files XcodeMV - Move/rename files BuildProject - Build the Xcode project GetBuildLog - Get build output RunAllTests - Run all tests RunSomeTests - Run specific tests GetTestList - List available tests XcodeListNavigatorIssues - Get Xcode issues/errors XcodeRefreshCodeIssuesInFile - Get live diagnostics ExecuteSnippet - Run code in a REPL-like environment RenderPreview - Render SwiftUI previews as images DocumentationSearch - Search Apple docs and WWDC videos XcodeListWindows - List open Xcode windows The above is a list of MCPTools exposed by Xcode. Im am interested in the DocumentationSearch Tool . Here Xcode is able to search only Apple Docs. Lets say i am using a custom .xcframework or i have added HTML Do
2w