SiriSearchFeedback crashing 30 times per day for over a year, Siri completely broken - tried everything Hi, I have been dealing with a persistent Siri bug for over a year across two different iPhones (15 Pro then 16 Pro) and I cannot find a fix anywhere. The symptom is simple : Siri does not work at all. When I check Settings > Privacy > Analytics > Analytics Data, I see around 30 SiriSearchFeedback .ips crash files generated every single day. The bug_type is 313, which points to the parsecd daemon crashing in a loop, preventing Spotlight indexing and Siri from functioning. What I have already tried, all without success : Full restart Toggling Siri and Search settings for every app Disabling and re-enabling Suggest Apps Before Searching Temporary language switch (French to English and back) Deleting Siri and Dictation history from Apple servers Signing out of iCloud and back in Full factory reset, set up as new iPhone with no backup restored Switching to a new device (15 Pro to 16 Pro) The key point : the bug always comes back the moment I sign back into my Apple ID. This makes me think the corruption is stored server-side and synced back automatically with every login. Has anyone solved this permanently ? Is there any way to fully wipe Siri or Spotlight data on Apple's servers beyond the standard Dictation history deletion ? Any help appreciated.

Preview doesn't show summaries of highlights anymore. It also adds my name to each new highlight although I've chosen not to add name to annotations

There seems to be an error with a code checkpoint in Swift Playground "getting started with apps" It says to put a VStack inside an HStack and shows how to do it. my screen looks the same but it is not getting marked as correct which is preventing me from moving on. Any Ideas?

Hi, I am Nilay Ranjan I created an App named EDUcopedia. I created this app on Android Studio aligned with Firebase. But now that I have to publish it on App Store. I am unable to convert the codes to Xcode. Please respond!

Dear Team, Can you please check and confirm for this security Google Threat Intelligence Group (GTIG) has identified a new iOS full-chain exploit that leveraged multiple zero-day vulnerabilities to fully compromise devices. Based on toolmarks in recovered payloads, we believe the exploit chain to be called DarkSword. Since at least November 2025, GTIG has observed multiple commercial surveillance vendors and suspected state-sponsored actors utilizing DarkSword in distinct campaigns. These threat actors have deployed the exploit chain against targets in Saudi Arabia, Turkey, Malaysia, and Ukraine. https://cloud.google.com/blog/topics/threat-intelligence/darksword-ios-exploit-chain?hl=en

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.

I have a very important voice memo that I have recorded on my iPad, as I was recording it, it seemed to have completely worked, but for some strange reason the voice memo will not play, download to my filess, I am unable to send it to anyone, and it basically just pops up blank every time I just try to share it. I cannot listen to it and have not been able to listen to it. This is the same on both my iPad and my phone, when I went to Apple, they said to come on here and ask for guidance, and that it might be because my regular iPhone is updated normally but on my iPad, which was the Voice Memo was recorded on is updated To beta. please give me some advice and if there’s any way, I could recover even the transcript of the voice message because it is truly so important to me. The sound waves are there and everything and I just don’t understand why it will not play on either device. I have also tried copying it. I have also tried trimming the beginning and it’s like the data is there, but it will not play.

Any idea when will the results of Swift Student Challenge be declared?

