Hello, I have an iOS app with a lot of embedded frameworks. It works well when I start it from Xcode, it works well once it is on the AppStore or in TestFlight. My only problem is when uploading it using Xcode 13. At the "Processing symbols for ....framework" stage, when reaching a specific framework, it keeps going forever (I've tried letting it run for a night, and it did not move). I can upload with Xcode 12 without problems, but not with any version of Xcode 13 or 14. Since it keeps going forever, I do not have an error message that could help me in identifying the issue. The issue seems to be with a specific framework, but I cannot identify anything that this framework has that is different from the other frameworks (they've all been compiled from C code, using a Makefile and the same CFLAGS and LDFLAGS options). I couldn't find any similar issues on the forum. Do any of you guys have a suggestion on how to fix the issue?

I have a Mac mini (A1347 MD387LL/A) that because of its age is limited to MacOS Catalina. Because of this, it’s limited to running Xcode 12, which is incapable of supporting iOS 15.5, and the App Store now requires that all apps be signed for iOS 15.5. I also have a 2020 iPad Pro, with the latest version of Swift Playgrounds, and it is perfectly capable of submitting apps to the App Store. Is there any way to convert a project created on my Mac to one that can be opened on the iPad version of Swift Playgrounds? Are there any other alternatives that could possibly work? I can’t afford to buy a new Mac at this time. Any suggestions would be greatly appreciated. Whatever solution I use will only be temporary. I plan to buy a new MacBook Air with my tax refund next year.

Hello apple, hello creative developers, I will present an idea for AirDrop, which I hope will be liked! It's about having a bridge between transfers thanks to apple devices, which could strengthen the brand's ecosystem. In this suggestion during a transfer between two devices, I see the Apple Watch as a bridge that can view and then accept or refuse a file transfer between two iPhones. And we could generalize this "bridge" system to other devices... For example, when transferring a file from an apple device to another apple device (excluding iPhone), the iPhone could make this bridge between both devices (always allowing you to view and then accept or refuse the transfer). The examples of different bridges are numerous but I think you have understood! For the good realization of this project I hope one day that AirDrop will be more open and will allow retouching by developers :) But also that AirDrop will be able to detect sleeping devices, or at least that "bridge" devices that have come out of sleep are detectable, and allow the transfer to the sleeping device... I know it's a lot of assumptions and suggestions but I find this system quite relevant. I'm waiting for your feedback, what do you think? Will we one day be able to see such a system arrive in the Apple ecosystem? Thanks for reading, have a nice day, Mikael. PS: sorry I am using google trad for this post, my knowledge in english is pretty low 😅

There is currently no way to "Bring your driver to iPad with DriverKit" because it's impossible to develop a driver because developers can neither deploy to the device nor run there because there is no way to procure development provisioning profiles with the required entitlements for actual hardware (USB, PCI). I bought an M1 iPad just to test this alleged new capability and the only thing it's good for so far is theoretically transferring files quickly or attaching some kind of ethernet dongle. My 1 month no-questions-asked returns window is going to close soon! FB10152280 FB10244398 FB10244627 FB10160665 FB10152361 FB10160793 FB10152210 FB10160567 FB10244046 FB10427776

Is Apple Provide “Vibrate when call is received” feature in ios16?

App opens, then closes a few seconds later. Sometimes allows login screen, but immediately closes if the button is pushed.

Hello, Does anyone know, how to programmatically detect top window in multi-window app on iPad? Especially in new overlapping window/Stage Manager environment?

I was wondering if it is possible to use the bluetooth API on iPadOS to let an app become an emulated "bluetooth speaker/car". I want to make an app where an iPhone or Android phone can connect to it via bluetooth so the app can play the audio from the phone, and receive and handle calls just like a car can play audio and handle calls and display call information via bluetooth. I would also like to know if the app could also get contact information from the phone over bluetooth. If it is possible to do so, how? I would love a friendly nudge in the right direction :)

Hey everyone! I'm taking a look at all the new APIs and I'd really love to implement some forms in my app in a new window instead of in a sheet as I'm currently making them. Basically I have a couple of forms that gather data from the user and add new stuff to the database. I initially did this by using the new Window API and dismissing it via the dismiss action in the environment once the user clicks "Add", but when I try to create a new Window it seems like the view keeps its state and doesn't really gets re-created, which means that all the forms contain the previous values that I don't need anymore. Is there any nice way to achieve this? I think that I can make this work by making it a WindowGroup and using the openWindow function that accepts a value and passing a new UUID every time, but I don't think this is a good idea since as mentioned on the talk these values get persisted.

Our device continuously sends images to the iPad. However, images are choppy because wifi power management is enabled on the iPad. I saw the same inquiry on another forum. However, it appears that no solution has been reached. How do I disable wifi power management? There is another problem. This has been an issue since iPad OS 15 came out. Whenever you make a Wi-Fi connection after a period of time, iPad drops the Wi-Fi connection. Once our device is disconnected, the safety system works and the connection cannot be restored. If you know how to solve this problem, please let me know.

