Replies (4)

CB's avatar
CB 4 days ago
Fwiw Anyone looking to move. I have a Premium account and the integration becomes flakey with NWC and Minibits. Also noticed issues saving lightening address when the Primal Wallet is turned off. Some days it works, but only appears to be an issue with Primal premium. I’ve setup other users with minibits on Primal without issue, but they were not Premium users. I’ve also integrated Minibits with two other Nostr clients without issue. There’s an issue logged on github so I’d imagine it will get addressed. This is specific to iOS in my case. Premium is great otherwise and considering Pro, but waiting to see the Minibits issue gets squared away first. If any devs want me to run tests or have q’s, just reach out.
CB's avatar
CB 21 hours ago
Followup. I figured out a workaround for anyone that’s in the same situation. Mileage may vary. Again, this is iOS specific. I have a Premium and non-Premium account and zapping from the same Minibits/Lightening address: 1. Keep a separate NWC profile setup in Minibits for each. (Label them differently) 2. When you experience wallet connection issues Disconnect the Minibits wallet from the Primal client for the selected profile. 3. Paste the Connection string back in and close both Minibits and Primal. Reopen Minibits and Primal in that order. 4. When you open up Primal you should see the pop-up from Minibits: “Minibits NWC listener Listening for NWC commands…” *That indicates it’s ready to zap. 🤞 If it doesn’t work repeat steps 2 & 3. I don’t know if this is more of a Primal or Minibits issue, but it’s currently a suitable workaround for my purposes.