The newest iOS 26 CarPlay upgrade seems more like a downgrade with vehicles from Subaru with the 11.6 inch vertical infotainment display. Such a big screen, but only one widget shows at a time additionally, prior to this iOS update we had three lines of apps on the main page now only two. also to be noted album art size on all music streaming and podcast apps is extremely small about half the size of what it originally was prior to this update yes, I tried turning on and off the screen optimization setting and CarPlay. It did not do anything.

Hello within these last two updates find my location has been turned off for my other phone number, only a specific number can’t see my location, but everyone else can see my location, I am puzzled as to what is going on

Almost everytime, when I try to search apps in App library, the icons go invisible, o are showed for and instant to quickly go invisible.

Hi, I’ve been experiencing a strange issue with video playback on my iPhone. While watching videos, the image will suddenly shift it becomes more greyish, then sometimes briefly goes black, and then returns to normal bright quality. This can happen multiple times during a single video. This is not limited to the Photos app. I’ve seen it happen: In the Photos app when playing videos I recorded myself In Snapchat when watching videos sent by others Occasionally in other social media apps as well Additional details: HDR Video is turned off Apple ProRes is turned off Tried both 4K 60fps and 4K 30fps Camera format set to “Most Compatible” Low Power Mode is off Issue happens whether the phone is cool or warm Doesn’t seem related to the video file itself the same file exported to another device looks fine all the way through These exact same videos play back completely normally on my iPad with no brightness or contrast shifts at all I’m currently on the iOS 17 public beta, but this issue was happening before I installed the beta as well, so it’s not beta-specific It almost feels like the display or system is switching between different brightness/contrast profiles mid playback, regardless of the app. Has anyone else experienced this, and is there a way to disable this behavior so the brightness and color stay consistent during video playback? Thanks in advance!

