Hello, I want to use universal links in my application, for which I need to get the TeamID and BundleId, for apple-app-site-association file. Can you please tell me, do I have to buy an Apple Developer Account at the time of development to do this, or can I get it all for free at the time of development?

Hello, Apple developers. I have joined the MFi certification program. My Accessory to use USB HID IAP2 communication protocol and IOS devices connected, but in the first step, the Accessory to send the following data (0 XFF, 0 x55, 0 x02, 0 x00 to 0 xee, 0 x10) for IOS devices, but the IOS devices have no response, this is probably the reason why?

Hi just wanted to ask if it's normal to have a screen who looks like there's slashes all over text, what I mean is there's a visible lines everywhere and it looks like a slashes. For context I recently brought my first Iphone and installed privacy tempered. I only noticed it after I installed the tempered glass. I probably used to much force to erase the bubbles so wondering if that is the caused? Thanks a lot to whoever can answer this. Thanks.

Dear Apple Support Team, I hope this message finds you well. I am writing to report an issue I have encountered with Wi-Fi connectivity on my iPhone 16 series running iOS 18.0. The problem occurs as follows: When attempting to connect my iPhone 16 series (iOS 18.0) to a Wi-Fi network, the connection always fails. After this failed attempt, any other iPhone (not from the 16 series) running iOS 18.0 also fails to connect to the same Wi-Fi network. However, if I restart the Wi-Fi router, the non-iPhone 16 series devices can successfully connect to the Wi-Fi network. To further investigate, I used Wireshark to monitor the network traffic. I observed that the iPhone sends a DHCP Discover message, but the Wi-Fi router does not respond with a DHCP Offer message. Based on these observations, it appears that the issue is triggered by the iPhone 16 series running iOS 18.0, which causes the Wi-Fi router to malfunction and prevents other devices from connecting. Additionally, I have tried all the steps listed on the following site, but the issue persists: https://support.apple.com/en-us/111786 Could you please investigate this issue and provide guidance on how to resolve it? If this is a known bug, is there a planned update to address it? Thank you for your assistance. I look forward to your prompt response. Best regards, WJohn

Hello, I'm creating an app that use PhotogrammetrySession Class to build 3D objects from photographs (https://developer.apple.com/documentation/realitykit/creating-3d-objects-from-photographs). I'm wondering why this class is working only on Pro iphone (12 Pro, 13 Pro, 14 Pro, 15 Pro and 16 Pro) and none non-Pro iPhone. My app does not use Lidar so it's not the problem. I thought it could be power-related but a18 soc from iPhone 16 is more powerful than a14 bionic from iPhone 12 Pro (i could also mention iPhone 13 Pro and iPhone 14 that both have a15 bionic whereas only the first one is compatible). Did I miss something that could explain these restrictions ? Is there any plan to make this class usable by every iPhone enough powerful to run it ? Thanks in advance for answering me

I upgraded Xcode to 16, my Mac to Sequoia and my iphone and iPad to IOS 18. My developer devices are my iPhone, my iPad, my Husband's iPad and iPhone, all running IOS 18. Before upgrading Xcode to 16 I could compile onto all of these devices with no difficulty. But now, Xcode 16 recognises and compiles to all of my developer devices except my iPhone. My Mac recognises my iPhone when I plug it into a USB-C port, but Xcode does not. Xcode does not even try to pair with it or let me try to add it as a device. I have tried switching off dev mode on the phone, switching it back on again, plugging and replugging, rebooting Xcode. But Xcode will not recognise my iPhone, which is a 13 mini. Any idea what to do? I plugged my iPhone into a usb port using a vanilla Apple lightning cable and typed this into Terminal: xcrun devicectl list devices then lists the following. And for info, MCW's iPad and MCW's iPhone are in Shanghai at the moment, I am in the UK. Devices: Name Hostname Identifier State Model EasterdownDev1 00008020-00094D403C41402E.coredevice.local DE6CB0B3-399A-4B54-9ADD-E8758D8D4837 available (paired) iPad mini (5th generation) (iPad11,1) MCW's iPad 00008030-001E18E90AF0C02E.coredevice.local 3AE52B50-D69F-4827-82DA-E6968B0D5A5F unavailable iPad (9th generation) (iPad12,1) MCW's iPhone 00008101-001868D20222001E.coredevice.local 13AABF38-441B-4C4D-9FE8-440D3D9472CC unavailable iPhone 12 mini (iPhone13,1)

Pouvez vous me donner un code d’uns et demander un code d’un et après m’envoyer un courriel et comme ça j’ora mon code.

Pouvez vous me donner un code d’uns et demander un code d’un et après m’envoyer un courriel et comme ça j’ora mon code.

Exact same issues on my old leather MagSafe wallet, so I brought a new one from the Apple Store ‘blackberry’ colour. Yep that’s a word we don’t hear often in tech anymore. Anyway, I’ve reported it in all versions of iOS 18.1 when in beta and they still exist in iOS 18.2 beta 1. I’ve removed them, restarted phone to no avail unfortunately.

