It's possible, we've gone through a lot of use cases to make sure that users have full autonomy over signing events. Strange that this happens right from the start.

Just to be clear, you are able to sign in, but once you sign in this happens?

Please also make sure you are using our latest build, we introduced a fix for users who use NWC while signed in via Amber.

Reply to this note

Please Login to reply.

Discussion

Running versionCode 235, is that the latest?

I only saw the first screen to log in. Now when I open the app I'm stuck in this loop, whether I accept or reject.

Try starting from scratch, removing the app from Amber. And maybe try rejecting signing kind 10000300 to see what happens.

Yep, this is an issue on our end. We found that you can bypass it by picking “remember for this event” authorization.

Thanks for the report, we’re looking into it.