I file a lot of bug reports. I also ask a lot of third-party developers to file bug reports about problems they see. This post is my attempt at collecting together some hints and tips about Apple’s bug reporting process. To file a bug report, use Feedback Assistant. To file an enhancement request, use Feedback Assistant. In the “What type of issue are you reporting?” popup, choose Suggestion. If you’re filing a bug against an API, choose Developer Technologies & Resources at the top level. The technologies popup should then list familiar items, from Accelerate Framework to XPC. If you can’t find the correct item, select “Something else not on this list”. Feedback Assistant is both a website and an app. For details on how to access the app, see Opening the app on the Developer > Bug Reporting page. For lots of great hints and tips about filing bugs, see File effective bug reports. I may repeat some of the info covered by that article, but only where I think it’s particularly important. After filing a bug report, please include the bug number in your DevForums post. Feedback Assistant shows the bug number in both the bug list and the bug detail view. Bug numbers start with FB and continue with a sequence of digits. For example, a recent bug report posted here on DevForums was FB11357055. Including the FB prefix avoids any confusion as to what type of bug number this is. Occasionally you’ll see other types of bug numbers. In release notes they are just in parens, so (99071807), and in DTS documents they have an r. prefix, so (r. 99071807). These are Radar numbers. Radar is the internal bug system here at Apple. Other developers can’t see your bug report. However, posting the bug number is still important for a couple of reasons: It allows Apple folks to quickly track down your issue. If another developer wants to file a related bug, they can reference your bug number in their bug report. You can share bug reports with other members of your team. For details on how to do that, see Collaborating with your team on the Developer > Bug Reporting page. Otherwise you can’t see a bug report filed by another developer, or one filed internally at Apple. One option here is to file your own bug and request that it be marked as a duplicate of the original bug. You’ll then be notified when the original bug is closed. The File effective bug reports article discusses the importance of including a sysdiagnose log with your bug report. I have a few additional tips: Include a sysdiagnose log from the machine that’s having the problem. Sometimes I see folks with an iOS problem include a sysdiagnose log for their development Mac )-: Include a sysdiagnose log even if you attach a test project that reproduces the problem. The contents of the log help with screening, making sure that your bug gets to the right person quickly. And that person will be very grateful to have your test project! If multiple machines are involved — for example, you’re reporting a Handoff problem — include a sysdiagnose log from each machine. Trigger the sysdiagnose log as soon as possible after you see the problem. The sooner you trigger the log, the more likely it is to capture relevant info. If the problem is hard to reproduce, see Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem for hints on how to capture an actionable sysdiagnose log. If you install a debug profile, install it before you reproduce the problem. These profiles typically enable more logging, and you want that logging to be active at the time of the problem. Most profiles activate immediately but some require that you restart. Follow the instructions that came with the profile. When reproducing the problem, make a rough note of the time and include that in your bug report. This doesn’t have to be super precise. Just note down the time, with seconds, shortly after you reproduce the problem. If the bug involves a crash, reproduce the crash outside of Xcode and then take your sysdiagnose log. This means running your code as the user would, so running an app from the Finder on macOS, running an app from the Home screen on iOS, and so on. If you reproduce the crash inside Xcode, the Xcode debugger catches the crash and prevents the system from generating a crash report to include in the sysdiagnose log. File focused bug reports. Imagine you’re seeing two problems, A and B, related to the same API. Don’t file a single bug that covers both A and B. Rather, file separate bugs for A and B. Feel free to reference your A bug in your B bug, and vice versa. Finally, some personal notes: DevForums is not an official support channel. Mentioning a problem here is not the same as filing a bug about it. That’s true even if you’re discussing your issue with an Apple person. Apple is a big company, and it’s very unlikely that the person you’re talking to is directly responsible for fixing your bug. Historically I used to post a lot of Radar links, of the forms rdar:nnn, where nnn includes the bug number. I no longer use these links because I’ve found that they confuses folks. They click the link and wonder why it does nothing. If you post an FB number here, DevForums automatically turns it into a link. However, that link is only useful to you. Other folks can’t access the bug via that link. I’ve filed a bug against DevForums requesting that it only generate this link for the bug’s originator (r. 92946014). In the meantime, I work around this by putting FB numbers in code style, which disables this link generation. If you want to share bug information outside of DevForums, one popular option is Open Radar (https://openradar.appspot.com/). Apple uses a lot of open source and many open source projects maintain their own bug tracker. Two big examples are Swift and WebKit. If your bug originates in such an open source project, consider filing it in the project’s bug tracker. You can then go on to submit a pull request with the fix (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com" Revision History 2025-08-07 Updated “Developer Technologies & SDKs” to “Developer Technologies & Resources”. 2024-03-07 Made minor editorial changes. 2023-10-26 Added a link to Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem. Added a recommendation to file focused bug reports. 2023-06-28 Updated the advice on how to file an API-level bug based on recent changes to Feedback Assistant. Corrected some link titles. 2023-03-21 Added a bunch of bullets to the personal notes section. 2023-03-13 Extended the discussion of seeing other folks’ bugs to make it clear that you can’t see bugs filed internally at Apple. 2022-12-13 Added advice about the “Something else not on this list” option. 2022-09-01 Added a personal notes section at the end. Added a new bullet in the sysdiagnose section about running your app outside of Xcode. Made other minor editorial changes. 2022-08-29 Added a note about filing duplicate bugs. 2022-08-24 First posted.

Sehr geehrtes Apple-Team, ich bin seit mehreren Jahren aktiver Teilnehmer am Public Beta-Programm und habe in dieser Zeit zahlreiche Feedbackmeldungen über die Feedback Assistant App eingereicht – teils mit ausführlicher Fehlerbeschreibung, Screenshots oder systematischer Reproduktionshilfe. Leider bleibt bei mir als Nutzer der Eindruck zurück, dass dieses Feedback ins Leere läuft. Viele meiner Meldungen stehen seit Jahren im Status „Offen“, ohne jegliche Rückmeldung oder sichtbare Bearbeitung. Auch wenn mir bewusst ist, dass eine individuelle Antwort nicht vorgesehen ist, fehlt mir zumindest eine Bestätigung, dass das Feedback angekommen ist, bewertet wurde oder an die zuständige Stelle weitergeleitet wurde. Ich wünsche mir als engagierter Tester mehr Transparenz im Umgang mit unseren Rückmeldungen – sei es durch eine automatische Eingangsbestätigung, eine grobe Statusanzeige (z. B. „dupliziert“, „weitergeleitet“, „behoben in Version XY“) oder gelegentliche Hinweise, wie viele Probleme durch die Community-Beiträge erkannt und gelöst wurden. Diese kleine Form der Anerkennung würde die Motivation vieler freiwilliger Tester stärken und das Vertrauen in den Prozess erhöhen. So wie es derzeit gestaltet ist, entsteht eher das Gegenteil: Frustration, Zweifel am Nutzen des Feedbacks und damit auch weniger Bereitschaft, zukünftige Probleme zu melden. Ich hoffe sehr, dass Sie diese Anregung intern weitergeben – auch im Sinne der langfristigen Qualitätssicherung Ihrer Software. Vielen Dank. Mit freundlichen Grüßen Christian Dear Apple Team, I have been an active Public Beta tester for several years and have submitted many reports via the Feedback Assistant – often with detailed descriptions, reproduction steps, and screenshots. Unfortunately, from a user’s perspective, it feels like this feedback disappears into a black hole. Most of my reports remain marked as “Open” for years, without any indication of review or resolution. I understand that individual responses are not part of the process, but there is no confirmation that feedback is received, reviewed, or forwarded internally. As a committed tester, I would greatly appreciate more transparency in the feedback process – for example, a short confirmation message, a basic status indicator (e.g., “duplicate”, “forwarded”, “resolved in version XY”) or even general updates about how user feedback contributes to product improvement. These small gestures would strengthen trust in the process and encourage ongoing contributions. The current silence, however, tends to demotivate testers and raises doubts about the usefulness of reporting bugs at all. I hope you will consider this suggestion and possibly forward it to the responsible internal teams. Sincerely, Christian

Although it doesn't seem to be a forbidden practice, placing toolbar items in the bottom bar of a modal Sheet (which has its own NavigationStack) triggers massive layout warnings. The same thing occurs when using the .searchable(...) view modifier inside a Sheet (which affects the bottom bar too). LayoutWarning.txt

While I was submitting a new feedback today for an iPhone/iPad storage issue, I saw a new log called “iOS storage log”. I could find no reference to this when I searched online. It made me wonder if it was new and if it contained personal data? Most of us only have one device, with all our personal data. Therefore, I’d appreciate any input on what personal data these logs contain.

When anyone calling through cellular call first calls don’t show or call notifications in screen even didn’t play ringtone . but if caller calling second time then ringing tone play properly. this problem happen my iphone 15 pro .128gb im from india . )

