Search results for

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

186,331 results found

Post

Replies

Boosts

Views

Activity

Will resubmitting my app send it to the back of the line?
Hi everyone - My first iOS app submission has been in Waiting for Review since Jan 27 (we actually submitted Jan 23, saw no movement, and resubmitted with a small update), and Apple Support has not responded to my outreach. Since Jan 27, our team has implemented a handful of app updates from our roadmap and plans to submit the updated version of the app once the first submission is approved. However, we're at a crossroads: Do we wait for the first submission (currently 14 days and counting) and submit the updated version once (hopefully) approved, rolling the dice that an update to an existing app would see a faster 2-3 day turnaround? Cancel our current version and resubmit the updated one, with the risk that we're just moving ourselves to the back of the queue and get stuck in another 15-20 day Waiting for Review status? Any devs with insight or experience navigating these choices, any suggestions would be greatly appreciated.
2
0
149
1w
MacOS(Apple Silicon) IOKit driver for FPGA DMA transmission, kernel panic.
MacOS(Apple Silicon) IOKit driver for FPGA DMA transmission, kernel panic. Hardware and software configuration: MAC mini M1 2020 16GB, macOS Ventura 13.0 or 13.7.8 FPGA device capability: 64-bit Complete description: We've developed a DMA driver for PCIe devices (FPGA) based on IOKit. The driver can start normally through kextload, and the bar mapping, DMA registers, etc. are all correct. I am testing DMA data transmission, but a kernel panic has occurred. The specific content of the panic is as follows: {bug_type:210,timestamp:2026-01-28 14:35:30.00 +0800,os_version:macOS 13.0 (22A380),roots_installed:0,incident_id:61C9B820-8D1B-4E75-A4EB-10DC2558FA75} { build : macOS 13.0 (22A380), product : Macmini9,1, socId : 0x00008103, kernel : Darwin Kernel Version 22.1.0: Sun Oct 9 20:14:30 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T8103, incident : 61C9B820-8D1B-4E75-A4EB-10DC2558FA75, crashReporterKey : 6435F6BD-4138-412A-5142-83DD7E5B4F61, date : 2026-01-28 14:35:30.16 +0800, panicString : panic(cpu 0 c
9
0
303
1w
Minimum Functionality Rejection Blocks My App's Users
Parents often spend lots of time to search for kids' events and government programs. Even after they found ideal ones, they need lots of copy and paste to check Google Map in order to align with their time and location. My app is designed to solve this pain point. It will handle those time consuming web search and time & location matching. For good user experience, the UI is simple, it recommends nearest kids programs that aligns with parents' time. It also has a Map to show suggestions visually and provides map navigation. Parents are all very busy, the UI has to be simple and easy to use. This app can save parents 60% of time to find kids' programs. The v1.0.0 of this app got approved. It works well on Android phones all the time, but the map navigation didn't work on iOS. I later realized have to add LSApplicationQueriesSchemes to enable map navigation on iOS app. So I fixed this and tested the new build on iOS phones, the new build 1.0.1 works well. But App
1
0
46
1w
Reply to macOS to macOS SwiftData iCloud Sync Problems
I was able to get things syncing reliably between Macs today running internal TestFlight builds after adding CloudKit.Framework to the app target's Frameworks, Libraries, and Embedded Content section as described in this thread.. Once that was set, creating/editing a Project record would sync between the TestFlight apps. I then noticed that creating/editing a related TimeEntry record would cause syncing to completely stop in either direction. I then discovered that only my Project records type had been deployed to Development on the iCloud Console; while TimeEntry had not been deployed for some reason. I re-deployed schema changes from development to production on iCloud Console, and now Project and TimeEntry record types show in iCloud Console in production. Syncing now works for creating/editing/deleting Project and TimeEntry records. So all is syncing well in my Internal TestFlight builds now. Thank you, Ziqiao, for the links. I'm sure those would be helpful if
1w
UIToolbar Missing from View Hierarchy Since iOS 26
Since iOS 26, navigationController?.toolbar no longer appears in the view hierarchy, and UIToolbar itself is not visible in the view tree. Is there currently any supported way to access the toolbar’s container view or its underlying view hierarchy? However, the API itself is not deprecated. https://developer.apple.com/documentation/uikit/uinavigationcontroller/toolbar
Topic: UI Frameworks SubTopic: UIKit Tags:
1
0
51
1w
Reply to Xcode Simulator error
Thanks for this very interesting. I would check about the multiple returns the error is complaining about: NSMultipleUnderlyingErrorsKey=(n) I have 2 recommendations, first can you read this thread: https://developer.apple.com/forums/thread/815397?page=1#875810022 Second, I would like you to try to run this on the simulator to see if makes any difference. On the terminal: xcrun simctl status_bar clear I am sure you already went through the clearing and build and restarting the simulator. Open the Console app on your Mac and filter logs for your simulator. Look for any additional error messages or warnings that might provide more context about what's going wrong and post it here. Occasionally, beta versions of macOS and iOS/iPadOS simulators may contain bugs that have been fixed in later beta releases. So please provide me all the versions you are using. As a last resort, consider reinstalling Xcode and the simulators to ensure there aren’t any cor
1w
Xcode Simulator error
Following is an error I encounter when trying to run a foundation model function in simulator. Error Domain=FoundationModels.LanguageModelSession.GenerationError Code=-1 (null) UserInfo={NSMultipleUnderlyingErrorsKey=( Error Domain=ModelManagerServices.ModelManagerError Code=1026 (null) UserInfo={NSMultipleUnderlyingErrorsKey=(n)} )} Its a swift playground I'm building in xcode and works fine in the preview and on a real device too but since it's my submission for the swift student challenge I need it to run on the simulator. I have updated my macOS to latest version of Tahoe(26.3) and Xcode is also on latest version. The simulator I run the playground is also on ios and iPadOS 26. I have set my region to US and have turned on Apple Intelligence on my mac too. Any suggestions on how to fix the issue?👾
1
0
81
1w
UIApplication.canOpenURL not working without Safari
If I delete Safari and only have another browser installed on my device, UIApplication.shared.open does not work. I think this is a bug. Why would it not work? If Safari is not the main browser, UIApplication would open the URL in my main browser. Those are valid use cases. I would expect this API to work with any browser... iOS 26.2 iPhone 14 Pro guard let url = URL(string: https://www.apple.com) else { return } if UIApplication.shared.canOpenURL(url) { UIApplication.shared.open(url) } else { print(Could not open URL) }
Topic: UI Frameworks SubTopic: UIKit
11
0
273
1w
SwiftUI .toolbar(placement: .keyboard) item not exposed to accessibility on iOS 26.1 (affects VoiceOver + XCUITest)
Description On iOS 26.1, a ToolbarItem placed in .keyboard is no longer exposed to the accessibility hierarchy. As a result: VoiceOver cannot focus or activate the toolbar button XCUITest cannot discover the element, making the UI impossible to test TextEditor() .toolbar { ToolbarItem(placement: .keyboard) { Button(Done) { /* action */ } } } This worked correctly on previous iOS versions. The button appears visually but is missing from both VoiceOver navigation and XCUI accessibility queries. Steps to Reproduce Create a new SwiftUI project. Use a simple text field with a keyboard toolbar button. Run on an iOS 26.1 device or simulator. Focus the text field to show the keyboard. Turn on VoiceOver and attempt to navigate to the toolbar button. Run an XCUITest attempting to locate the button
2
0
172
1w
Live Q&A Summary - SwiftUI foundations: Build great apps with SwiftUI
Here’s a recap of the Live Q&A for SwiftUI foundations: Build great apps with SwiftUI. If you participated and asked questions, thank you for coming and participating! If you weren’t able to join us live we hope this recap is useful Where can I watch the VOD? Is the sample code “Wishlist” that was shown available for download? You can view the replay of the entire event here https://www.youtube.com/watch?v=Z3vloOtZLkQ The sample code for the Wishlist app will be made available in the coming weeks on the Apple Developer website, we'll send an update via email when it is available. What are the best practices when it comes to building complex navigations in SwiftUI? The developer website has documentation on navigation style best practices. Explore navigation basics like NavigationStack and TabView to get a ground-up understanding. For documentation on navigation APIs see Navigation. How can I integrate UIKit with my SwiftUI app? What about adding SwiftUI into my UIKit app? See UIKit integ
Topic: UI Frameworks SubTopic: SwiftUI
1
0
39
1w
Local Network permission on macOS 15 macOS 26: multicast behaves inconsistently and regularly drops
Problem description Since macOS Sequoia, our users have experienced issues with multicast traffic in our macOS app. Regularly, the app starts but cannot receive multicast, or multicast eventually stops mid-execution. The app sometimes asks again for Local Network permission, while it was already allowed so. Several versions of our app on a single machine are sometimes (but not always) shown as different instances in the System Settings > Privacy & Security > Local Network list. And when several instances are shown in that list, disabling one disables all of them, but it does not actually forbids the app from receiving multicast traffic. All of those issues are experienced by an increasing number of users after they update their system from macOS 14 to macOS 15 or 26, and many of them have reported networking issues during production-critical moments. We haven't been able to find the root cause of those issues, so we built a simple test app, called FM Mac App Test, that can reproduce multica
14
0
530
1w