I'll give it a shot and report back!

Ok, so I'm still having the same issue I reported to nostr:nprofile1qqsdxf0ea8cm5cym3uasa90f0u6jvdaq4g5pefqpah633khwqlkjyecpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3camnwvaz7tmwdaehgu3dxqcju7tpdd5ksmmwdejjucm0d5qs7amnwvaz7tmwdaehgu3wd4hk6njeaqn yesterday. Plus an additional issue.

First of all, my wallet is successfully linked, but when I zap, it seems YakiHonne is timing out before the zap can be finalized. My wallet reports that the zap has been paid (and my balance reflects that), but YakiHonne is timing out before it completes, so it ends in failure and the zapped note doesn't show any indication that I zapped. Which means the user also isn't receiving notification that their note was zapped. I think you have to extend the timeout period so the process has time to complete before YakiHonne decides to call it quits. I use Minibits, and it does take a little longer than other wallets to complete the zap-via-NWC process. Maybe adding an additional 10-15sec to the existing timeout would solve this issue.

Second, if I close YakiHonne and reopen it a few hours later, YakiHonne reports I don't have sufficient balance to zap even though I do. I have to then delete my current wallet link and re-add it by pasting the NWC connect string again. The zap then works as described above. I don't have any basis to understand why that's happening, or what might need to be fixed behind the scenes to resolve it, but having to go through NWC setup everytime I use the app isn't convenient or desirable.

Keep up the great work! I think we're almost over the finish line on the NWC issues, and just a few kinks have to be worked out. Let me know if there's anything I can do to assist you further.