Hey there! Let’s tackle this frustrating problem where your UI5 app’s "UI5 loaded" alert isn’t firing on iPhone/iPad, even though everything works smoothly on desktop and Android. It’s definitely one of those platform-specific quirks that makes you go "wait, why?!" — let’s break down the most likely fixes:

1. iOS Safari Blocks Async Alerts #

iOS Safari has strict anti-intrusion rules: it will block window.alert() (and confirm()/prompt()) if they’re triggered from an asynchronous callback (like UI5’s initialization events). Your "UI5 step1" alert probably runs synchronously right after your script loads, so it gets through, but the "UI5 loaded" alert is tied to UI5’s async ready state — which iOS flags as an unprompted popup and blocks.

Fix:

• Swap window.alert for UI5’s platform-native sap.m.MessageBox.alert() — it’s built to work across all devices without triggering iOS’s popup blocks:

  sap.ui.getCore().attachInit(function() {
    sap.m.MessageBox.alert("UI5 loaded", { title: "App Status" });
  });
  

• If you just need debug info, use console.log("UI5 loaded") instead — console output never gets blocked by iOS.

2. Fix Your Incomplete Viewport Tag #

Looking at your code snippet, your viewport meta tag cuts off mid-way (heigh...). A malformed viewport tag can cause all sorts of unexpected behavior in iOS Safari, including breaking JS execution flows that work elsewhere.

Fix:
Replace it with the complete, standard UI5 viewport tag:

<meta name="viewport" content="user-scalable=no, initial-scale=1, maximum-scale=1, minimum-scale=1, width=device-width, height=device-height" />

3. Adjust UI5 Initialization Timing #

iOS Safari’s JS engine handles async operations a bit differently than other browsers. If you’re triggering the alert directly in a require callback, try wrapping it in a setTimeout (even with 0ms delay) to push it to the next event loop tick — this can bypass iOS’s blocking mechanism:

sap.ui.require(["sap/ui/core/Core"], function(Core) {
  setTimeout(() => {
    window.alert("UI5 loaded"); // Only use this for quick testing!
  }, 0);
});

But again, using MessageBox is the better long-term solution for user-facing notifications.

4. Check for Hidden Errors #

Don’t overlook silent JS errors that might be stopping execution on iOS. Connect your iOS device to a Mac, open Safari Web Inspector, and check the Console tab for any errors that aren’t showing up on desktop/Android. A tiny syntax issue or unsupported API could be halting your callback before it reaches the alert.

内容的提问来源于stack exchange，提问作者Guoping Zhang