Skip to main content

​
pnpm install Did Not Create node_modules In My Scaffolded App

You likely created the app inside another pnpm workspace. Run from the parent directory:

​
Web Bluetooth Is Unavailable

Check the following:
  • Use Chrome or Edge
  • Run on https:// or localhost
  • Make sure Bluetooth is enabled on the machine
  • Do not expect this workflow to work in Safari or iOS

​
loadWasmBackend() Returned null

Make sure your app is serving the packaged pkg/rppg_wasm.js and pkg/rppg_wasm_bg.wasm assets from a path the browser can reach. If you are unsure, compare your app with the scaffolded rppg-demo app.

​
initEegWasm() Failed

Your app is probably not serving the packaged wasm/ assets from @elata-biosciences/eeg-web correctly. Compare your asset layout with the scaffolded eeg-demo app.
If you are using Vite, the two common fixes are: add vite-plugin-wasm and vite-plugin-top-level-await, or import the WASM asset URL directly and pass it to initEegWasm(wasmUrl).

​
Elata Upload Says “Elata sensor SDK not detected”

Elata checks every upload for real SDK usage. Make sure your build:
  • actually calls the SDK, for example createRppgSession(...) or initEegWasm(...), not just imports it
  • includes the packaged .wasm files in the build output
The create-elata-demo templates pass this check, so compare your build with one of them.

​
app-payments, app-state, Or app-metrics Calls Time Out

These packages talk to Elata’s parent frame. When you run your app on localhost there is no parent to answer, so calls time out or reject with no_parent. Handle that case gracefully, and test the full flow in Elata’s play window. For purchases, examples/iap-demo includes a mock host you can run locally.

​
I Am Not Sure Which Package I Need

Start with Choose The Right Package. If you still just want the fastest path, use create-elata-demo.

​
Next

Choose A Package

Package decision guide

Compatibility

Browser, device, and tooling support