Explore the integration of web technologies within your app. Discuss building web-based apps, leveraging Safari functionalities, and integrating with web services.

All subtopics
Posts under Safari & Web topic

Post

Replies

Boosts

Views

Activity

Persistent Deceptive Website Warning on Safari and iOS – Request for Apple’s Assistance (mamvid.com)
Hello Apple Developer Community, I am looking for assistance with a persistent false positive security warning affecting my company’s website: https://mamvid.com/. I am the owner and administrator of MamVid Soluciones, a software development company based in Bolivia. Background The issue originated from a demonstration application hosted on a subdomain (demotiktok.mamvid.com). It was developed to demonstrate a sales registration system related to sales generated through TikTok, not to impersonate TikTok or collect users’ credentials deceptively. After receiving a phishing report, we immediately discontinued the subdomain and permanently removed all related content. Actions taken to resolve the issue We contacted the security providers involved and obtained the following confirmations: Fortra (PhishLabs): Confirmed that the phishing flag was successfully removed. Fortinet: Reviewed our domain and officially changed its classification to Information Technology on November 17, 2026. VirusTotal: The domain currently appears clean, with no remaining detections. Current problem Despite resolving the original issue, Apple continues to display the following warning: “This website was reported as deceptive by Apple.” The warning appears when accessing our website from both iPhone and iPad, using Safari and Firefox. We have submitted multiple review requests through Apple’s official website review portal: https://www.websitereview.apple.com/ Unfortunately, the warning remains, and we have not been able to resolve the issue through that process. Request for assistance I would appreciate guidance from Apple engineers or community members who have experienced a similar situation. Is there another channel to request a manual review of a website flagged by Apple’s security systems? Could this warning persist independently of other security providers’ classifications? Is there any additional procedure to request removal of an outdated or incorrect deceptive website classification? This false positive is seriously affecting our company’s reputation and legitimate business operations. We are willing to provide the correspondence from Fortra and Fortinet, VirusTotal results, and screenshots of the warning. Thank you for any guidance or assistance. Best regards, Cristiam Mamani Vides Owner / Administrator – MamVid Soluciones https://mamvid.com/
Topic: Safari & Web SubTopic: General
0
0
23
3h
(Air)Printing from JavaScript in Safari?
Is there any documentation or advice on printing from a Safari webapp (in JavaScript)? My app needs to print labels, and printing from Safari presents few options. For example, you can't turn off backgrounds or the URL/date/time footer. And it wants to print a full-size page, which ends up printing miles of label. (I've also tried printing from SwiftUI on a macOS app, and even that is just terrible to try to get right. Why is printing so hard?)
1
0
1.1k
7h
Domain blocked across Apple services (Safari, Mail, Apple Business) since April 2026, clean everywhere else
Our webshop hardwarewalletonline.nl has been blocked by Apple since around April 2026. Since then, our revenue from Safari users has dropped by about 85%. What we see: Safari shows “This website was reported as deceptive by Apple” on every page, with and without www. Our identical English site www.hardwarewalletonline.com (same WordPress installation, same server, same CDN) is not flagged. Apple does not deliver email to @hardwarewalletonline.nl. An Apple Business verification code never arrived, and our mail logs show no delivery attempt from Apple. The same code sent to another domain of ours, with the same mail setup, arrived instantly. Apple Business rejects adding hardwarewalletonline.nl as a domain (“The URL you entered is incorrect or uses an unsupported format”). Our .com, .de and goedeshampoo.nl were accepted. macOS shows a security warning when pasting text containing the domain. The domain is clean in Google Safe Browsing, Google Search Console, VirusTotal (0/92) and SURBL. It does not imitate any brand: it is our own shop, with our own company details and a physical warehouse in the Netherlands. Already done: “Report an error” from the Safari warning page, websitereview.apple.com, reportphishing@apple.com, and a case through Apple Business support. No response so far. Could someone at Apple route this to the team responsible for the Safari Fraudulent Website Warning list? We can provide any verification needed.
Topic: Safari & Web SubTopic: General Tags:
0
0
25
13h
Safari flags four company domains across two servers as fraudulent: diagnostic and escalation path?
I develop products for VelikSoft Limited and have an active Apple Developer Program membership. Safari displays Fraudulent Website Warnings for four company-owned domains that we believe are false positives. Domains and IPv4 addresses checked on October 17, 2026: veliksoft.com - 77.110.106.89 tizigo.net - 77.110.106.89 vstranslate.net - 77.110.106.89 translatorphone.com - 94.228.163.126 The first three share a server. The newer translatorphone.com was placed on a different server and IP, but also received the warning shortly after launch. A shared IP alone therefore cannot explain all four warnings. The classification provider and trigger remain unknown. The latest site is an informational translator-device project website, with no EXE downloads. Its homepage serves HTTPS with HTTP 200; www redirects to the same domain. A limited check of homepage references and the primary application script found local assets and interface interactions, without an executable download or automatic redirect to the old server. This is not an exhaustive security audit. It identifies VelikSoft Limited and links to our company site. Chrome opens it normally on this Mac. Earlier checks of the older domains using Search Console and independent security services did not explain the Safari warnings. These historical checks are not current verdicts for the newer domain. We already submitted Website Review requests multiple times and Feedback Assistant report FB24448660. Apple Developer Support case 102967798534 records contact events on September 19, September 30 and October 1, 2026. As of October 17, we have no substantive explanation or resolution. Telephone support is not a usable option for us. Can an Apple engineer or a website owner who resolved a comparable issue advise: How can we identify whether the warning comes from Apple, Google Safe Browsing or another provider? Is there an owner-accessible diagnostic identifying the affected URL and reason? Which escalation path works when Website Review and an existing support case have not produced a substantive response? Can the existing case and FB report be routed for a manual review of all four domains? If you resolved this, what evidence and contact channel actually led to a review? Reproduction: open one of the affected HTTPS domains in Safari with Fraudulent Website Warning enabled; the red warning appears instead of the site. Safari 26 on macOS has been affected. I can provide exact current version details and further evidence through the support case if requested. I am seeking an investigation and correction of any mistaken classification, not instructions to disable protection or bypass warnings.
Topic: Safari & Web SubTopic: General Tags:
1
0
629
1d
Web Browser Public Key Credential Requests capability request pending since 27 Oct
I build a Chromium-based web browser for macOS. It's signed with Developer ID, notarized and distributed outside the Mac App Store. On 27 October I requested the managed capability Web Browser Public Key Credential Requests (com.apple.developer.web-browser.public-key-credential) for my App ID. On the App ID's Capability Requests tab it still shows "Submitted", with no email since. I need it for iCloud Keychain passkeys, and so that Apple's iCloud Passwords browser extension can start its helper. Users are reporting that the extension doesn't work. Request ID: H543AX456N Developer Support case: 30000006313896 (they're administrative and suggested I ask here) My questions: is there anything else I should send for this review, and is there somewhere to follow up on a pending capability request? And once it's approved, will the capability be included in a Developer ID provisioning profile, or only in Mac App Store profiles? Thanks!
2
0
201
1d
Screen Time is incorrectly blocking a safe website as adult content
I’m the owner of actifinder mobile app. Apple’s Screen Time ‘Limit Adult Websites’ setting is incorrectly blocking our website, including the homepage. ActiFinder is an outdoor activities platform for hiking, cycling, kayaking, skiing, events and similar activities and does not contain adult content. I believe our domain has been incorrectly classified as adult content. I’d like to have actifinder.com reviewed and removed from the adult-content block/classification. Could you please escalate this to the team responsible for Screen Time web-content filtering/domain classification?
9
2
2.3k
3d
Supported archive formats for auto-extraction after download
After downloading a .zip file containing a .app bundle, Safari auto-extracts the .zip file (assuming the "Open safe files after downloading" preference is enabled, which it is by default) which leaves the .app ready to run in Downloads. .zip is not a very efficient archive format. We would like to use something better, but want to maintain Safari's auto-extract behavior. I've tested several other formats but found that Safari does not extract them: .aar(Apple Archive), .tar.xz, .txz. Is there any documentation on which formats Safari will auto-extract? Should anything other than .zip auto-extract?
Topic: Safari & Web SubTopic: General Tags:
0
1
352
1w
Website incorrectly blocked by Apple's adult content filter
Hi everyone, I'm hoping someone can help with an issue I'm having with Apple's Web Content Restrictions. I manage a legitimate fitness and wellness website, but some iPhone/iPad users are unable to access it when they have: Settings → Screen Time → Content & Privacy Restrictions → App Store, Media, Web & Games → Web Content → Limit Adult Websites enabled. They receive: Website Not Allowed The website is a restricted website. I've been able to reproduce the exact same issue myself by enabling this setting on an iPhone. The important point is that the website is not adult content whatsoever. It is a normal fitness/wellness website providing workouts, fitness programmes, nutrition guidance and related content. There is no pornography, sexually explicit content or adult services. I've also tested blank pages and different URLs associated with the site, and the restriction still occurs. Everything works normally when the Web Content setting is changed to Unrestricted Access. I've contacted Apple Support and Apple Developer Support but haven't been able to get the issue in front of someone who can review the website's classification. Does anyone know how to request a review or reclassification of a website that appears to have been incorrectly flagged by Apple's Web Content Filter? I'm not trying to bypass Apple's parental controls. I simply want to understand how a legitimate fitness website can be reviewed and removed from whatever classification is causing it to be blocked under Limit Adult Websites. Any advice from anyone who has dealt with this before would be hugely appreciated.
Topic: Safari & Web SubTopic: General
6
2
1.5k
1w
Safari Fraudulent Website Warning on anonumber.com: please explain the reason
Hello, Safari shows a "Fraudulent Website Warning" ("Apple reports this website as fraudulent") for https://anonumber.com. Google Safe Browsing reports no unsafe content for this domain, so the flag comes from Apple's own list. We have already submitted requests at websitereview.apple.com on October 23, October 30 and November 8, and emailed reportphishing@apple.com, but received no reply and the warning is still shown. anonumber.com sells virtual phone numbers for SMS verification when registering online accounts, mainly to SMM and marketing teams. The site does not impersonate any brand, does not ask for passwords, card details or personal data, offers no downloads and has no ads or third-party scripts. Terms and privacy: https://anonumber.com/terms We want to fix whatever triggered the warning. Could you please tell us: Why the site was classified as fraudulent (content, domain name, hosting provider or IP address)? What exactly we should change for the warning to be removed? Where we can follow the status of our review request? Thank you, Alex anonumber.com Feedback ID: FB25532938
Topic: Safari & Web SubTopic: General Tags:
0
0
80
1w
iPadOS 27 (24A435): Safari crashes (SIGABRT) on first focus of a web form field after process launch
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).
Topic: Safari & Web SubTopic: General
6
6
3.6k
1w
Some websites hang in Safari on iOS 26 over mobile data, while working on older iOS, Android and desktop
We are investigating intermittent loading failures affecting our websites on several iPhones running iOS 26 or later. The same sites open on our tested Android devices, desktop computers, and iPhones running earlier versions of iOS. In one case, Safari kept loading indefinitely over a Tele2 mobile connection with VPN disabled. On a second iPhone running iOS 26 or later, one of the applications also failed to load; we do not yet know the carrier or whether the website was tested separately in Safari. The same affected iPhones also cannot load our VK Mini Apps, which are hosted on the same servers as the websites. For one of the sites, we partially improved the situation by routing traffic through a proxy hosted with a different provider. On the same affected iPhones, the site then opened over Wi-Fi, but it still did not load over mobile data. During an earlier investigation of a similar failure, server-side packet captures showed incomplete TCP/TLS exchanges: some data did not arrive, or a server response was not acknowledged. That capture covered TCP only, so it did not rule out QUIC attempts or interactions between QUIC and TCP. We have not established where the packets were lost or whether all incidents share the same cause. We also observed intermittent, selective access failures to the same servers from a desktop using certain VPN connections, while unrelated sites remained accessible. It is not known whether this is connected to the iPhone issue. Has anyone seen similar behavior on iOS 26 or later over mobile networks? What client-side and server-side diagnostics would you recommend to distinguish routing, MTU, TCP/TLS, DNS, and HTTP/3 issues when the page does not load far enough to run application code?
0
0
227
1w
Behavior of User Verification of WebAuthn
I checked the behavior of WebAuthn on Safari14 beta3 using "webauthn.io". (I checked with an iPad mini4.) When "User Verification = discouraged", I have been verified the PIN code. (In this case it wouldn't need to confirm my PIN.) And in the "User Verification = preffered" case, same behavior as "discouraged". But when I chose "User Verification = required", it didn't verify my PIN code, and also the authentication itself didn't complete. (Same symptoms as safari13) I think this behavior is strange. Is it a bug?
Topic: Safari & Web SubTopic: General Tags:
1
0
559
1w
Persistent Deceptive Website Warning on Safari and iOS – Request for Apple’s Assistance (mamvid.com)
Hello Apple Developer Community, I am looking for assistance with a persistent false positive security warning affecting my company’s website: https://mamvid.com/. I am the owner and administrator of MamVid Soluciones, a software development company based in Bolivia. Background The issue originated from a demonstration application hosted on a subdomain (demotiktok.mamvid.com). It was developed to demonstrate a sales registration system related to sales generated through TikTok, not to impersonate TikTok or collect users’ credentials deceptively. After receiving a phishing report, we immediately discontinued the subdomain and permanently removed all related content. Actions taken to resolve the issue We contacted the security providers involved and obtained the following confirmations: Fortra (PhishLabs): Confirmed that the phishing flag was successfully removed. Fortinet: Reviewed our domain and officially changed its classification to Information Technology on November 17, 2026. VirusTotal: The domain currently appears clean, with no remaining detections. Current problem Despite resolving the original issue, Apple continues to display the following warning: “This website was reported as deceptive by Apple.” The warning appears when accessing our website from both iPhone and iPad, using Safari and Firefox. We have submitted multiple review requests through Apple’s official website review portal: https://www.websitereview.apple.com/ Unfortunately, the warning remains, and we have not been able to resolve the issue through that process. Request for assistance I would appreciate guidance from Apple engineers or community members who have experienced a similar situation. Is there another channel to request a manual review of a website flagged by Apple’s security systems? Could this warning persist independently of other security providers’ classifications? Is there any additional procedure to request removal of an outdated or incorrect deceptive website classification? This false positive is seriously affecting our company’s reputation and legitimate business operations. We are willing to provide the correspondence from Fortra and Fortinet, VirusTotal results, and screenshots of the warning. Thank you for any guidance or assistance. Best regards, Cristiam Mamani Vides Owner / Administrator – MamVid Soluciones https://mamvid.com/
Topic: Safari & Web SubTopic: General
Replies
0
Boosts
0
Views
23
Activity
3h
(Air)Printing from JavaScript in Safari?
Is there any documentation or advice on printing from a Safari webapp (in JavaScript)? My app needs to print labels, and printing from Safari presents few options. For example, you can't turn off backgrounds or the URL/date/time footer. And it wants to print a full-size page, which ends up printing miles of label. (I've also tried printing from SwiftUI on a macOS app, and even that is just terrible to try to get right. Why is printing so hard?)
Replies
1
Boosts
0
Views
1.1k
Activity
7h
Domain blocked across Apple services (Safari, Mail, Apple Business) since April 2026, clean everywhere else
Our webshop hardwarewalletonline.nl has been blocked by Apple since around April 2026. Since then, our revenue from Safari users has dropped by about 85%. What we see: Safari shows “This website was reported as deceptive by Apple” on every page, with and without www. Our identical English site www.hardwarewalletonline.com (same WordPress installation, same server, same CDN) is not flagged. Apple does not deliver email to @hardwarewalletonline.nl. An Apple Business verification code never arrived, and our mail logs show no delivery attempt from Apple. The same code sent to another domain of ours, with the same mail setup, arrived instantly. Apple Business rejects adding hardwarewalletonline.nl as a domain (“The URL you entered is incorrect or uses an unsupported format”). Our .com, .de and goedeshampoo.nl were accepted. macOS shows a security warning when pasting text containing the domain. The domain is clean in Google Safe Browsing, Google Search Console, VirusTotal (0/92) and SURBL. It does not imitate any brand: it is our own shop, with our own company details and a physical warehouse in the Netherlands. Already done: “Report an error” from the Safari warning page, websitereview.apple.com, reportphishing@apple.com, and a case through Apple Business support. No response so far. Could someone at Apple route this to the team responsible for the Safari Fraudulent Website Warning list? We can provide any verification needed.
Topic: Safari & Web SubTopic: General Tags:
Replies
0
Boosts
0
Views
25
Activity
13h
Safari flags four company domains across two servers as fraudulent: diagnostic and escalation path?
I develop products for VelikSoft Limited and have an active Apple Developer Program membership. Safari displays Fraudulent Website Warnings for four company-owned domains that we believe are false positives. Domains and IPv4 addresses checked on October 17, 2026: veliksoft.com - 77.110.106.89 tizigo.net - 77.110.106.89 vstranslate.net - 77.110.106.89 translatorphone.com - 94.228.163.126 The first three share a server. The newer translatorphone.com was placed on a different server and IP, but also received the warning shortly after launch. A shared IP alone therefore cannot explain all four warnings. The classification provider and trigger remain unknown. The latest site is an informational translator-device project website, with no EXE downloads. Its homepage serves HTTPS with HTTP 200; www redirects to the same domain. A limited check of homepage references and the primary application script found local assets and interface interactions, without an executable download or automatic redirect to the old server. This is not an exhaustive security audit. It identifies VelikSoft Limited and links to our company site. Chrome opens it normally on this Mac. Earlier checks of the older domains using Search Console and independent security services did not explain the Safari warnings. These historical checks are not current verdicts for the newer domain. We already submitted Website Review requests multiple times and Feedback Assistant report FB24448660. Apple Developer Support case 102967798534 records contact events on September 19, September 30 and October 1, 2026. As of October 17, we have no substantive explanation or resolution. Telephone support is not a usable option for us. Can an Apple engineer or a website owner who resolved a comparable issue advise: How can we identify whether the warning comes from Apple, Google Safe Browsing or another provider? Is there an owner-accessible diagnostic identifying the affected URL and reason? Which escalation path works when Website Review and an existing support case have not produced a substantive response? Can the existing case and FB report be routed for a manual review of all four domains? If you resolved this, what evidence and contact channel actually led to a review? Reproduction: open one of the affected HTTPS domains in Safari with Fraudulent Website Warning enabled; the red warning appears instead of the site. Safari 26 on macOS has been affected. I can provide exact current version details and further evidence through the support case if requested. I am seeking an investigation and correction of any mistaken classification, not instructions to disable protection or bypass warnings.
Topic: Safari & Web SubTopic: General Tags:
Replies
1
Boosts
0
Views
629
Activity
1d
Web Browser Public Key Credential Requests capability request pending since 27 Oct
I build a Chromium-based web browser for macOS. It's signed with Developer ID, notarized and distributed outside the Mac App Store. On 27 October I requested the managed capability Web Browser Public Key Credential Requests (com.apple.developer.web-browser.public-key-credential) for my App ID. On the App ID's Capability Requests tab it still shows "Submitted", with no email since. I need it for iCloud Keychain passkeys, and so that Apple's iCloud Passwords browser extension can start its helper. Users are reporting that the extension doesn't work. Request ID: H543AX456N Developer Support case: 30000006313896 (they're administrative and suggested I ask here) My questions: is there anything else I should send for this review, and is there somewhere to follow up on a pending capability request? And once it's approved, will the capability be included in a Developer ID provisioning profile, or only in Mac App Store profiles? Thanks!
Replies
2
Boosts
0
Views
201
Activity
1d
Screen Time is incorrectly blocking a safe website as adult content
I’m the owner of actifinder mobile app. Apple’s Screen Time ‘Limit Adult Websites’ setting is incorrectly blocking our website, including the homepage. ActiFinder is an outdoor activities platform for hiking, cycling, kayaking, skiing, events and similar activities and does not contain adult content. I believe our domain has been incorrectly classified as adult content. I’d like to have actifinder.com reviewed and removed from the adult-content block/classification. Could you please escalate this to the team responsible for Screen Time web-content filtering/domain classification?
Replies
9
Boosts
2
Views
2.3k
Activity
3d
Supported archive formats for auto-extraction after download
After downloading a .zip file containing a .app bundle, Safari auto-extracts the .zip file (assuming the "Open safe files after downloading" preference is enabled, which it is by default) which leaves the .app ready to run in Downloads. .zip is not a very efficient archive format. We would like to use something better, but want to maintain Safari's auto-extract behavior. I've tested several other formats but found that Safari does not extract them: .aar(Apple Archive), .tar.xz, .txz. Is there any documentation on which formats Safari will auto-extract? Should anything other than .zip auto-extract?
Topic: Safari & Web SubTopic: General Tags:
Replies
0
Boosts
1
Views
352
Activity
1w
Website incorrectly blocked by Apple's adult content filter
Hi everyone, I'm hoping someone can help with an issue I'm having with Apple's Web Content Restrictions. I manage a legitimate fitness and wellness website, but some iPhone/iPad users are unable to access it when they have: Settings → Screen Time → Content & Privacy Restrictions → App Store, Media, Web & Games → Web Content → Limit Adult Websites enabled. They receive: Website Not Allowed The website is a restricted website. I've been able to reproduce the exact same issue myself by enabling this setting on an iPhone. The important point is that the website is not adult content whatsoever. It is a normal fitness/wellness website providing workouts, fitness programmes, nutrition guidance and related content. There is no pornography, sexually explicit content or adult services. I've also tested blank pages and different URLs associated with the site, and the restriction still occurs. Everything works normally when the Web Content setting is changed to Unrestricted Access. I've contacted Apple Support and Apple Developer Support but haven't been able to get the issue in front of someone who can review the website's classification. Does anyone know how to request a review or reclassification of a website that appears to have been incorrectly flagged by Apple's Web Content Filter? I'm not trying to bypass Apple's parental controls. I simply want to understand how a legitimate fitness website can be reviewed and removed from whatever classification is causing it to be blocked under Limit Adult Websites. Any advice from anyone who has dealt with this before would be hugely appreciated.
Topic: Safari & Web SubTopic: General
Replies
6
Boosts
2
Views
1.5k
Activity
1w
Safari Fraudulent Website Warning on anonumber.com: please explain the reason
Hello, Safari shows a "Fraudulent Website Warning" ("Apple reports this website as fraudulent") for https://anonumber.com. Google Safe Browsing reports no unsafe content for this domain, so the flag comes from Apple's own list. We have already submitted requests at websitereview.apple.com on October 23, October 30 and November 8, and emailed reportphishing@apple.com, but received no reply and the warning is still shown. anonumber.com sells virtual phone numbers for SMS verification when registering online accounts, mainly to SMM and marketing teams. The site does not impersonate any brand, does not ask for passwords, card details or personal data, offers no downloads and has no ads or third-party scripts. Terms and privacy: https://anonumber.com/terms We want to fix whatever triggered the warning. Could you please tell us: Why the site was classified as fraudulent (content, domain name, hosting provider or IP address)? What exactly we should change for the warning to be removed? Where we can follow the status of our review request? Thank you, Alex anonumber.com Feedback ID: FB25532938
Topic: Safari & Web SubTopic: General Tags:
Replies
0
Boosts
0
Views
80
Activity
1w
iPadOS 27 (24A435): Safari crashes (SIGABRT) on first focus of a web form field after process launch
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).
Topic: Safari & Web SubTopic: General
Replies
6
Boosts
6
Views
3.6k
Activity
1w
Some websites hang in Safari on iOS 26 over mobile data, while working on older iOS, Android and desktop
We are investigating intermittent loading failures affecting our websites on several iPhones running iOS 26 or later. The same sites open on our tested Android devices, desktop computers, and iPhones running earlier versions of iOS. In one case, Safari kept loading indefinitely over a Tele2 mobile connection with VPN disabled. On a second iPhone running iOS 26 or later, one of the applications also failed to load; we do not yet know the carrier or whether the website was tested separately in Safari. The same affected iPhones also cannot load our VK Mini Apps, which are hosted on the same servers as the websites. For one of the sites, we partially improved the situation by routing traffic through a proxy hosted with a different provider. On the same affected iPhones, the site then opened over Wi-Fi, but it still did not load over mobile data. During an earlier investigation of a similar failure, server-side packet captures showed incomplete TCP/TLS exchanges: some data did not arrive, or a server response was not acknowledged. That capture covered TCP only, so it did not rule out QUIC attempts or interactions between QUIC and TCP. We have not established where the packets were lost or whether all incidents share the same cause. We also observed intermittent, selective access failures to the same servers from a desktop using certain VPN connections, while unrelated sites remained accessible. It is not known whether this is connected to the iPhone issue. Has anyone seen similar behavior on iOS 26 or later over mobile networks? What client-side and server-side diagnostics would you recommend to distinguish routing, MTU, TCP/TLS, DNS, and HTTP/3 issues when the page does not load far enough to run application code?
Replies
0
Boosts
0
Views
227
Activity
1w
Behavior of User Verification of WebAuthn
I checked the behavior of WebAuthn on Safari14 beta3 using "webauthn.io". (I checked with an iPad mini4.) When "User Verification = discouraged", I have been verified the PIN code. (In this case it wouldn't need to confirm my PIN.) And in the "User Verification = preffered" case, same behavior as "discouraged". But when I chose "User Verification = required", it didn't verify my PIN code, and also the authentication itself didn't complete. (Same symptoms as safari13) I think this behavior is strange. Is it a bug?
Topic: Safari & Web SubTopic: General Tags:
Replies
1
Boosts
0
Views
559
Activity
1w