Area: Software Update Type of Feedback: Application Bug Description Device: iPhone 13 Pro running iOS 26 Build environment: Xcode 16.4 Problem description: When a text field has secureTextEntry = YES and Password Autofill / Passkeys is active, the autofill panel is not included in the rect reported from the keyboard notifications (UIKeyboardFrameEndUserInfoKey or others). As a result, when calculating the offset to move the screen up and reveal the hidden input field, the field is not displayed correctly because the reported keyboard height is smaller than the actual visible height. Observed behavior: This only occurs on devices running iOS 26 built with Xcode 16.4. On previous versions of iOS, with the same settings (secureTextEntry and Autofill active), the rect correctly includes the autofill panel height, and the UI works as expected. I tested with both UIKeyboardDidShowNotification and UIKeyboardWillChangeFrameNotification, and in both cases the behavior is the same: the height is incorrect (smaller than expected with the autofill panel). What I expect / questions: That UIKeyboardFrameEndUserInfoKey (or the related notification) correctly reports the total area covered by the keyboard, including any password autofill panel, when secureTextEntry is active. That the new behavior in iOS 26 be documented if this omission is intentional, or otherwise considered a bug if it is not. If there is any official workaround suggested by Apple for developers affected by this issue while a fix is provided. Thank you for your support.

Hi all, I’m running into a persistent build issue with my Swift project ORSOFINAL after migrating from Xcode stable to Xcode-beta.app (June 2025 version). ⸻ 💥 Errors displayed: 1. C99 was enabled in PCH file but is currently disabled 2. module file .../ModuleCache.noindex/SwiftShims-AXUM98L131W4...pcm cannot be loaded due to a configuration mismatch with the current compilation 3. missing required module 'SwiftShims' ⸻ 🛠 What I’ve already tried: • xcode-select -s /Applications/Xcode-beta.app/Contents/Developer • Deleted ~/Library/Developer/Xcode/DerivedData, ModuleCache.noindex, Archives, and Products • Ran sudo xcodebuild -runFirstLaunch • Clean Build Folder in Xcode-beta • Verified Command Line Tools setting points to Xcode-beta ⸻ ❓Looking for guidance on: • Whether this is a known bug in Xcode-beta • If SwiftShims/PCM conflicts are expected between versions • Best practices to safely migrate from Xcode stable to beta for Swift-based projects Any advice is much appreciated. Thanks, Mathéo

I set iOS 26 to install overnight, put my iPhone 16 Pro on the MagSafe charger, watched it charge just fine, and went to sleep. When I woke up the iPhone showed the “plug into power” dead battery screen. I took it off MagSafe and put it back on. A half hour later the phone was warm but still wouldn’t power on, just showed the battery screen with a little red in it. I took it off MagSafe and plugged it into my iPad charging brick with USB cable to give it more power, still it did not turn on. I tried holding all the buttons to try to force a restart but didn’t work. For anyone else encountering this, do this to enter DFU mode and restore it. I had to do it a few times before I got the timing right. Plug into your Mac and open Finder (or apparently a PC with Apple Devices or iTunes) Press and quickly release volume up Press and quickly release volume down Press and hold right side button When the battery disappears and screen goes black, hold volume down and continue holding side button After a couple seconds release the side button and continue holding volume down A prompt to allow connecting to the iPhone should appear after a couple seconds, click Allow, and it’ll say the iPhone entered DFU mode - proceed to restore the firmware

Problem Description When the Type-C port is connected to an ASUS ROG Swift OLED PG32UCDM monitor set to 3840×2160 @ 120 Hz, and the DP port is connected to a Samsung U28E590D monitor set to 3840×2160 @ 60 Hz, the DP port shows no response and no video output after the system wakes from sleep. The DP monitor is not detected. Reproduction Steps Apple MacBook Pro (14-inch ,2024) connect the DP port to Samsung U28E590D and set the resolution to 3840×2160 @ 60 Hz. Connect the Type-C port to ASUS ROG Swift OLED PG32UCDM and set the resolution to 3840×2160 @ 120 Hz. Put the platform into sleep mode, then wake it up. After wake-up, the DP port has no response and no video output. Bug Description When the Type-C port is connected to an ASUS ROG Swift OLED PG32UCDM at 3840×2160 @ 120 Hz, and the DP port is connected to a Samsung U28E590D at 3840×2160 @ 60 Hz, the DP port fails to output video after system sleep and wake-up, and the monitor is not detected.

