Key exists but llookup can't find it.

[yahu1031]

Describe the bug When a bad key was updated, The key content is being changed due to this issue at_wavi_app-130.

To Reproduce Steps to reproduce the behavior:

1. Reproduce the above-mentioned issue
2. Then authenticate to your secondary using dess/OpenSSL.
3. Try scanning the keys and search for the weird key you updated.
4. You will find some other key but similar(some chars will be replaced by _)
5. Try llookup:WEIRD_KEY.

Expected behavior It must return whatever value the key has.

Screenshots

https://user-images.githubusercontent.com/35523357/148705286-40400fb1-76ff-4a90-ab76-749e17576cab.mp4

Smartphone (please complete the following information):

• Device: Mi 11x
• OS: Android 11

Were you using an @‎application when the bug was found?

• at wavi app

Additional context This happens cause of this issue https://github.com/atsign-company/at_wavi_app/issues/130