@sungen/driver-mobile 3.2.29 → 3.2.31

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sungen/driver-mobile",
3
- "version": "3.2.29",
3
+ "version": "3.2.31",
4
4
  "description": "Sungen mobile platform driver (Appium / WebdriverIO) — gesture vocabulary, mobile selector strategies, viewpoint gate, and the WDIO runner. Plugs into @sun-asterisk/sungen via the capability SPI.",
5
5
  "main": "src/index.ts",
6
6
  "types": "src/index.ts",
@@ -13,7 +13,7 @@
13
13
  "author": "eqe team (engineer & quality) — Sun Asterisk",
14
14
  "license": "MIT",
15
15
  "dependencies": {
16
- "@sun-asterisk/sungen": "3.2.29",
16
+ "@sun-asterisk/sungen": "3.2.31",
17
17
  "@wdio/appium-service": "^9.0.0",
18
18
  "@wdio/cli": "^9.0.0",
19
19
  "@wdio/local-runner": "^9.0.0",
@@ -97,6 +97,10 @@ export const mobileRepairRules: MobileRepairRule[] = [
97
97
  example: "No Chromedriver found that can automate Chrome '112.0.5615'. See the appium chromedriver documentation.",
98
98
  fix: 'A WebView step needs a Chromedriver matching the device\'s System WebView. Set `appium:chromedriverAutodownload: true` in the capabilities, or pin `appium:chromedriverExecutableDir` to a directory holding the right build. If this unit is a native screen that only crossed a WebView by accident, assert the native markers instead so the run never enters WEBVIEW context.' },
99
99
 
100
+ { id: 'mobile-webview-context-absent', match: /no WEBVIEW\/CHROMIUM context appeared within/,
101
+ example: '[sungen] "switch to Payment frame" — no WEBVIEW/CHROMIUM context appeared within 30000ms (contexts seen: ["NATIVE_APP"])',
102
+ fix: 'The WebView context never came up inside the wait budget, so `switch to [X] frame` refused to continue rather than run every later step against the native tree (#705). Read the contexts it listed: only `NATIVE_APP` means the WebView had not been created yet — the action before this step starts a slow navigation, so give it room by raising `waitforTimeout` in `wdio.conf.ts` past the real transition time. A WEBVIEW entry present but unmatched means Chromedriver never attached — see `mobile-chromedriver-mismatch`. If the screen has no WebView at all, delete the frame step and assert the native markers instead.' },
103
+
100
104
  // ── Runtime: element-level symptoms (both measured on a real device) ─────────────────────────
101
105
  { id: 'mobile-scroll-no-scrollable', match: /Default scrollable element .* not found/,
102
106
  example: "Default scrollable element '//android.widget.ScrollView' not found",