one of my app users cancelled the subscription from settings. After that, she tried to buy the subscription from app which she could not as I receive same transaction id and previous exp date.

Installation has completed login is successful but after 30 secs it returns to login screen safe mode does the same. tried recovery mode and reinstalled. Still in the login loop. what are my choices now?

Is anyone else having trouble posting to the forums? I can't get past form validation.

アプリ開発を依頼して公開中ですが、 アプリ開発会社が倒産し、連絡もつかず、 アップル社への年間料金の支払いができません。 登録アカウントがわかりませんので、どうしたらいいでしょうか？ よろしくお願いいたします。

Recently I've noticed that certain cursor actions cause the finger icon to appear with a gray box around it. It appears when I hover over other icons (for example, the menu items at the top of this website; Microsoft Teams options but not MS Word, etc.). Is this new? Is there a way to get rid of the box?

I’m experiencing an issue on macOS Tahoe (Developer Beta, July 2025) related to the new “Allow in Menu Bar” section in System Settings. After uninstalling the application Backdrop (developer: Cindori), the entry com.cindori.Backdrop.Wallpaper still appears in the list of apps allowed to show in the menu bar, even though: — The app and all its associated files have been fully deleted. — The LaunchAgents files in ~/Library/LaunchAgents and /Library/LaunchAgents have been removed. — Preferences have been deleted via defaults delete com.cindori.Backdrop and defaults delete com.cindori.Backdrop.Wallpaper. — The system has been restarted. It seems the “Allow in Menu Bar” section keeps phantom references to apps or agents even after complete cleanup. Could you please confirm if this is expected behavior (perhaps for future reactivation) or a bug? Is there any official method or recommended command to permanently remove such residual entries from this list? Thank you very much for your help and clarifications.

Problem description: Connected to a Sharp 8TC60DWTX (8K) display, but unable to select 4K resolution Setup Condition Apple MacBook Pro 16-inch M4 Max Sharp 8TC60DWTX (8K) 3.Duplicate Procedure After connecting to 8K MNT and select 4K solution, it still display as 8K. Vendor analysis: 8K60 shows no image; switching to 30 Hz works normally → After analysis, we found that the 8K60 timing output from the MacBook is incorrect. The horizontal blanking (H-CBlanking) is too small to accommodate the audio data, so the RTD2191E does not output video to the monitor. → This issue does not occur on Windows platforms, confirming that this is a host-side issue.

Hi everyone, my Digital Services Act (DSA) status in App Store Connect has been “In Review” for over a week. Is this normal? The app is already available in 178 countries, but it can’t be released in the EU (my home market) solely because this DSA isn’t approved yet. How long did it take for you? Is there anything that helps speed up the DSA review? Thanks for any insights.

When I try to create a post in Apple Support Community, it forces me to create a new account (for some supersmart reason because my apple account is apparently not enough). In this process, I am required to pick a new username and choose my communications preferences. The next screen? 403 Forbidden Error page.

