Skip to content
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

Closed
cconstab opened this issue Oct 16, 2023 · 10 comments
Closed

Unable to sync "used" atSigns using trunk version of atBuzz #1139

cconstab opened this issue Oct 16, 2023 · 10 comments
Assignees
Labels
bug Something isn't working

Comments

@cconstab
Copy link
Member

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

I/flutter ( 4881): SEVERE|2023-10-16 11:34:55.169796|SyncService (@happyclam)|Exception in sync 7703fbc5-d838-4627-9fbf-329aa8bfa715. Reason: Failed to syncData caused by
I/flutter ( 4881): Unable to fetch latest server commit id: Exception: 9a 

Steps to reproduce

  1. First I get the latest trunk of atbuzz
  2. Then I run it in an Android emulator (ios/iphone build breaks with MASSIVE list of errors!)
  3. And then try to onboard an atSign
  4. Onboard seems OK but sync never works and asks me to reset atSign
  5. Not sure if this is a bug in Lib or app but since this error above is in the lib I raised the issue here..
  6. REALLy would like this solved so it can get into the demo in NYC and I need to record it ASAP (today)

Expected behavior

Things just work!

Screenshots

No response

Smartphones

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Were you using an atApplication when the bug was found?

atBuzz (trunk)

Additional context

No response

@cconstab cconstab added the bug Something isn't working label Oct 16, 2023
@cconstab
Copy link
Member Author

Video example...

video1829848063.mp4

@ksanty
Copy link
Member

ksanty commented Oct 16, 2023

Currently troubleshooting root cause

@VJag
Copy link
Member

VJag commented Oct 16, 2023

Observations so far:

  1. For @happyclam, all of the data is properly synced for regex '.atbuzz|atconnections' using a test client
  2. Purnima could reproduce the issue with the buzz app, where she saw contacts not being synced
  3. Observed decryption issues in logs while running the app, however they are not present when synced using the test client

@VJag
Copy link
Member

VJag commented Oct 16, 2023

From app logs:

SEVERE|2023-10-16 18:51:15.602306|EncryptionUtil|Error while decrypting value: Invalid argument(s): Invalid or corrupted pad block
I/flutter ( 2011): INFO|2023-10-16 18:51:15.603355|AtContactsImpl|atconnections.anthony.contacts.happyclam does not exist in keystore

However, sync completes by skipping over any bad keys.

@purnimavenkatasubbu
Copy link
Member

purnimavenkatasubbu commented Oct 17, 2023

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
data:[]

@sachins-geekyants
Copy link
Contributor

@cconstab have you previously created data in atBuzz with @happyclam?

If yes, was it on the store test versions or locally ?

@VJag
Copy link
Member

VJag commented Oct 17, 2023

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
data:[]

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

@ksanty
Copy link
Member

ksanty commented Nov 14, 2023

@cconstab needs review please

@cconstab
Copy link
Member Author

cconstab commented Nov 14, 2023

This was ckeared up with a bug Gary found and was commited a week or so back

Can be closed

@ksanty ksanty closed this as completed Nov 14, 2023
@ksanty
Copy link
Member

ksanty commented Nov 14, 2023

This was ckeared up with a bug Gary found and was commited a week or so back

Can be closed

Yay! Closed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants