@wdio/browserstack-service 9.35.0 → 9.35.2

package/build/service.d.ts

@@ -101,6 +101,23 @@ export default class BrowserstackService implements Services.ServiceInstance {
     afterScenario(world: ITestCaseHookParameter): Promise<void>;
     beforeStep(step: Frameworks.PickleStep, scenario: Pickle): Promise<void>;
     afterStep(step: Frameworks.PickleStep, scenario: Pickle, result: Frameworks.PickleResult): Promise<void>;
+    /**
+     * Whether accessibility is being driven by the binary rather than the classic handler.
+     *
+     * Precisely: it decides whether the CLASSIC handler owns the session's accessibility state.
+     * It is the same condition that gates `AccessibilityHandler.before()` in the `before` hook, so
+     * keeping it in one place is what stops the two drifting.
+     *
+     * The two paths are not strictly exclusive. `AccessibilityModule` is registered on
+     * `startBinResponse.accessibility?.success` alone, independent of provider — `isNonBstackA11y`
+     * exists for exactly the turboscale / non-BrowserStack case — so with the binary up against a
+     * non-BrowserStack provider the module can hold real state AND the handler's `before()` will
+     * have run. Both then need migrating, which is what the caller does.
+     *
+     * `isRunning()` alone is NOT equivalent, and that is the trap: under a non-BrowserStack
+     * provider it is true while the classic handler is the one holding the live state.
+     */
+    private _isCliAccessibilityFlow;
     onReload(oldSessionId: string, newSessionId: string): Promise<void>;
     _isAppAutomate(): boolean;
     _updateJob(requestBody: unknown): Promise<unknown>;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wdio/browserstack-service",
-  "version": "9.35.0",
+  "version": "9.35.2",
   "description": "WebdriverIO service for better Browserstack integration",
   "author": "BrowserStack <support@browserstack.com>",
   "homepage": "https://github.com/browserstack/wdio-browserstack-service",