The "A problem repeatedly occurred on..." message in Safari on iPhones (like iPhone 11 Pro and iPhone 12) usually indicates a crash or incompatibility in how the webpage is loaded or rendered. This is often related to script errors, rendering issues, or resource conflicts that affect Safari's WebKit engine.
1. Check for Custom Code Errors
- If you've added custom code in the Page Settings or Site Settings > Custom Code, remove it temporarily and republish.
- Common culprits include:
- Malformed JavaScript
- Third-party scripts (e.g., trackers, widgets) that conflict with WebKit
document.write() usage, which can crash mobile Safari
2. Disable Legacy Interactions or Animations
- Excessive or complex interactions and animations (especially on page load or scroll) can trigger crashes.
- Try disabling interactions and testing the site.
- Look for large or nested
while scrolling in view animations or GSAP integrations.
3. Check Media Assets and File Formats
- Large or incompatible image formats (e.g., uncompressed TIFF, large GIFs, or improperly compressed WebP) can cause render errors.
- Video embeds or background videos might crash mobile Safari. If using MP4 videos, ensure they’re optimized for mobile playback.
4. Update or Test in Safari Technical Preview
- iOS Safari rendering might behave differently between versions. Ask users to update to the latest iOS.
- Use Safari Developer tools via Mac to inspect your Webflow site in a mobile simulator to identify offending code or layout issues.
5. Test on a Blank Webflow Page
- Create a clean Webflow page without custom code, animations, or third-party embeds.
- Publish it to the same domain and test if the issue persists.
- If the blank page loads, the issue is within your original page content.
6. Check Console Logs on Affected Devices
- You can use a Mac to inspect the iPhone Safari browser using Developer > [Device] > Safari in Safari’s dev tools.
- Check for JavaScript errors or resource failures throwing fatal exceptions.
Summary
The "A problem repeatedly occurred" message usually stems from custom code, animations, or media causing Safari to crash. Begin by stripping down to a basic version of the page, removing custom code and complex interactions, and test progressively. Use Safari's developer tools to pinpoint exact causes during mobile rendering.