3box
"Invalid encoding" error in private.log
@oed @zachferland
The error I was seeing only locally I'm now see at the master URL (Oed, the same error I showed you a few weeks ago).
This is probably quite trivial (with respect to the dapp) because the only fields that are private are birthday and email, and only prevents us from properly fetching the logs of adding and removing entries to the private store.
However, this it is preventing private activity (add/remove birthday) from being loaded when i'm signed in and looking at my activity feed.
Catching error now so that we can still display public data, but as mentioned, private logs are not displaying now (when you're a user that happens to be affected by this error)
Behavior:
in fetching for users activity feed box.private.log;.
Happens every time for me, though seems most other users haven't been seeing this issue.
Is this the same error as we tried to debug a couple of other times? If I recall correctly there was an entry in your private store that was not encrypted, and seem to have gotten there from the public store. That seems like it's the issue we'd want to fix, but if I understand correctly it's not so easy to reproduce? Anyway I think we should add a fix that ignores this error since it seems unrelated to the actual entries in the private store.
Yes, this is the same error, I'm able to reproduce it every time I load my profile