iPhone mirroring is available from macOS 15. When running an app with iPhone mirroring Can I know whether the app currently being mirrored is running at the top of the Mac app or screen? Or is there a way to know whether it is hidden by another app on the Mac or re-displayed? If not, I hope it will be added in a future update. And I hope there is an API that can tell whether the current app is connected to iPhone mirroring or not.

iPhone mirroring function has been added to this macOS. I am also currently using the iPhone mirroring function. However, when isSelectable is set to true in UITextView and isEditable is set to false (isScrollEnabled is also set to false.) Editing is not possible, but selection is possible. (In non-mirroring mode) But in iPhone mirroring mode, selection is not possible Is there an option for UITextView that allows text selection or a separate setting in macOS? Or can this be fixed in the iPhone mirroring app when macOS is updated in the future? (If it is a bug or error?) It seems to work normally in cases where UITextView is used but Edit is possible, such as in the memo app.

I installed beta 18.2 on the day of release and requested access to playground that day 2 min after I got in it is now a week later and I still do not have access am I missing something ? 16 pro max

Good afternoon The essence of the question: our product is written in .net maui (a framework for cross-platform development from microsoft), when we use the profile for development in the build and directly install the application on the iPhone, everything works fine. But if you take the same build with the same settings, replace the development profile with the distribution profile, assemble and send it to TestFlight, install it on the same iPhone - when the application is launched, a crash occurs. Yes, we studied the logs, and at the moment we have come to the theory that maybe the main problem lies inside the maui framework, but still - why will the behavior of the application change so much when using different profiles? From full functionality when using the development profile, to crash at the start when using the distribution profile. What exactly changes when you change your profile? Is there any documentation on this topic? Or advice from those who are more knowledgeable about this topic? Thanks in advance for any reply

I have noticed that my iPhone keeps jerking. I notice this juddering especially when the iPhone has been in my pocket and the always on display is not switched off. Normally, the always on display is switched off by the proximity sensor. Sometimes it doesn't recognize this and the display in the pocket stays on. When I then unlock my iPhone and swipe across the home screen, it happens more and more often that it doesn't recognize my input and the display starts to jerk. It actually looks as if the refresh rate of the display has been reduced to 60 Hz or less. Instead of the actual 120 Hz. In addition, accurate input is not really possible. The iPhone sometimes does not recognize any input and generally does not behave like a pro model. I have tried all types of resets and none of them offer a permanent solution. Resetting by “pressing and releasing the volume up button, pressing and releasing the volume down button and then holding the power button until the Apple logo appears” sometimes helps less than switching off in general. I am currently on iOS 18.2 Developer Beta

Hi! I am trying to test an app developed in Xcode 16.1 on an iPhone 7 running iOS 15.8.3. My MacOS is 15.0.1 (Sequoia). But I am getting "iPhone is busy" no matter what I do. And yes - Finder can see the iPhone 7 and show information about it. I have followed a lot of advice that is supposed to solve this, for instance here: https://forums.developer.apple.com/forums/thread/692230 And here: https://stackoverflow.com/questions/46316373/fixing-xcode-9-issue-iphone-is-busy-preparing-debugger-support-for-iphone/48238062 But nothing works. Actually it's getting worse... At one point it said "100% complete", although it was still "busy". But now I don't even get to the "100% complete" message... (After 30 minutes.) So my conclusion is that it's impossible to use an iPhone 7 running iOS 15.8.3 to test an app developed in Xcode 16.1 on MacOS 15.0.1. Am I right? In that case: Which iPhone models and iOS versions can be used instead?

I was on iOS 18.1 beta 6 on my iPhone 14 Pro Max when my iPhone 16 Pro Max arrived. I took it out of the box and started to set it up as usual. I scanned the moving blue circle with my camera and began setting up the device. When I reached the software update screen, it was going to update to iOS 18.0.1. The phone restarted, and everything seemed normal. However, it brought me back to another update screen, asking me to go through the same setup steps again, which I found odd. This time, the update was for iOS 18.1 beta 7. After the update, the device restarted and appeared to be good to go, but it wasn’t. It wouldn’t go past the lock screen and kept respringing when I held down the power button to turn it off. I tried to restore the device from my computer using Apple devices, and it began to restore. The Apple logo appeared on the black screen with a loading bar, but it got stuck at about 15%. It remained like that for over an hour while plugged in. I hard restarted the device, following Apple Support’s directions, and the device became corrupted, stuck on the restore screen. I attempted to restore it again from my computer, but it only gave error codes and once again stalled at 15% of the loading bar. The error and videos and images are linked below one error is not in pictures but it was unexpected error 3503 could not complete update and restore. Betas are Apple Original, they are developer betas as I have a developer account.

I have recently been having trouble with my iOS 18.2 beta update. It has been 2 weeks since I have updated to iOS 18.2 beta and joined the Genmoji and image playground waitlist. I am wondering how much longer I have to wait till my request is approved.

