Since the code that is causing this behaviour is not ours but the one of steemconnect-js, changing the approach would mean writing all the Keychain functions ourselves instead of using the convenient steemconnect-js library which is written for this purpose. We haven't really looked into the Steemconnect browser extension, any reason to have it installed parallel to Keychain?
You are viewing a single comment's thread from:
Hello and thanks for the upvote. I still owe you an answer to your last question about the reason. Bookmarked and will come back to it later.