ObsidianAndroidAppiumTransportOptions.appStartTimeoutInMilliseconds?

ObsidianAndroidAppiumTransportOptions › appStartTimeoutInMilliseconds?

Type: number

Timeout in milliseconds for Obsidian Mobile to get as far as globalThis.app existing after the vault is (re)opened.

The first of the two budgets the transport spends after location.reload(). It covers the app's own cold start — the WebView reloading and Obsidian's bundle coming up — which on a cold or contended guest can take minutes, and is not work layoutReadyTimeoutInMilliseconds should be sized for. Only once globalThis.app appears does that far tighter clock start.

Splitting the two is what stops a first run after a machine restart from failing by design: the old single 90s wall clock started at the reload, so a cold app start spent it before Obsidian had begun laying anything out.