The graph API is missing
Confirm that the graph-capable package or product is selected. In Python, Node.js, and Kotlin, do not load the base and graph native aggregates together; replace the base package because graph already includes retrieval.
Troubleshooting
Diagnose the boundary before changing the query.
Most integration failures come from package ownership, embedding dimensions, generation-bound selections, or closed handles. These checks name the expected v0.1.0 behavior before you debug wrapper code.
Diagnostic checks
Start with the failure that matches what you see.
Each answer is a product boundary, not a workaround. Follow the selected language guide for exact method names.
An embedding query is rejected
Check that every document and query embedding has the dimension established by the first non-empty document embedding. A dimension change is rejected before it can mutate the database.
Hybrid results lean toward the wrong signal
Treat alpha as the vector weight: 1 selects vector-only ranking, 0 selects BM25-only ranking, and values between them fuse both. Keep metadata filters or graph scope separate from that ranking choice.
A graph selection is stale or rejected
Selections are opaque, generation-bound handles. Do not reuse a selection after closing it, across clients, or after publishing a different database generation; run the graph query again against the active database.
Operations fail after cleanup
Closing a database or selection makes it unavailable to new work. Await asynchronous close methods where the wrapper exposes them, and create a new handle instead of reusing a closed one.
A browser database disappeared
That is the documented v0.1.0 boundary. Browser databases live in their dedicated Worker and are in memory; rebuild the corpus after the Worker or page lifecycle ends.
An Android package resolves but device behavior is uncertain
Publication proves packaging for API 24+ arm64-v8a, not live-device compatibility or performance. Treat physical Android inference, lifecycle, thermal behavior, and performance as unqualified.
Still blocked? Open the pinned source guide for your language from the documentation home, then report a reproducible failure against the signed v0.1.0 release rather than the moving main branch.