You sure? Works with alby
Discussion
And it gets pubkey from hostname, not query string
I tried both. 1st one didn’t work. 2nd one worked..
1. nostrwalletconnect://c7063ccd7e9adc0ddd4b77c6bfabffc8399b41e24de3a668a6ab62ede2c8aabd?relay=wss://wc1.current.ninja&secret=xxx
2.nostrwalletconnect://c7063ccd7e9adc0ddd4b77c6bfabffc8399b41e24de3a668a6ab62ede2c8aabd?relay=wss://wc1.current.ninja&secret=xxx&pubkey=438297f6e1051d301ff086216ed6e55e36d7ee6642b2d39903dfe96636127e03
That is why I asked. Also will there be an input field to copy/past the connect string?
NIP-47 spec has only 3 inputs. Wallet pubkey, relay and secret. Since secret itself is a private key, you can always get pub key from it. Also instead of showing the relay name, you should NIP05 the wallet pub key and display it. 
Check the code (WalletConnectURL), it does not get it from the querystring
ok. let me check again and report back.
ok found the issue. qr code expects the string to start with nostrwalletconnect:// where as the spec says nostr+walletconnect://
+ is missing..this is the issue..!
I suspected the case and fixed it before you sent me this message :)
all good. still need a input box to accept the connect string..! this is easier to copy/paste than scan QR code when both apps are on the same phone..!
You’re even loster.
Needs work