iOS 18 System Bug Causes URL Scheme Failure A bug in iOS 18 causes URL Schemes to become invalid through the following steps, resulting in failure to open apps via URL Scheme. Reproduction Steps: Long-press the app icon Select "Require Face ID" Choose "Hide and Require Face ID" to hide the app Go to the App Library and locate the hidden app in the "Hidden" folder Uninstall the hidden app reinstalling the hidden app After reinstalling the app, all configured URL Schemes will become invalid, causing failure when attempting to open the app via URL Scheme. The issue appears to be that after uninstalling a hidden app and reinstalling it, the system fails to restore the app's URL Scheme functionality.

I don't know if this is the right place to raise this, so apologies if not. For years now, I have exported an NFS share from a host Mac which I connect to from a Raspberry Pi on the same network. I configure this by adding a line in /etc/exports - /Users/Pi -mapall=myusername This has always worked flawlessly, but since updating my Mac (M4 Mac Mini) to Sequoia 15.5 last week, it has developed a problem. If the NFS share is not accessed from the Pi for five minutes, it dies, and the Pi's file manager locks up necessitating a complete reboot. If I run a script on the PI which does an ls on the mounted share every 5 minutes, the lockup does not happen. But if I extend the period to 6 minutes, the lockup occurs. Something on the Mac NFS server seems to be dying in an unrecoverable fashion after five minutes of idle. Even with nfsd logging set to verbose, there is nothing helpful in the console logs. I am open to suggestions to further investigate or to try and fix this, but this is basically a showstopper for me - I need to be able to share data between Mac and Pi, and this is now broken.

Cannot Install Tahoe Beta 2 because Software Update Dialogue Box will not accept my Password (None in my case). Reports: "User interaction required" Recommendations?

Some users of my app complain that it stops responding to touch after a while. The screen is still updating, and the app seems to be working normally otherwise. It just doesn't respond to any touches anymore. It is not a problem with the touchscreen itself, because the user is able to swipe up to get to the home screen, and then interact with other apps as normal. When re-opening my app, it is still unresponsive to touch. The only way to solve it, is to restart the app. Does anybody have a similar experience, and knows what could cause it? The app is based on UIKit, and still written in Objective-C, if it matters. The iOS version involved does not seem to matter, it happened with a couple of them.

Hey everyone. Ever since installed OS26 (and 26.1 now) - whenever I fast play any video on 1.25x, 1.5x, 2x on the AppleTV - the audio gets massively distorted on HomePods. Be it on YouTube, Difuse, or any supporting app. I even tried mirroring from iPhone -same issue. Anyone else experiencing the same? I noticed no posts about troubleshooting.

Hello everyone! I'm a newly graduated Computer Engineer living in Türkiye. I've been developing my skills in the iOS field for a while now. But sometimes I get lost and don't know what to do. I've just joined this community and have a request for you. I'd be very grateful if you could share your own advice, experiences you've had along the way, and how you successfully overcame them. I'm open to all kinds of positive or negative feedback. Self-improvement is paramount to me.