We have a USB dongle that would like to connect to the iPhone for power (using USB-C). Since it is not MFi, we will then use bluetooth for communication between the dongle and an app. When doing bluetooth pairing between the dongle and iPhone, it would be ideal to only see the dongle that is plugged into the iPhone listed in the app. This is to avoid connecting to other dongles that may be in the area. We think this could be possible using USB descriptors. We assume the iPhone can read the USB descriptors for non-MFi dongles. Our question is, can our app see the USB-descriptors of the dongle? Is iOS able to pass that info to the app? Then, we could have a unique USB descriptor for each dongle and the app could only list bluetooth devices with that descriptor (effectively filtering out any other dongles in the area). Any help and/or feedback is greatly appreciated :)

Hello community, I have the following problem, when I update my Mac to Mac Sequoia 15.1, it does not let me install any library in my project and I get the following error that is reflected in the screenshot. Greetings

I belong to an EC shop application developers' team, and we got a crame from a small part of our customers about our application. "Search Bar does not work on iOS 18." This bug doesn't appear on most of our devices updated to iOS 18.0. In some cases, it disappeared by turning [Settings > Accessibility > Touch > Reachability] off. But it is not the same for all customers found the bug. I'm looking for how to fix this bug, and why it happens. I'm not sure but I doubt that this may be a bug of iOS18, UIKit, RxCocoa, RxSwift, or something else. Any information would be welcome. import UIKit import RxSwift import RxCocoa @IBDesignable public final class SearchBar: UISearchBar { var textField: UITextField { if #available(iOS 13.0, *) { return searchTextField } else { return value(forKey: "_searchField") as! UITextField } } private let disposeBag = DisposeBag() private func bind() { textField.rx.isFirstResponder .bind(to: Binder(self) { me, isFirstResponder in // This doesn't work in some iOS 18 devices. me.textField.attributedPlaceholder = placeholderAttributedString(isFirstResponder: isFirstResponder) me.textField.backgroundColor = isFirstResponder ? Asset.Colors.whiteTwo.color : .white if me.useCancelButton { me.showsCancelButton = isFirstResponder } if me.useBookmarkButton { me.showsBookmarkButton = !isFirstResponder } }) .disposed(by: disposeBag) } public override init(frame: CGRect) { super.init(frame: frame) commonInit() } public required init?(coder aDecoder: NSCoder) { super.init(coder: aDecoder) } public override func awakeFromNib() { super.awakeFromNib() commonInit() } public override func prepareForInterfaceBuilder() { super.prepareForInterfaceBuilder() commonInit() } private func commonInit() { bind() } } extension Reactive where Base: SearchBar {} import UIKit import RxSwift import RxCocoa @IBDesignable public final class SearchHeaderView: UIView { @IBOutlet private weak var searchBar: SearchBar! @IBOutlet private weak var cartContainerView: UIView! private let disposeBag = DisposeBag() public override init(frame: CGRect) { super.init(frame: frame) loadFromNib() commonInit() } public required init?(coder aDecoder: NSCoder) { super.init(coder: aDecoder) } public override func awakeFromNib() { super.awakeFromNib() loadFromNib() commonInit() } public override func prepareForInterfaceBuilder() { super.prepareForInterfaceBuilder() loadFromNib() commonInit() } private func commonInit() { bind() } private func bind() { // ↓ This doesn't work in some iOS 18 devices. searchBar.textField.rx.isFirstResponder .bind(to: cartContainerView.rx.isHidden) .disposed(by: disposeBag) } } extension SearchAndCartHeaderView: NibOwnerLoadable {}

I've noticed an issue when using an iPhone or iPad that uses a USB-C port (such as the iPhone 15 Pro or iPad Pro 12.9" 6th generation) and a USB-C to USB-C cable on ARM Macs (such as the M2 Mini). After rebooting the Mac, the iOS device is no longer recognized despite the iOS device continuing to charge. I can temporarily resolve the issue by reseating the USB-C cable, which allows the device to be recognized again by applications like Finder. However, this isn't a practical solution due to the number of M2 Minis we have (each with an attached iPhone for testing) and the Mini's frequent automatic reboots throughout the day. Using a USB-A to USB-C cable (with USB-A connected to the Mac Mini) seems to avoid this problem altogether, as the iOS device remains consistently recognized after a reboot. As the title suggests, this issue appears to be specific to ARM-based Macs. We've encountered it on both the M2 Mini and a 2021 Macbook Pro with the M1 Max chip. Interestingly, we haven't been able to reproduce this behavior on Intel-based Macs (tested on an 8,1 Mac Mini and a 2019 16" Macbook), where the iOS devices remain connected after a reboot when using a USB-C to USB-C cable. Here are some additional details: iOS Devices & Versions: iPhone 15 Pro: Issue persists on both iOS 17.1 and iOS 18.0.1 iPad Pro 12.9" (6th generation): Issue persists on both iPadOS 17.6.1 and iPadOS 18.0.1 Cables: Apple's 60W USB-C Charge Cable (USB 2.0): Issue occurs Generic/Third-party USB-C cable (USB 3): Issue occurs