Skip to content

Troubleshooting

Check Compatibility and remember public npm/CLI distribution is not available yet. In this repository use the documented workspace/packed-consumer paths.

Provider/overlay/toast behavior is missing

Section titled “Provider/overlay/toast behavior is missing”

Mount one application-root BeeUIProvider. Nested providers reuse the supported root runtime; do not create unrelated roots and expect them to arbitrate one global Escape/back event.

Content is double-inset or under system UI

Section titled “Content is double-inset or under system UI”

Assign each edge to the SafeArea that actually touches it. A Screen, header or bottom bar does not secretly own all insets. See Provider & safe area.

Verify the token theme CSS plus Tailwind/Uniwind imports in Web onboarding.

Compare your peer/native dependencies to Compatibility. After adding/changing a native dependency, rebuild the native app; a JavaScript refresh cannot install native code.

Popover/Select/Dropdown placement or focus is wrong

Section titled “Popover/Select/Dropdown placement or focus is wrong”

Check that the app root/provider and modal-local overlay hosts are intact; avoid moving interactive children out of their documented composition. See anchored overlays.

Read the component limitation plus native compatibility evidence. iOS sheet presentation has explicitly qualified support; do not infer it from Web behavior.

Start with the responsive guide and component reference. Keep page horizontal scrolling off; give genuinely wide data/code its own bounded scroll region.

Run the repository-local CLI exactly as documented in CLI & source ownership and inspect the reported source/dependency drift before updating files.

Use Keyboard & focus and test real Tab/Escape flows.

Canonical behavior sources: registry CLI, components, and Web support.