In the public release of iOS 18.4.1 and iPadOS 18.4.1, external input support for keyboards and mice is critically degraded. This issue affects both Apple-branded and third-party HID-compliant devices, over both wired USB-C and Bluetooth. Tested Hardware: • iPhone 16 Pro Max (256GB) • iPad Pro (USB-C, latest gen), last gen iPad as well Affected Devices: • Apple Magic Mouse and Keys (wired USB-C/Bluetooth) • Redragon K580RGBPRO (Bluetooth/wired USB-C) • Razer Naga V2 Pro (Bluetooth/USB-C) Symptoms: • Severe keystroke delay and dropped input • Modifier keys (Shift, Command, Option) fail intermittently • Input degrades further with multiple HID devices connected • Mouse input via Bluetooth exhibits pointer lag and jitter • Occurs in all apps: Notes, Safari, Mail, text fields, password entries, etc. • Identical results using Apple USB-C cables Reproducibility: 100%. Clean boots, minimal background activity, and isolated environments (including Airplane Mode) do not resolve the issue. Identical behavior across both iPhone and iPad. Expected Behavior: All HID-compliant external input devices — particularly Apple-branded ones — should provide low-latency, reliable, and consistent input over both USB-C and Bluetooth, especially in a production iOS/iPadOS release. Actual Behavior: External keyboards and mice exhibit: • Lag • Dropped characters • Failed modifiers • Degraded mouse tracking Even with the latest hardware and clean configurations. Severity: Critical. This is a platform-level failure affecting I/O at the user interaction layer. Input reliability is non-negotiable — especially on $2000+ flagship devices using Apple’s own peripherals. Closing Note (for Apple engineering & peer devs): This is not a beta regression — it’s a public release flaw that undermines iOS and iPadOS usability for power users, professionals, and accessibility communities alike. That Apple Magic Keyboard, Redragon, and Razer gear all fail equally and consistently should be a wake-up call. Apple: this needs to be escalated. Now. External input — one of the most basic subsystems in any OS — is broken on your highest-end devices.

Hi everyone, It’s been almost three weeks, and I’m still waiting for a reply about my subscription to the Apple Developer Program, but I haven’t received anything. I replied to the email three days ago and got no response. I tried again by requesting the subscription two days ago, but all I received was an automated message saying they would reply within two business days. What I did: I went to my Apple Developer account, clicked on Subscriptions, and entered my card details. They sent me an email saying they are preparing my order, but nothing else. Has anyone else had the same issue with Apple Developer support? Regards,

Recently update my 15 pro max to ios 26.2 and now 90% of the apps are not working. No payment app is working. Even G Map and G Drive isnt working. Amazon is down. I am not able to use UPI or even pay electricity bill.

.fullScreenCover(isPresented: $isShow) { Button(action : { isPresented.toggle() }){ Text("Choose") } .familyActivityPicker( isPresented: $isPresented, selection: $selection) .onChange(of: selection){ value in } } In the official version of iOS 18, when I click the Done button of familyActivityPicker, the fullScreenCover pop-up box will disappear.

I tried to enroll some weeks ago, went thru the whole process, it eventually took by IDs, but now I'm stuck on "Enrollement not completed - You enrollment in the Apple Developper pogram could not be completed at this time." So, after 2 weeks, what's next ?

As l proceeded through the enrollment/membership. I found the price is fixed for US$99. At the end. What about Renewal. Is there any cost reduction for Apple Developers?

Updated iPhone to 26 beta 2, everything is ok but battery, battery is changed, not original. My phone can't charge higher than 1% and turns off every 5 minutes, even connecting to wireless charger and cable at the same time don't work, restored iPhone thru iTunes.I hope I will be able to install new beta without any problems because loving the new design,hoping for the best. Thanks.

The iPhone XS Max and Garmin watch pairing cannot use BLE to send Scan Response; it can only send BLE advertisements. May I ask if this is a limitation of the Apple system? So far, we have tested several iPhone models, and only the iPhone XS Max has this issue. We are not sure if other untested models have the same problem.

My app has three main SwiftData models: Collection, SavedItem, and Extract. A Collection can contain subcollections (folders within folders) and SavedItems (files). Each SavedItem can have child Extracts. I'm preparing for the ability for users to be able to share Collections with each other. Currently, my architecture treats each Collection as the root of its own CloudKit zone (a root parent Collection and all of its items and subcollections live in 1 zone). This makes sharing and isolation straightforward, but it also means that moving a SavedItem or subcollection between Collections involves moving it across zones. I’m trying to figure out the best pattern for handling these cross-zone moves while keeping data integrity, relationships, and sharing intact. My understanding is that in CloudKit, and moving a record from Zone A to Zone B would require deleting it from Zone A and recreating it in Zone B - while somehow maintaining the link back to my local SwiftData store. Has anyone run into this or know how best I should handle it?