Hello, On the recent iOS / iPadOS 16, SwiftUI 4, and Xcode Version 14.0 beta (14A5228q), my app contains a NavigationStack within the content view; and the stack contains a ForEach that iterates over a list of fruits / items. The form loop outputs a navigation link, the label being a view, and the destination being another NavigationStack. And whenever I go to click on that link, the app shoots me back to the root view instantly. This seems to happen whenever I have any kind of content in the StackNavigation that's within the NavigationLink. I will post the code snippets below, along with a GIF showing the bug in action. ContentView.Swift: struct ContentView: View {     @State private var isShowingSettings: Bool = false     var fruits: [Fruit] = fruitsData     var body: some View {         NavigationStack {             List(fruits.shuffled()) { fruit in                 NavigationLink(destination: FruitDetailView(fruit: fruit)) {                     FruitRowView(fruit: fruit) .padding(.vertical, 4)                 }             }             .navigationBarTitle("Fruits")             .toolbar {                 ToolbarItem(placement: .navigationBarTrailing) {                     Button(action: {                         isShowingSettings = true                     }) {                         Image(systemName: "slider.horizontal.3")                     }                     .sheet(isPresented: $isShowingSettings) {                         SettingsView()                     }                 }             }         }     } } FruitDetailView.Swift: // Code is shortened, but has the same bug as the actual code struct FruitDetailView: View {     var fruit: Fruit     var body: some View {         NavigationStack {             ScrollView(.vertical, showsIndicators: false) { Text(fruit.name)             }             .edgesIgnoringSafeArea(.top)         }     } Preview:

There is no documentation for running, debugging and testing system extensions on iPadOS16. The WWDC 2022 session "Bring your driver to iPad with DriverKit" does not count because (as of beta 2) it is completely unreproducible. This document tells us that to test our system extensions we must disable SIP so it's clearly only for macOS: https://developer.apple.com/documentation/driverkit/debugging_and_testing_system_extensions It would be nice if this document were updated with reproducible instructions for testing system extensions on iPadOS! FB10427776

In iPadOS, I'm building a tree on the screen using CALayer subclasses. Touching a visible node on the screen selects the node using CALayer.hitTest(CGPoint). This works reliably when I arrange the layers like this: But when I rearrange the same CALayer objects to look like this, after an unpredictable number of touches on the a*b composite structure, the app dies with EXC_BAD_ACCESS: Here is my code at the point of death. The LOOK HERE print statement just before invoking hitTest verifies that both layer and ksCGPoint have reasonable values. Here is the stack trace: Here is where the code actually dies in computeZ, which is called by CALayer.hitTest, which is invoked by VNode.touchesBegan, where VNode is a subclass of UIView. Does anyone know what's going on here, or how to fix it?

Usually, when I display a UITableView (UITableViewStyleGrouped) somewhere, there's a nice strip of gray padding at the top, above the first cell in the first section. But, when displayed in a popover on an iPad, the same UITableView appears with the first cell aligned to the top edge, i.e., you can't see any gray padding. If you drag the UITableView down with your finger, you can see that the padding exists, but as soon as you let go, the UITableView snaps back so that the top cell is aligned with the top edge. Curiously, if the top section has a header string, the UITableView behaves as you would expect. Any thoughts are appreciated!

I need to detect right-clicks / two-finger clicks with a trackpad or mouse on an iPad inside an action extension. I am finding that if I put a UITapGestureRecognizer in a view controller inside an action extension and set its allowedTouchTypes to UITouch.TouchType.indirectPointer, the gesture recognizer does not fire and none of the UIGestureRecognizerDelegate methods are ever called. The same code inside a standalone app works, just not in an action extension. This happens on both iPadOS 15.5 and iPadOS 16. I can filed FB10296917 regarding this, but it seems odd enough that I wanted to ask here whether I might be missing something.

Is it possible to turn on Stage Manager on Xcode's iPadOS simulator?

Hi! Is it possible to set different Display Scaling using the Xcode 14.0 simulator for iPadOS devices? Thanks!

is there a way let develop know an m1 pad has connected an external display？ if this pad is not in mirror-display mode, can I show two different window from one app in two screens?

Xcode 14.0 beta (14A5228q) refuses to build a DriverKit extension's installer app unless the dext's bundleID a single . suffix added to the bundling app's bundle ID. The error is error build: Embedded binary's bundle identifier is not prefixed with the parent app's bundle identifier. Is this behaviour intentional? Maybe it makes sense for non-driverkit bundled things, but it breaks existing software, invalidates existing dext bundle IDs and leads to awkward bundleIDs like com.foo.installer.mydriver.

Is it possible for an ipadOS app running in the background to receive the key down/up event from an external keyboard?