Hello everyone, I'm a 2nd-year Computer Science student who's excited to dive into iOS development, and I'd really appreciate some guidance from the experienced developers in this community. MY CURRENT BACKGROUND I have a solid foundation in programming fundamentals through my university coursework (data structures, algorithms, OOP concepts), and I'm familiar with general software development principles. However, iOS development is entirely new territory for me, and I want to make sure I start on the right foot. WHAT I'M LOOKING TO UNDERSTAND Learning Path & Technologies Should I start with UIKit or SwiftUI? I've heard conflicting opinions about this How important is it to learn Objective-C in 2025, or should I focus solely on Swift? Are there any foundational Apple frameworks I should prioritize learning early on? Roadmap & Structured Learning Is there a recommended roadmap or learning sequence I should follow? What skills/topics should I master before moving to more advanced concepts? Should I learn iOS development in a linear fashion, or is it better to learn as I build projects? Are there any official Apple learning paths or certifications worth pursuing? Common Mistakes to Avoid What are the most common pitfalls beginners face when starting iOS development? Are there any bad habits or patterns I should consciously avoid from day one? What misconceptions did you have as a beginner that you wish someone had corrected earlier? Project-Based Learning What types of projects would you recommend for someone at my level? Should I build several small apps or focus on one comprehensive project? At what point should I start contributing to open-source iOS projects? Best Practices & Design Patterns Which iOS-specific design patterns (MVC, MVVM, etc.) should I learn first? How can I develop good habits around memory management and app architecture from the beginning? What resources do you recommend for learning iOS best practices, not just syntax? Apple Ecosystem & Tools Beyond Xcode, what tools should be in my toolkit? How important is it to learn about TestFlight, Instruments, and other Apple developer tools early on? Should I get comfortable with CocoaPods/SPM from the start, or wait until I'm more experienced? MY GOALS My goal is to build a solid foundation over the next 6-8 months, create a few portfolio-worthy apps and pursuing iOS development as a career path after graduation. SPECIFIC QUESTIONS How many hours per week would you recommend dedicating to learning iOS development while managing university coursework? What's the best way to stay updated with Apple's annual changes and new frameworks? When should I start thinking about publishing apps to the App Store? Are there any mentorship programs or communities specifically for beginner iOS developers you'd recommend? I know this is a lot of questions, but I genuinely want to learn the right way rather than picking up bad habits I'll have to unlearn later. Any advice, resources, or personal experiences you're willing to share would be incredibly valuable to me. Thank you in advance for taking the time to help a beginner. I'm committed to putting in the work and learning properly!

Steps to Reproduce make an outbound call cover the sensor Actual Behavior the screen won't go dark device iOS Result iphone15 17 Pass iphone14p 18.0.1 Pass iphoneXs_pro max 18.1.1 Pass iphone13pro max 18.2.1 Pass iphone16pro 18.2 Fail iphone15pro max 18.3 Fail iphone12 pro max 18.3 Fail ps: Skype has the same probelm Seems like this issue only happens on iOS18.2+ on some devices, so is there a bug for this?

HiIm currently on iOS 11 Beta 2 (Build 15A5304i) With Update 1 Build 15A5304j just been released, will there be any difference since last weeks release?I can't update OTA to the new build released today.ThanksBarry

Issue in now mode in console Reproduce steps: open /private/var/log/com.apple.xpc.launchd/launchd.log in console app click now to enable it wait for system to write some to the log. instead of tailling log, it comes to the start of log. I have filed a bug 3 months back FB16849784 it is not resolved yet.

I have filed 27 bug reports against macOS using Feedback Assistant and none have had any sort of follow-up. I'm wondering if anyone at Apple looks at these reports? A few of these involve accessibility features that are not working (for example: speak announcements doesn't work -- and yes, my feedback is much more detailed than "doesn't work"). I would have thought issues with accessibility would be a high priority for Apple to fix quickly. Another report is that Grapher uses black text on dark gray making it very difficult to see the formula you enter. This should be a one-line code fix. These two, and 25 other bug reports have seemingly been ignored. Several of these reports indicate more than 10 similar reports, yet go unfixed. Leading me back to my opening question -- does anyone at Apple read these reports? I'd like to think I'm helping Apple to deliver a more perfect product but I feel like I'm wasting my time writing detailed bug reports. Is there another way to bring these to Apple's attention?

Hi all, Well Im about to publish an app for iOS and the process is almost done but I don't know how is it to publish the same for MacOS, I mean, I can generate the app file from my engine (Unity) and even run it, but from there what are the steps? do we need to pass this to Xcode too? if so please direct me to where its explained because I couldn't find it, thanks a lot for any help