Looking at the pull requests they are becoming a nip 55 signer soon

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

That could be it, I think amethyst is using all the resources and the other apps can't use it. I'll try to fix this
The older versions of amber works right?

I receive your messages. It looks like amethyst is sending then and not showing the note or any indicator that it still trying to send the message @nprofile1q...

I sent you a test apk in a dm. Did you receive it?
Basically I just updated the dependencies and tried to fix the app not closing when you accept or reject a permission
Not sure if it will fix the connection issue in this apk
Let me know if you received it and if it fixed something

Always a Samsung or Xiaomi when those crazy bugs happens 🤣🤣
Have you also tried rebooting the device?
Just tried in a Samsung and it worked I have no idea what's happening with your device

What device are you using?

In nak works because you don't change apps when you connect to it. When you open amber the browser suspends the relay connection and then unsuspend it when you open the page again
If there's no failed to send logs or relay disconnected logs amber is working just fine
Relays should also implement the mute keyword fiatjaf added some months ago so we can always be sure when a client is losing the messages

Also try force closing amber and opening it again of it doesn't work with another browser

Can you also try in another browser?

Does the logs in the settings says anything?