Skip to main content

Verified behavior, troubleshooting and maintenance

These are the recorded implementation checks summarized by the current local guide. Version 3 of this page (17 Nov 2026) adds live checks run that day through DSServer against BrowserStack (desktop Safari accessibility on Golden Gate, start-failure reporting) and the unit tests listed below.

AreaRecorded status

Windows 11 Chrome

Live navigation, evaluation, accessor click, WebDriver/CDP and cleanup verified.

Windows 11 Firefox and Edge

Firefox interaction checks and Edge saved-script playback/cleanup verified.

macOS Safari

Playback verified on Sonoma. Golden Gate started and navigated through DSServer on 17 Nov 2026, with accessibility. Tahoe not played.

iPhone 16

Basic playback/cleanup verified on iOS 18.5 and 18.6.

Galaxy S24 Android 14 / iPad Air 13 iOS 18.6

Saved-script playback/cleanup verified. These are older targets than several refreshed defaults.

Accessibility

Windows 11 Chrome and macOS Golden Gate Safari (17 Nov 2026): scans, saved results and processed final report verified. Mobile and distributed-scenario accessibility pending.

Start failures, incognito, Build name suffix

17 Nov 2026: a refused start fails the run with BrowserStack's reason (verified live for Safari); incognito is ignored for BrowserStack; the Build name suffix is unit-tested and packaged but not yet saved from a running AIQ page.

AIQ settings

Local save/apply and earlier starter-list visibility verified. Actual save of the new accessibility fields in a running AIQ and production frontend acceptance remain pending.

Newest starter list

Source defaults and shared-library refresh recorded. New targets not played; AIQ had not been repackaged for that refresh.

Focused checks

17 Nov 2026: Accessibility 22/22, Configuration 18/19, Reconciliation 4/4, DSClient start failure 2/2, frontend BrowserStack module 24/24. Previously recorded: WebDriver connector 9/9, screenshot stitching 11/11, profile loader 4/4. The remaining Configuration check compares against an older AppvanceInterfaces JAR still on the DS test classpath.

Snapshots

Sizing correction packaged. Android repeated-screen defect fixed and verified live on 16 Nov 2026 (Pixel 9 / Android 15, vwr.com). Android pages no longer use ChromeDriver’s whole-page capture, which repeated the visible screen; they are stitched from screenshots that follow the visible area, also on pages wider than the screen. The snapshot showed the whole page, both edges and no repeats. iPhone/iPad bar cropping, ChromeDriver whole-page capture on non-Android sessions and the new targets remain unverified live.

Broad rollout

Full distributed scenarios, all versions/devices and long-duration production acceptance remain pending.

Feature limits to plan around

  • Incognito is ignored for BrowserStack profiles; every cloud allocation already has a fresh isolated profile.
  • Cloud-to-DS file download transfer, native file-chooser upload and arbitrary browser-permission grants through WebDriver are unsupported.
  • Actions that require CDP/BiDi fail on WebDriver-only targets or when optional native attachment did not succeed.
  • The integration uses WebDriver/Appium with optional same-session CDP/BiDi; it does not provide a Playwright execution path.
  • Accessibility scan failures do not automatically fail functional playback; real pass/fail reporting to the provider’s test-health view is deferred.

The in-page scanner used for phones and desktop Safari runs no advanced rules and loads its engine into the page from BrowserStack's asset host; a page whose Content Security Policy blocks that host cannot be scanned (not yet observed).

  • Full-page snapshots use CDP on desktop Chromium and stitching on other targets, including Android. Stitching a long page takes longer than one capture (about 33 seconds for vwr.com on a Pixel 9). Validate the image itself before treating it as evidence.

Troubleshooting

SymptomLikely causeAction

No BrowserStack profiles

Disabled integration/profile, missing/rejected credentials, failed Plan API check, or invalid configuration.

Inspect saved settings and configuration logs; reapply the correct account. Account checks refresh every 60 seconds by default.

Your local Webdesigner is unreachable.

Local process stopped, port 9090 unavailable, timeout or browser network policy.

Start local WebDesigner, verify the intended computer and retry Apply. Check approved browser local-network permissions if AIQ is remote.

BROWSERSTACK_UNSUPPORTED: explicit incognito mode

A DSServer build older than 17 Nov 2026, which refused incognito.

Update DSServer; current builds ignore incognito for BrowserStack.

Could not start <browser>: BROWSERSTACK_REFUSED: <reason>

BrowserStack answered the start without a session. "Automate testing time expired." means the account's Automate minutes are used up.