I submitted a Feedback (FB17843422) on Monday evening after the keynote about Tahoe beta 1. At the time it still wasn't listed in the "What build does the issue occur on?" dropdown. I selected "I'm not sure" instead hoping I could update it later but as far as I can tell that isn't the case since "Add more information" only lets me add additional comments. Is there some way for me to do that or is it even necessary?

I'm running macOS 15.5. I now have Xcode 26 and I'm testing my iOS app against iOS 26. I've encountered several UIKit / iOS 26 bugs I'd like to report. In Feedback Assistant I choose "Developer Technologies & SDKs". Eventually I get asked "What build does the issue occur on?". The list of choices is: iOS 18.2 Seed 4 iOS 18.1.1 iOS 17.7.2 An earlier iOS build I'm not sure So how to I report this as an iOS 26 beta 1 issue?

Hello Apple Team, Thank you for the recent Group Lab and for your continued work on advancing Xcode and developer tools. I’d like to submit a feature request: Are there any plans to introduce support for Agentic AI Mode (MCP protocol) in future versions of iOS or Xcode? As developer tools evolve toward more intelligent and context-aware environments, the integration of agentic AI capabilities could significantly enhance productivity and unlock new creative workflows. Looking forward to your consideration, and thank you again for the excellent session. Best regards

Dear Apple,I'm an iOS developer and provided feedback in the good old online bug tracker for many years.Decent conversations with Apple egnineers often resulted in bug fixes or updated documentation.The fact that my contributions helped to improve the products was rewarding.So I kept adding reports in the new Feedback Assistant app in macOS Catalina.But ever since (September 2019) I never ever got any response on any ticket.1 month ago I even added a report if Apple even read my reports. Again, no response ever since.So my question on this forum: Is Apple actually reading reports in the new Feedback Assistant?This can either be answered by Apple, or by other Developers that hopefully did response feedback from Apple. Or did not.Best regards,Martijn

