Metadata Martyr 

 Yes, it was NIP-55; how was the issue resolved? Combing through the Amber and Quartz code it seemed like it was potentially a pubkey decryption bug but I wasn't sure. I felt like a crazy person debugging a single line of code over and over. 😅

Also, Amber isn't a NIP-46 compatible signer correct, or have I just not looked hard enough through the app? I'm planning on implementing NIP-46 as well, I've just gotten a bit more inbound asking for Amber support. 

 It was a bug in amber not splitting the strong correctly.
Amber supports nip 46 

 Does the connection token get generated from the app or should that be handled client side using the relays set in Amber? 

 you can do both, there's a nostrconnect uri that a client can generate and there's a bunker uri that the signer generate.
In amber to generate the bunker string you go to permissions, press the plus button and then press the new app button 

 You can also use some library that does all the work for you like https://github.com/fiatjaf/window.nostr.js and https://github.com/nostrband/nostr-login 

 Awesome, thank you!