When using a web page to upload from the camera roll. During selection everything is ok but after confirming the selection, its still possible to change the selection and if media is in a processing or downloading state its not obvious to a user what is going on. This results to a confusing user experience. It doesn't seem like theres any signal back to the page in this state, its just a poor camera roll picker which doesn't block selection changes or show any progress that something is happening (i.e. localising or processing for upload). Same result on Chrome and Safari

When I login to an account on a subdomain of a main domain, I want to be able to store a separate password for the same login id on the main domain account. This doesn't seem possible in the current Safari implementation.eg: domain.com is the main domain and is the general information site.my.domain.com is the subdomain that hosts the customer support.I want different passwords on each for the same login ID... Can't I do this?--marcel

Issue Description My Mac originally had macOS 26.2, and I updated it to macOS 26.6. After using Safari normally for 2–3 days, Safari suddenly crashed. After the crash, when I open Safari again, it sometimes launches as a new/empty Safari instance instead of opening my existing Safari profile. My bookmarks, history, tabs, and other Safari profile data are not available in this new instance. While investigating the issue, I found a folder under my Mac's Library whose name appears to be my Mac's serial number/hardware identifier. This folder contains Safari-related files. I believe this serial-number-named folder may be related to the problem. My concern is that this folder may be causing Safari to create or open another Safari instance/profile after Safari crashes. If this folder is incorrectly created or recreated, it may explain why a new Safari instance appears and why my original Safari profile is not loaded. I have already contacted Apple Support and tried the following: Created and tested with a new macOS user Tested in Safe Mode Cleared Safari cache and cookies and checked Safari Library data Restarted the Mac multiple times Reinstalled macOS Completely erased the internal drive Performed a fresh macOS installation Updated macOS to the latest available version The issue still occurs even after completely erasing the drive and performing a clean macOS installation. I am also currently seeing two different Safari icons/appearances on my Mac: one appears to be the newer macOS 27 Safari icon, while another appears to be the older macOS 26 Safari icon. Request to Apple Please investigate the serial-number-named folder specifically and determine: Why this folder is created. Which macOS or Safari process creates it. What its purpose is. Whether it is related to Safari profiles, containers, application registration, or Safari instances. Whether this folder can cause Safari to launch as a new/empty instance after a crash. Why the folder or related Safari state can appear again even after a completely clean macOS installation. Why two different Safari icons/appearances are currently present. I believe identifying the source and purpose of this serial-number-named folder may help identify the root cause of the Safari issue. I do not want to delete or modify this folder without Apple's confirmation because it may be a system-managed folder. Please investigate this as a possible macOS/Safari system-level issue and escalate it to the Safari/macOS engineering team if necessary. I can provide the exact folder path, screenshots, Safari crash reports, system logs, and Terminal output showing the Safari application locations and related folders.

Hi, We are experiencing an issue where Safari displays a “Deceptive Website Warning” when accessing our legitimate website: https://burbleonline.co.za The domain is owned and operated by a legitimate business and has been in use for several years. The website is an online printing/e-commerce platform. We have investigated the issue and so far: The website uses a valid HTTPS certificate. The certificate is issued by Let’s Encrypt and is currently valid. The domain is not newly registered. The website is operational and does not intentionally host phishing or deceptive content. We have checked the site and have not identified any obvious malicious redirects or injected content. Current third-party reputation checks do not show a broad consensus that the domain is malicious. One security reputation provider, SOCRadar, currently appears to classify the domain as malicious, which may be contributing to the warning. The website also uses standard third-party services such as Google Analytics/Tag Manager and Tawk.to. We would appreciate any guidance on how Safari’s fraudulent/deceptive website classification can be reviewed or corrected. In particular: Is there a way to determine why Safari is currently classifying this domain as deceptive? Is there an Apple-specific process for requesting a review/false-positive correction? If the classification originates from a third-party Safe Browsing or threat-intelligence source, does Apple automatically refresh this classification after the source is corrected? Is there anything specific we should check on the website or infrastructure to ensure it complies with Safari’s security requirements? We would be happy to provide additional technical information, URLs, screenshots, or verification of domain ownership if required. Thank you.

Hi, Safari shows a “Deceptive Website” warning for https://mim-kulinariya.com/. It’s a simple café menu with prices and contact details. No login, payments, personal data collection forms or tracking scripts. It’s hosted on GitHub Pages with a valid Let’s Encrypt certificate. I submitted a review request through websitereview.apple.com but have received no response at all. The warning discourages customers from visiting our website. Could someone from Apple please help expedite the review or explain how to escalate this? If a specific page or resource triggered the warning, please let us know so we can address it promptly. Thank you.

