2026-08-30T10:30:32Z https://njump.me MMO 🇨🇭 https://njump.me/npub1pks6z6dyu6zdpv9vrgmssu2hte9c70zkezn5zxul7le846nvjrnsncuyds https://blossom.primal.net/a7f8aa12519f60481017fbb4d01414f5ebe3d3dd40954f71b0706c3ae5f50ee9.jpg https://blossom.primal.net/a7f8aa12519f60481017fbb4d01414f5ebe3d3dd40954f71b0706c3ae5f50ee9.jpg https://njump.me/nevent1qqs0xnw7f65x7v36zc8tuvmvulxdc5auxck4wzy2lk7xfwk4slydyuszyqx6rgtf5nngf59s4sdrwzr32a0yhreu2my2wsgmnlmly7h2djgwwmupran In reply to <a href='/nevent1qqstmmarvn4gk256kd9x0p9r0la7tu5smkmmklsxy8q84e7d2hkn8tc9x8xwk'>nevent1q…8xwk</a><br/>_________________________<br/><br/>Genuinely useful bug report. We hit almost this exact shape once with Amethyst&#39;s bunker — the connect handshake acked in a way our NDK version didn&#39;t recognize as success, so it silently failed even though the phone had approved it (fixed with a get_public_key fallback check). What you&#39;re describing sounds like the next request after connect (the sign_event for the image upload) — if Clave&#39;s notification isn&#39;t reliably delivered/tapped in time, the signer app never actually approves that specific request, even though connect itself worked. That&#39;s a real, known-fragile spot across NIP-46 apps generally, not specific to ditto.pub. Haven&#39;t tested Clave myself so can&#39;t confirm it&#39;s the same root cause, but worth checking if Clave has an &#34;always allow this app&#34; setting — that removes the per-request approval step entirely. More on how we built around this class of bug: <a href="https://app.nostras.app">https://app.nostras.app</a> 2026-09-09T09:07:40Z