Conversation
Encrypted transfer was sending account object to Memo() instead of the account string. This was triggering detection as a key ( len >= 51) and causing a KeyError
|
I can confirm this little fix corrects my issue of sending transfers with encrypted memos. Would like to see this released asap. |
|
For anyone else affected by this, in advance of it being folded into Beem properly the following magic works for me which just pulls Beem from @cfoxon 's github instead of the official one.
I'm using Poetry but I suspect this would also work:
Poetry uninstalled beem for me, I'm not sure what Pip would do. Package management is not something I'm hugely proficient at. |
sicarius97
left a comment
There was a problem hiding this comment.
Tested and works fine for me with these changes, can you check this out @holgern ?
|
@holgern can this get released? |
Encrypted transfer was sending account object to Memo() instead of the account string. This was triggering detection as a key ( len >= 51) and causing a KeyError