Thanks for confirming. We will try to reproduce and may reach out for additional info.

Please send crash reports and we will investigate!

In our experience push notifications won’t help beyond just letting the user know that they should open the app to resume their remote session.

Don’t worry at all about being a “quick copycat”. We’d love to see more signers, which is why we shared the playbook.

Please make sure you’re running the latest app store build. We pushed an update yesterday that should address some crashes people ran into.

Thank you sir. Yes, we can add wss:// if it’s missing. We’ll aim to include this in the next update.

yep!

Yes, you can easily trigger the signer by using the standard nostrconnect:// uri scheme. That's what a "Login with Nostr" button should do.

We even added support for a convenient "callback" parameter, so Primal will redirect back to your app immediately after establishing the remote connection. If it's a browser app, simply use callback=https://[your_app_login_progress_page] to get redirected back to your app.

@nprofile1q... implemented this flow for some of his web apps; it works great. Derek, maybe you could share a quick video of this in action?

To clarify, we don't yet support generating the bunker:// string that you can paste into the remote app

Yes, click the "Use keyboard instead" button on the scan screen.

You can mute the sound via the dynamic island or lock screen UI. Also the signer should be running only while you have remote sessions going.

Yes, it's already open source

Thank you. Hopefully this paves the way for more signer implementations and the "Login with Nostr" button becomes ubiquitous.