Hardware: • Mac Studio (M1 Ultra) • Apple Silicon • Sufficient free disk space (~35GB+ available) • SIP enabled • 4 local Time Machine snapshots present Current System: • Already running macOS Tahoe beta • Attempting upgrade to macOS Tahoe 26.4 Beta (Build 25E5207k) Primary Issue: Software Update downloads successfully, then moves to “Preparing…”. It stalls at “About 5 minutes remaining” for ~10–15 minutes and fails with: “Failed to prepare the software update. Please try again. An error occurred while downloading the selected updates.” The error appears network-related, but download always completes. Observed Behaviour: • “Checking for Updates” completes in <3 minutes. • softwareupdated and mobileassetd CPU usage <1%. • softwareupdate --history shows no record of the failed beta install. • No excessive system load or obvious disk pressure. Steps Already Attempted: 1. Standard Software Update retries • Multiple download/retry cycles from System Settings. • Same Preparing failure every time. 2. Permissions / Disk Access • Granted Terminal Full Disk Access. • SIP remains enabled. • Some system-protected locations still return “Operation not permitted”. 3. Cache / State Cleanup Attempts • Removed /Library/Updates/*. • Cleared temporary softwareupdate folders under /private/var/tmp. • Attempted MobileAsset cache cleanup where permitted. • Killed softwareupdated and mobileassetd processes (auto-restarted by launchd). 4. Beta Channel Reset • Turned Beta Updates OFF in System Settings. • Rebooted. • Re-enabled Beta Updates. • Forced catalog refresh via softwareupdate -l. 5. Snapshot Check • tmutil listlocalsnapshots / shows only 4 snapshots (normal range). 6. Full Installer Workaround softwareupdate --list-full-installers shows: • macOS Tahoe Beta 26.4 (25E5207k) • Tahoe 26.3 / 26.2 / 26.1 • Sequoia / Sonoma / Ventura / Monterey installers Downloaded installer via: softwareupdate –fetch-full-installer –full-installer-version 26.4 Installer downloaded correctly: /Applications/Install macOS Tahoe Beta.app 7. startosinstall Method (Apple Silicon optimized) Attempted install with: sudo “/Applications/Install macOS Tahoe Beta.app/Contents/Resources/startosinstall” –user –agreetolicense –nointeraction –forcequitapps –rebootdelay 30 –passprompt Authorization succeeds, installer begins preparing, but installation still ultimately fails. Additional Notes: • CPU usage remains low during failure. • No excessive snapshot count. • Error messaging consistently references download/network even though download completes. • Issue appears to occur during cryptex/asset preparation phase rather than initial download. Question for Apple / other developers: Has anyone else seen Tahoe 26.4 beta fail specifically during the Preparing phase on Apple Silicon (especially Ultra-class chips)? Looking for confirmation whether this is a known MobileAsset or cryptex staging issue, or if logs indicate a deeper APFS / volume-owner authorization problem.

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.

as of now I think it's not possible to have multiple .searchable lists in the same view. can someone confirm? or is there a known workaround? I'd had expected, that the search field would offer: in which list do you want to search. Because it doesn't it gives a fatal crash but maybe there's a workaround? thinking of: attach .searchable only on focus of the relevant list?

Hi all, Has anyone else experience review bombs and how effective was Apple at remedying it? In my case there is zero guidance and zero substantive insight by Developer support how I can effectively remedy a dishonest/bad-faith review attack on my application by a competitor. What are the criteria or guidelines for assessing an ‘attack’ under Apple Media Services Terms of Service section M? And the same for ‘bad-faith‘ and ‘dishonest‘ reviews? In my case I had an encounter on Reddit with somebody threatening to review bomb me, explaining to me how they knew how to bypass the Apple review system, and critiquing my app with specific comments. On that same day I received a 1 star review including exactly the same ‘critiques‘ that the Redditor gave me, written in German instead of English. Who here wants to guess the nationality of the Redditor? Before I received the review I had already notified Apple of the fact that I had this interaction and I was expecting a review bomb. I explained the explicit intention and the bad faith. I have set out all the evidence in emails to Apple, including links to the Reddit thread, that the reviewer and redditor use literally the same tends to describe my app, the timing, the circumstances, and so on. Apple provides me nothing in terms of concrete assessment except for telling me two different things in order for reviews to qualify to be removed: Reviews must be spam, attacks or hate speech Reviews must be offensive or factually inaccurate I had argued with concrete evidence that it was na attack. The review is also factually inaccurate. But this review procedure keeps moving the goalposts. Is there anyone at Apple who moderates / manages the assessment of these reviews when they’re reported to Apple? I’d be happy to have a call about this. After all, in a case like this where somebody explicitly threatens somebody with a review bomb, and is then review bombed with overlapping terms, language etc, then it makes you wonder if the assessment is effective at all.

Dear Apple Support, I would like to raise a concern regarding the behavior of the “Desktop & Documents Folders” feature in iCloud Drive. From a business and development standpoint, the fact that folders may be automatically moved or created without clear and explicit user awareness is quite concerning. File system behavior is something users generally expect to remain predictable and fully under their control. In particular, when working in development environments, even small and unintended changes to folder structures can lead to issues such as broken file paths, build errors, or inconsistencies in project setups. The possibility that such changes may occur automatically introduces an element of uncertainty that is difficult to manage in professional workflows. Additionally, there are security considerations. For example, if sensitive files such as configuration data or API keys are temporarily stored on the Desktop, the possibility that they could be unintentionally synced to the cloud raises valid concerns. Even if safeguards exist, the lack of clear visibility and explicit confirmation makes it difficult to confidently assess and manage risk. Overall, the current behavior gives the impression that folder operations may occur without sufficient transparency. From a business perspective, this impacts trust, predictability, and operational reliability. I would appreciate consideration of the following improvements: Clear and explicit communication before any folder movement or creation occurs A strictly opt-in model with unambiguous user consent Greater visibility into when and how synchronization affects local files Options to ensure fully local control over specific directories Thank you for your attention to this matter. I hope this feedback will contribute to improving the reliability and transparency of the feature. Sincerely,

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?

noticed that when I use PHPickerViewController in iOS26, preselectedAssetIdentifiers not working. It doesn't pre-select an image. This is the code snapshot how I use it with UIViewControllerRepresentable Same code works in iOS18 but not iOS26 func makeUIViewController(context: Context) -> UIViewController { var configuration = PHPickerConfiguration(photoLibrary: PHPhotoLibrary.shared()) configuration.filter = .images configuration.selectionLimit = 5 configuration.preselectedAssetIdentifiers = ["some id from previous selected results"] let imagePicker = PHPickerViewController.init(configuration: configuration) imagePicker.delegate = context.coordinator return imagePicker }

This is a generic, non-developer related macOS issue, but reporting here as well so it has more visibility since. It is an embarrassing bug that has not been fixed since the earliest versions of macOS Tahoe. Issue description: When Dock Magnification is enabled, the Dock Folder abruptly jumps approx. 10-15pixels down as the user moves the cursor after a brief pause). Video about the issue (see the last second of the small video and observe the entire grid popup jump abruptly): https://forums.macrumors.com/threads/macos-tahoe-26-4-release-candidate-now-available.2479503/post-34494643 Related FB: FB20761846 (opened in October, 2025) The issue is easily reproducible and confirmed by many. The lack of this issue being fixed for so long is indicative in the eyes of many of the lack of attention to details in macOS Tahoe's Glass interface.

My iphone freezes during the night, having the alarm not go off, me miss important things as I oversleep. And the phone needs to go thru hard reboot to get back to normal. It´s only been happening after I started using "Downtime". (An underdeveloped feature by Apple in the first place). I love locking my apps down nighttime for less screentime. Annoyingly it only happens once in a while, so I´m not able to link it directly to downtime consistently. I´m not developing an app right now so I´m steep ground with this post, but, with lack of sleep as this has messed up my sleep rythm several times, well I´m not able too anyway. I know ios well, and there isn´t much "to do" except having to always remember to turn off downtime (it doesn´t play well with shortcuts app either), but I hope someone from apple sees this and is able to push this bug into the right team as all reports I have seen goes on focus modes bugs, but not "downtime".

I have an app with multiple Windows, but hardly any "input" field. I want to control certain stuff via Menu (FocusedValues / FocusedKeyValue)... first I thought: this does not work at all... then I figured: If I write in a text field something.. then the focus is clear and the proper windows is targeted.. Just bringing the other window to focus (no edit nothing, just clicking on the window header) does not seem to trigger "hey.. I'm the focus now"... anyone experiencing the same? could I "fake" that? thinking of putting a very small text field so when I focus a windows, I could like, don't know: focus that input field such that the menu command realises: ah.. here's the windows I need to talk to...

Hey there! Faced a strange problem. We're a board game publisher, not quite experienced in publishing digital applications. However one of our games needs a digital app that already exists in AppStore. It is not possible to localize it ro our language, so we agreed with Rights Owners that we will develop the localized version ourselves and publish it in Store. The localized App is quite different from the original one: not only language, but a whole new part of the game exists. However Apple keeps declining our App considering it a spam. We tried everything to put that into consideration, but got nothing. Any lifehacks how to get this going? Is there anything they look at in particular, any tips what can we change quickly to finally publish the App?

Has anyone been able to raise a ticket with the support team in the past 48 hours without getting an infinite loader or error on the page?