Act on BrowserStack's reason: add Automate time, check the account, or pick another target.

Desktop Safari: … The session timed out while connecting to a Safari instance after about 3 minutes

A DSServer build older than 17 Nov 2026 sent the accessibility capability for desktop Safari; BrowserStack's "Accessibility Toolkit Headless" setup window kept Safari from connecting.

Update DSServer; current builds use the in-page scanner for desktop Safari.

scan failed … reason=Scanner is not ready on the page after multiple retries.

The scan waited for BrowserStack's browser extension, which was not in the page.

On desktop Safari, update DSServer. On desktop Chrome, check the session in BrowserStack's dashboard.

BROWSERSTACK_CAPACITY

Node limit reached.

Wait for cleanup or adjust maxSessions within the account’s total capacity.

BROWSERSTACK_UNAVAILABLE

Credentials/configuration became unavailable or changed.

Check account status and reapply the current AIQ revision.

BROWSERSTACK_LOCAL_UNAVAILABLE / BROWSERSTACK_LOCAL_PLATFORM_UNSUPPORTED

No verified usable binary for the node host.

Check the bundled folder, executable permissions and update access; review explicit overrides.

Local proxy tunnel timeout

Outbound tunnel blocked or execution-node network not ready.

Check outbound HTTPS/WSS, VPN/proxy rules and application reachability from that node.

BROWSERSTACK_PROTOCOL_UNAVAILABLE

Explicit CDP/BiDi required but unavailable.

Use auto when fallback is acceptable; avoid native-only actions on WebDriver-only targets.

BROWSERSTACK_TLS_TRUST_REQUIRED

Safari rejected the DS proxy certificate.

Restore the supplied Safari/iOS networkLogs policy and verify the target’s trust behavior.

Accessibility says not enabled

Wrong product tab, disabled setting, unsupported DS target, entitlement or registration failure.

Open Accessibility → Automated Tests; check skipped/registration messages and the target matrix.

Accessibility counts differ

Preliminary in-session summary compared with processed report.

Wait for the final-report line and use processed report counts.

Red accessibility test-health status

DS currently reports test outcome as unknown.

Use the functional playback result and accessibility findings separately.

Final report unreadable

Account access, regional API configuration or processing failure.

Follow the report link; inspect 401/403 or processing messages and the account’s region restrictions.

Android snapshot repeats the page top

A DSServer build older than the Android snapshot fix of 16 Nov 2026.

Update DSServer on that execution machine. Until then, do not accept the image as a complete page.

Method not found clearLastSnapshot

Older DSClient call not implemented by DSServer.

Current guide records that capture continues; diagnose actual image content separately.

Remote stop not confirmed

Provider deletion acknowledgement lost/failed.

Inspect only the matching run/session in Automate and confirm it has ended before allocating additional work.

References and maintenance

Provider references were checked on 16 Nov 2026, and BrowserStack's accessibility and Safari pages again on 17 Nov 2026. Catalogs, UI labels, plans and supported SDK matrices can change. Use AIQ's live catalog and the linked provider pages for current account-specific choices.

Implementation basis for maintainers

This page is a publication snapshot of branch IQ-18353-5313-imp-p1, including the reviewed working-tree changes. Source implementation is not a claim of deployment to every installation.

Repository / pathPurpose

DS: documentation/BrowserManager/reference/browserstack.md

Canonical current operator guide and links to dated verification records.

DS: documentation/BrowserManager/design/codex/browserstack-configuration-review.md

Configuration, accessibility lifecycle, final report evidence and refreshed starter-list status.

DS: documentation/BrowserManager/design/codex/browserstack-live-failure-corrections.md

Measured desktop/mobile playback and cleanup results.

DS: DSServer/src/main/resources/com/appvance/platform/browserstack/browserstack-defaults.json

Actual shipped settings/profile defaults reviewed for this page.

DS: DSServer/src/main/java/com/appvance/platform/browserstack/BrowserStackAccessibility.java

Target eligibility, scan lifecycle and final-report polling reviewed for this page.

frontend-BrowserStack: documentation/browserstack.md

UI labels, key handling, catalog behavior and frontend acceptance limits.

AIQ: documentation/BrowserStack/README.md and http-configuration-application.md

Central Save, workstation Apply and private scenario-node delivery.

Keep this page synchronized with both the DS human guide and its knowledge-base route. Preserve dated evidence and distinguish source changes, packaging, live verification and deployed behavior. The newer provider Edge support is intentionally distinguished from DSServer’s narrower accessibility gate.