Summary On iPadOS 27.0 (build 24A435), MobileSafari crashes with SIGABRT the first time the software keyboard is brought up by focusing a form field inside a web page. It happens on any website that has a text input: we reproduced it on our own web app, amazon.co.jp, Yahoo! Mail, Gmail, Rakuten, X, and two Japanese public-sector sites. No login is required to reproduce. Environment Devices: iPad mini (A17 Pro / iPad16,2) x2, plus a third iPad (reproduced on 3 devices) OS: iPadOS 27.0 build 24A435 — both the public beta and the RC build (releaseType "User"). Also reproduces after a full erase + clean install, so it is not device-state related. NOT reproducible on: iPhone (iOS 27, same build 24A435), Chrome on the same iPads, or the Xcode 27 Simulator. Steps to reproduce (no login required) Launch Safari and open any page with a login form (e.g. the amazon.co.jp sign-in page). Without logging in, kill Safari from the app switcher (or background it and go to the Home Screen). Launch Safari again; the same page is shown. Tap any text field (ID / email / password) to focus it. Safari crashes immediately. The essential condition appears to be: the FIRST keyboard activation in a freshly launched MobileSafari process is driven by focusing a form field inside WKWebView. If the keyboard has already been built once in that process (see Workaround below), the crash never happens. Crash details We collected five .ips crash reports from three devices and two unrelated websites (our web app and amazon.co.jp). lastExceptionBacktrace is identical across all five, down to the instruction offsets, so page content is not a factor. Key frames: The exception is thrown by NSISEngine (CoreAutoLayout) while -[TUIKeyplaneView prepareForSplitTransition] removes layout constraints in an inconsistent state (this split-keyplane path is iPad-only, which explains why iPhone is unaffected). The re-entrancy: Safari's AutoFill metadata round trip (WBSAutoFillJavaScriptInjectionController -> _SFFormAutoFillController beforeStartInputSession: -> TabDocument _beginAutomaticPasswordInteraction:) calls -[UIResponder reloadInputViews] from -[WKContentView _continueElementDidFocus:requiresStrongPasswordAssistance:] while -[UIKeyboard activate] is still on the stack. In all five reports, a com.apple.root.utility-qos thread is blocked in DISPATCH_WAIT_FOR_QUEUE doing dispatch_sync onto the main queue from -[UITextChecker initGlobalsWithAsynchronousLoading:] (a once-per-process initialization). Four of the five crashes occurred 1–6 seconds after process launch. After the crash, Safari itself sometimes fails to launch until you do Settings > Safari > Clear History and Website Data. Already ruled out (all verified on device) Settings > Passwords > AutoFill turned OFF: still crashes Split keyboard setting turned OFF: still crashes Full device reset + clean install of the RC build: still crashes Site-side causes: reproduces on completely unrelated sites; the crash fires before any login/auth JavaScript runs, and no page code appears in the stack Workaround (reliable, verified) Focus Safari's own address bar FIRST, so the keyboard is constructed through a native text field without the asynchronous AutoFill round trip. After that, focusing web form fields works normally for the lifetime of the process. This workaround is unavailable in SFSafariViewController / in-app browsers, where the crash also reproduces. Questions Can anyone else reproduce this on iPadOS 27.0 (24A435)? Confirmations/boosts appreciated — we want to know how widespread this is before the public rollout. Is there any site-side mitigation (markup, autocomplete attributes, JS) that prevents Safari's AutoFill round trip from re-entering keyboard construction? Standard autocomplete attributes did not help in our tests. Is this a known regression being tracked for an iPadOS 27.x update? Is there any mitigation for SFSafariViewController-based in-app browsers, where the address-bar workaround cannot be used? Filed via Feedback Assistant: FBxxxxxxxx (five .ips crash reports attached there).

Hi! I've successfully uploaded my web extension using the Web Extension Packager. However, there was a build error. When I review the list of cloud builds and click "view issues" for the failed build, I get the message: "Exporting for App Store Distribution failed. Please download the logs artifact for more information." However, I can't find any link in the app store connect web UI for viewing the logs artifact for Web Extension Packager builds.

Hi everyone, I am new to this forum, and I have a question about Safari not displaying my .mp4 videos on my corporate website. This is probably an issue that has been posted before, but any help is welcome. I manage a major Travel portal, and I don't want to disappoint about 30% of my traffic coming in via Safari. Thanks in advance for any help or advice, -Paul

Safari displays a red “Fraudulent Website Warning” for my website q-saver.com. The warning has been present for more than 5 months. I have already submitted two requests through https://websitereview.apple.com/, but neither resulted in the warning being removed or any response. The website is a video downloading service. It does not impersonate Apple or financial services and does not ask for Apple IDs, banking credentials or other sensitive information. The only password it asks for is the optional password of a q-saver.com account; sign-in with Google or Telegram goes through their official OAuth pages, and payments are processed on the payment providers' own pages. The site used to show pop-under ads from third-party ad networks. They have been turned off (the last one on September 26, 2026), and the ad network code has been removed from the pages. On 27 September I submitted a new Website Review request. Google Safe Browsing reports no unsafe content for the site: https://transparencyreport.google.com/safe-browsing/search?url=q-saver.com The website works normally in Chrome, Firefox and Edge. In iOS in-app browsers (for example, Telegram) it does not open at all because of the warning. Is there an official escalation path for Safari's Fraudulent Website Warning classification when Website Review requests remain unresolved for several months? I can provide screenshots and technical information privately if required.