Quick fixes for the common snags, and where to reach us when they aren't enough.
Bark and your signer must share at least one relay. Check the relay list in your bunker URI matches one your signer actually connects to, and that the signer is unlocked and online.
If the signer needs you to approve new clients, approve Bark there (Heartwood shows a button prompt; hosted bunkers show a queue). Then hit Retry in the popup.
If privacy mode is on, Bark is hidden from every site without a site rule. Open the popup, expand Signing Policies, and add the site (or untick privacy mode), then reload the page.
Bark also only injects on https pages (plus localhost), so http-only sites won't see it.
The first request after a long idle can take a few seconds while the service worker wakes and reconnects to the relay; Bark retries this automatically. If it hangs beyond that, open the popup and run the sign Test, which reports exactly where the chain is stuck.
Bark now shows a notice inside the requesting page whenever approval is waiting. Click "Review in Bark" to bring the approval window forward. The toolbar badge also shows the number of queued requests.
If neither appears, open the Bark popup and confirm the site is enabled and your signer is connected, then retry the request.
Add the new signer with "+ Add Signer" (URI or QR), confirm signing works with the Test button, then remove the old instance. Site policies are kept; they belong to Bark, not the signer.
GitHub issues is the fastest route. A good report includes your browser, signer type, and what the popup's sign Test says.
Open an issueNot sure it's a bug? Start a discussion and we'll figure it out together.
Start a discussionNever post vulnerabilities publicly. The security policy explains how to reach the maintainer privately.
Security policyOne thing we will never ask you for: your nsec, your seed phrase, or your bunker URI with its secret. Anyone who does is not us.