chore: reduce ios simulator animations

Author: YogendraShelke

maestro/helpers/prepare_ios.sh

@@ -64,6 +64,34 @@ elif best:
     xcrun simctl bootstatus "$DEVICE_ID" -b || echo "Simulator booted"
 }
 
+# Cut UIKit animation time, mirroring `disable-animations: true` on the Android emulator
+# (NativePipeline.yml) — iOS previously had no equivalent, so every navigation push/modal
+# played at full length on a 3-vCPU runner while Android's ran instantly.
+#
+# Scope: this shortens SYSTEM transitions (nav pushes, modal presents, alerts). React
+# Native's `Animated` does NOT read this flag automatically, so widget-internal animations
+# (carousel, animation-native) are unaffected — this is not a substitute for the per-flow
+# waits those need.
+#
+# Requires a BOOTED device (`simctl spawn`), so call after start_simulator. The value is
+# written to the device's persistent domain and survives shutdown/boot, so a
+# restart_simulator in helpers.sh keeps it.
+reduce_motion() {
+    echo "Reducing motion on iOS Simulator..."
+    if [ -z "$SIMULATOR_DEVICE_ID" ]; then
+        echo "Error: SIMULATOR_DEVICE_ID not set"
+        return 1
+    fi
+    # Best-effort: a future runtime that drops/renames these keys should not fail the shard,
+    # since tests still pass with animations on (just slower).
+    xcrun simctl spawn "$SIMULATOR_DEVICE_ID" defaults write com.apple.Accessibility ReduceMotionEnabled -bool true \
+        || echo "::warning::Could not set ReduceMotionEnabled; animations stay at full length"
+    # Replaces the sliding push/pop transition with a cross-fade — the slide is what Maestro
+    # most often races against when asserting right after a navigation tap.
+    xcrun simctl spawn "$SIMULATOR_DEVICE_ID" defaults write com.apple.Accessibility ReduceMotionReduceSlideTransitionsEnabled -bool true \
+        || echo "::warning::Could not set ReduceMotionReduceSlideTransitionsEnabled"
+}
+
 set_status_bar() {
     echo "Setting status bar on iOS Simulator..."
     if [ -z "$SIMULATOR_DEVICE_ID" ]; then
@@ -92,6 +120,7 @@ verify_installed_app() {
 }
 
 start_simulator
+reduce_motion
 set_status_bar
 install_ios_app
 verify_installed_app

packages/pluggableWidgets/intro-screen-native/e2e/specs/maestro/IntroScreen.yaml

@@ -6,9 +6,12 @@ appId: "${APP_ID}"
     text: "I"
 - tapOn:
     text: "Intro screen"
+# Opening the page mounts the widget and waits on the runtime, unlike the in-flow waits
+# below which only cover an on-device slide transition. 5s was flaky on the CI simulator
+# (3 vCPU, shared with the Mendix runtime JVM); 15s matches the repo's usual budget.
 - extendedWaitUntil:
     visible: "Active slide: 2"
-    timeout: 5000
+    timeout: 15000
 - assertVisible:
     text: "Changes: 0"
 - swipe:
@@ -42,9 +45,11 @@ appId: "${APP_ID}"
 - tapOn: "Go back"
 - tapOn:
     text: "Intro screen"
+# Re-entry remounts the widget, which must reposition to the attribute's slide — same
+# page-entry cost as the first open, so the same 15s budget rather than 5s.
 - extendedWaitUntil:
     visible: "Active slide: 2"
-    timeout: 5000
+    timeout: 15000
 - tapOn:
     text: "NEXT"
 - extendedWaitUntil: