-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to sync "used" atSigns using trunk version of atBuzz #1139
Comments
Video example... video1829848063.mp4 |
Currently troubleshooting root cause |
Observations so far:
|
From app logs: SEVERE|2023-10-16 18:51:15.602306|EncryptionUtil|Error while decrypting value: Invalid argument(s): Invalid or corrupted pad block However, sync completes by skipping over any bad keys. |
I debugged locally and found that there are no keys with '.atbuzz' namespace in the server In happclam atsign, Contacts with at_contact.atbuzz regex is empty @ happyclam@scan at_contact.atbuzz |
@cconstab have you previously created data in atBuzz with If yes, was it on the store test versions or locally ? |
contacts in the buzz app are saved with at_contact.atbuzz namespace In happclam atsign , Contacts with at_contact.atbuzz regex is empty @happyclam@scan at_contact.atbuzz Whereas if I do a scan with only "atconnections" I get contacts with mosphere, mospherePro and wavi namespaces but not .atbuzz namespace. I think this is the reason |
@cconstab needs review please |
This was ckeared up with a bug Gary found and was commited a week or so back Can be closed |
Yay! Closed now. |
Describe the bug
I wanted to demo atBuzz and cannot get it to sync in the emulator I see many errors but this one stands out
Steps to reproduce
Expected behavior
Things just work!
Screenshots
No response
Smartphones
Were you using an atApplication when the bug was found?
atBuzz (trunk)
Additional context
No response
The text was updated successfully, but these errors were encountered: