nostr:nprofile1qqszpxr0hql8whvk6xyv5hya7yxwd4snur4hu4mg5rctz2ehekkzrvcpz4mhxue69uhkummnw3ezuvtnv96zummjvuhsz9thwden5te0dehhxarj9cc8sdm99eu8j730qyv8wumn8ghj7un9d3shjtnsd3jkyum5wghxxmmd9ujkmvl8 why isn't it possible to log in with nostr:nprofile1qqswacu3amp428kj8wtpqf77yd2upukcn2ft4aycmxm5scmh359e0ssppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7mn0wd68ytnddakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uvt9vcv for two accounts?
Discussion
It is.
For me at least!
I think I need to change nip 55 and remove the get public key from background
The correct approach is use it on foreground when login in, save the user pubkey somewhere and never call it again anywhere
I see. Thanks!
This is fixed with the latest nostr:nprofile1qqswacu3amp428kj8wtpqf77yd2upukcn2ft4aycmxm5scmh359e0ssppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7mn0wd68ytnddakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uvt9vcv release, thanks nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgppemhxue69uhkummn9ekx7mp0qydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezumrpdejz7d9xcpk!
i'm able to :)
It should work with yakihonne normally not sure whats happening from your side.