Hello Apple Team, I love the existing keyboard shortcuts such as Control + Function + Left/Right Arrow which allow moving windows to the left or right half of the screen. It significantly improves window management and productivity. I would like to kindly request a similar feature to move windows across multiple monitors using a keyboard shortcut. This would be especially helpful for users with multi-monitor setups who want quick and seamless window transitions between displays without using the mouse. This enhancement could align with Apple's commitment to intuitive and efficient user experience, helping users manage their workspace more effectively. Thank you for considering this feature request!

I just downloaded ios 26 atm i was upgrading my phone battery was 50% and charging , now when i fully installated ios 26 it shows battery 1% and even i try to charge it still stays at 1% any idea how to fix it

I am trying to create a new app using IOS-26.1, macOS Tahoe 26.1 and Xcode 26.1 with Swift6. Is this a bug that is going to be addressed. This is in the Debug Console...Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints) ( "<NSAutoresizingMaskLayoutConstraint:0x10bb18870 h=--& v=--& _TtCC5UIKit19NavigationButtonBar15ItemWrapperView:0x115da48c0.width == 0 (active)>", "<NSLayoutConstraint:0x115ac2ee0 _TtCC5UIKit19NavigationButtonBar15ItemWrapperView:0x115da48c0.leading == _UIButtonBarButton:0x115d40c80.leading (active)>", "<NSLayoutConstraint:0x115ac30c0 H:[_UIButtonBarButton:0x115d40c80]-(0)-| (active, names: '|':_TtCC5UIKit19NavigationButtonBar15ItemWrapperView:0x115da48c0 )>", "<NSLayoutConstraint:0x115ac2df0 'TB_Leading_Leading' H:|-(12)-[_UIModernBarButton:0x115d20a80] (active, names: '|':_UIButtonBarButton:0x115d40c80 )>", "<NSLayoutConstraint:0x115ac2fd0 'TB_Trailing_Trailing' H:[_UIModernBarButton:0x115d20a80]-(12)-| (active, names: '|':_UIButtonBarButton:0x115d40c80 )>" ) Will attempt to recover by breaking constraint <NSLayoutConstraint:0x115ac2fd0 'TB_Trailing_Trailing' H:[_UIModernBarButton:0x115d20a80]-(12)-| (active, names: '|':_UIButtonBarButton:0x115d40c80 )> Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger. The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.

Around October 17, our app was removed from the App Store, and we were later informed that our developer account would be terminated within 30 days. This was an unexpected and shocking notice for us. After carefully reviewing Apple’s Developer Guidelines, we conducted a thorough internal investigation and confirmed that we did, in fact, violate certain policies. However, we are unsure whether the Apple Review Team could give us an opportunity to make corrections—otherwise, our new apps will not be able to launch on the App Store in the future. The stated reason for our account termination was: “You provided fraudulent and/or false account information, documentation, or otherwise falsely represented yourself or your submitted app to Apple either during the account enrollment process or after the account was created.” After reviewing this issue, we identified two foolish and critical mistakes on our part: We registered our developer account using our Mainland China company, but used a Hong Kong company’s bank account for payments. (Both companies are under the same management, and we have submitted supporting documentation during our appeal.) Our official website, Privacy Policy, and Terms of Service also displayed the name of our Hong Kong company instead of the Mainland China entity used for registration. Despite these mistakes, we have continued to support our users through email and our Discord community, resolving most issues within 24 hours. We have never deceived our users or the Apple Review Team in any way. For us as developers, providing an excellent user experience has always been our top priority, and we have always aimed to follow Apple’s review and compliance standards closely. We sincerely hope that, given our situation, the Apple Review Team could grant us an opportunity to correct these issues. We will promptly register a new Hong Kong Apple Developer Account, and once our app is reinstated, we will migrate all relevant information to that new account to ensure full compliance moving forward.

If Apple truly requires this much space for the system, I honestly don’t see the point of having a 256GB device. I have no way of knowing what exactly is included in “System Data,” and I cannot modify or manage it. This is extremely frustrating and confusing for users. Can someone explain why this is necessary?