Hello Apple community ! Not here to report an issue but I just wanted to make a suggestion ^^ I feel like a common frustration amongst developers is the lack of transparency over bugs filed on developer tools, SDKs, iOS versions, the whole Apple ecosystem really. This leads to the creation of parallel bug tracking tools (https://github.com/feedback-assistant/reports?tab=readme-ov-file / https://openradar.appspot.com/page/1) or filing of duplicates for reports that may already exist and are being worked on. I feel like this would save time for both external developers that encounter bugs & Apple engineers that have to look for possible duplicates to share a common public database of issues. Other companies have this kind of system in place (Google for example : https://issuetracker.google.com/) so why not Apple ? Thank you

As I've more verbosely asked at apple.stackexchange.com/revisions/479121/1#:~:text=Screenshot-,Screenshot,-I%20am%20able, when reporting feedback for an application installed via TestFlight, which of Feedback Assistant's "Third-Party Apps"'s "Something else not on this list" or "TestFlight" categories are superior? I ask primarily because applications installed via TestFlight are not enumerated there. However, also because via Feedback Assistant, I can provide significantly better feedback than I can on TestFlight, because of its undermentioned attributes: I can provide follow-up information as I gain more, and correct old information. It provides draft functionality, in case I need to take some time to create an actionable report. I can upload more information, like multiple screenshots and other file types.

How to report a bug says "With Feedback Assistant available on iPhone, iPad, Mac, and the web, it’s easy to report issues you encounter". The Feedback Assistant User Guide says "Tell Apple about your experience with beta or seed releases". Is Feedback Assistant only intended for reporting bugs in beta software? A year ago I reported a bug in Xcode 14 and now I'm being asked to verify this issue with Xcode 16 Beta 3. I'm not a beta tester and I don't want to install beta software. How should I proceed?

So, I was attempting to rename my Finder Tags. Unfortunately, I’m also trying Apple’s Intelligent Writing Tools to proofread it, but I’ve encountered a bug in it. Here’s an example: For reference, my macOS version is macOS Sequoia 15.3.2 (24D81)—a stable version. I hope that bug is fixed soon.

I received an email from Apple saying they couldn't auto-renew my developer subscription, due to a "billing error." I went in and deleted my lone payment method (which looked up-to-date), and created a new one for the same credit card in my developer account for billing. All the information appears correct. I've downloaded the Developer app, where it tells me my developer subscription is good through next month. There's a Renew button underneath. If I click on it, an alert says either "Unknown Error" (first time after launching), or it says "Unable to Continue. Please ensure your device and iCloud account meet our system requirements. Visit https://developer.apple.com/support/app-account/" (subsequent times). These are near-useless error messages. Which doesn't sound like a billing error. I don't pay anything for an iCloud account, nor wish to use an iCloud account. I'm running System 12.1 on my M1 MacBook Pro. After an hour of talking with three different humans at 1-800-MY-APPLE, they couldn't help, basically giving up and telling me to go to developer.apple.com/support/technical. But that's for submitting a TSI (Technical Support Incident) for my own needs as a developer, not for Apple's uninformative software. All I want to do is renew my developer subscription. Something's obviously wrong, but the automated system isn't providing enough information to continue, and the humans at the other end of the phone don't have enough information to help. The last guy I talked with threw up his hands, apologizzed, and then wished that I have a "good day." Any suggestions?

I've been getting this error when opening TestFlight since this morning. I tried restarting the network, re-install testflight, updating my iPhone, and re-logging with my Apple ID. This error prevents me from installing or updating all apps linked to my account, so I don't think it's related to a particular app permission.

Issue description: Using Xcodebuild command to build a project using Xcode 16.1 and 16.2, getting multiple device simulator warnings with same os and same model. Please see issue: https://github.com/actions/runner-images/issues/11036 Repro steps: create a Xcode project, build it using below command with Xcode 16 version. run: | echo "Building project manually..." xcodebuild -workspace MyApp.xcworkspace -scheme MyApp -destination 'platform=iOS Simulator,name=iPhone 16 Pro,OS=18.2' build | xcbeautify --renderer github-actions