Hi, I’ve recently installed the iOS 26 DB, and I’m experiencing heating issues on my iPhone. Is there a fix to this? Also, is it a bug or a feature, that I can’t remove certain sections in the Photos app rather than rearranging them. Pls lemme know. Thanks.

Hi! I found a UI bug in iOS 26.0 (23A5276f). When you swipe down from the top right to open Control Center and adjust brightness using the slider, everything looks normal. However, if you long-press the brightness slider, the brightness knob detaches from the base. The button becomes smaller while the frame remains the same, making the UI asymmetrical and misaligned. This happens consistently and is clearly a layout issue.

We have observed an issue where upgrading an iPhone to iOS 18.4 causes installed apps to revert to significantly older versions. For example, if the App Store version is 1.0.284 and the user had 1.0.283 installed before the upgrade, after updating to iOS 18.4, the app version reverts to 1.0.208—which is nearly a year old. We suspect this may be related to iCloud backup restoration. Has Apple encountered similar cases, and is there a known resolution for this issue?

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

Please expedite to Solve this bug , my Singpass is unable to launch in iOS 26. I believe this is more urgent than a new pride theme wallpaper 🏳️‍🌈

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

Enrolled via website for the apple developer account last Jan. 17 and got the e-invoice last Jan. 19. However, until now I still have not received any confirmation from Apple. I thought it was supposed to be 48hrs max only? Worth noting that I started the process in the developer app but had to withdraw it due to incorrect details but when I tried to enroll again, the button was disabled already so I had to do it via website. I also submitted 2 support tickets, one on Jan. 18 and one today, Jan. 20. Both no reply. Anyone else here had the same problem or knows the solution?

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.

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.

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

Facial recognition is not working with the glasses. I tried to do a new recognition with the glasses, and it's giving a direct error. Is anyone having the same problem?

Unable to search contacts , app crashes Call screen goes compl transparent

Hello Apple Developer Community, I'd like to propose a system-wide enhancement for future versions of iOS: the integration of native utility apps — Calculator, Compass, Voice Memos, Magnifier, Measure, Weather, and Translate — into a single unified app, tentatively called Apple Assist. The vision is to provide: A modular interface where users can enable/disable tools as needed. Smarter workflows with proactive suggestions based on context (time, location, task). AI-powered interaction through voice and Apple Intelligence (Advanced Siri). Benefits: Reduces icon clutter on the Home Screen. Simplifies the user experience with a single access point. Creates opportunities for automation and accessibility. Imagine saying: “Hey Siri, record a quick note and measure the table” — and the app smartly loads those modules on demand. Would love to hear feedback from the community — and whether Apple might consider something in this direction for iOS 19 or beyond. Best regards, Jose Luiz Horta Barbosa Maurity Cruz

we’ve identified that our PDF rendering pipeline leverages the native CGPDFDocument APIs to convert PDF pages into images. However, in the latest release of iOS 18, the provided document fails to render even at the CGPDFDocument level. Our analysis suggests that the issue may stem from the embedded custom fonts not being correctly processed in this version of the iOS platform. This appears to be consistent with several other reports and discussions around font rendering problems introduced in iOS 18, particularly involving subset fonts. We’ve attached a collection of relevant community threads and references, including: Apple Developer Discussion: Subset Font Rendering Issue in iOS 18 Given that our implementation is tightly coupled with Apple’s native PDF rendering APIs, this issue presents a blocking limitation for us. With your permission, we would like to use this document as a sample case to formally report the issue through the appropriate Apple Developer forums and feedback channels.

<SKPaymentQueue: 0x10629d1b0>: Payment completed with error: Error Domain=ASDErrorDomain Code=500 "(null)" UserInfo={client-environment-type=Sandbox, storefront-country-code=USA, NSUnderlyingError=0x108f15c80 {Error Domain=AMSErrorDomain Code=305 "Purchase Failed Server canceled the purchase" UserInfo={AMSFailureReason=Server canceled the purchase, AMSURL=https://sandbox.itunes.apple.com/WebObjects/MZBuy.woa/wa/inAppBuy?guid=00008030-001E19361A12202E, AMSDescription=Purchase Failed, AMSStatusCode=200, AMSServerPayload={ "cancel-purchase-batch" = 1; customerMessage = "Unable to process your request."; dialog = { defaultButton = ok; explanation = "Please try again later.\n\n[Environment: Sandbox]"; initialCheckboxValue = 1; isFree = 1; "m-allowed" = 0; message = "Unable to process your request."; okButtonString = OK; }; failureType = ""; "m-allowed" = 0; metrics = { actionUrl = "sandbox.itunes.apple.com/WebObjects/MZBuy.woa/wa/inAppBuy"; asnState = 0; dialogId = "MZCommerce.SystemError"; eventType = dialog; message = "Unable to process your re"; mtEventTime = "2025-07-30 07:08:24 Etc/GMT"; mtTopic = "xp_its_main"; options = ( OK ); }; pings = ( ); }, NSDebugDescription=Purchase Failed Server canceled the purchase}}}

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.

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.

I paid for my developer account on the 13th of June 2024 (1 week ago). My ID was approved. However, I still don't have access to the account. When I go to check the status of it, it is asking me to pay again. I then tried to email the team, however only received useless, timewasting responses, such as "Please go to developer.apple.com/enroll to enroll for an apple dev account", which I already told them prompts me to pay again and verify my ID again. I then tried to call them, and they said they had to re-verify my ID and would call me back in 10 mins, but I never received a call back. I also couldn't call them again because it wouldn't let me request another call from them. I then emailed them, but still haven't received a response. The next day I tried to request another call from them, during their opening hours at Thursday 4pm AEST, (they are open Mon-Fri 9am-5pm AEST see https://developer.apple.com/support/worldwide-telephone-hours/) however it still says that "Phone support is currently unavailable". I tried to email them but now I am getting no responses at all. I tried to contact the apple support through the iMessage chat, however I was only put on call with a lady who was helpful, but couldn't even do anything as she was only generic support. She couldn't even schedule me a call or transfer me to the developer team, even though it was within their working and calling/support hours. I have tried to refund my developer account, but apparently that purchase is "illegible for a refund". This is the treatment I get from apple for paying $100 USD. An entire week of being left on blank. I don't know what to do. I paid 100 bucks for an account which I can't even use, and the support hasn't helped me for an entire week. My emails being left on blank, and I can't even call them. If anyone from apple or anyone that could help me sees this, please contact me ASAP at makrypodisc@ hotmail.com or reply to this thread. Thank you.

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?