-
Notifications
You must be signed in to change notification settings - Fork 1
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
Not receiving messages between atsigns using at_onboarding_cli+at_auth #19
Comments
The issue got fixed by updating AtOnboardingPreference()..useAtChops = true dart bin/at_talk.dart -k /home/shaikirfan/.atsign/keys/@ yeastydotterel85_key.atKeys -a @ yeastydotterel85 -t @ charlie24 atsign-2 |
@gkc at_auth package requires at_chops for pkam signing. Fix for this issue has to be in at_talk.dart..is this fine? |
@murali-shris Shouldn't we instead make useAtChops true by default in at_client? |
yes Gary. We can. We should test there are no legacy code in packages that sets private key in preferences and not setting atChops. |
@murali-shris OK please create a P1 ticket for this work asap |
atsign-foundation/at_client_sdk#1141 |
issue fixed and at_client 3.0.66 published |
Describe the bug
Sent messages are not being displayed on the receiver's end
Steps to reproduce
Clone the trunk branch of at_talk (change the dart version)
Then Add the following dependency overrides
dependency_overrides:
at_commons: ^3.0.56
at_lookup: ^3.0.40
at_client:
git:
url: https://github.com/atsign-foundation/at_client_sdk
ref: trunk
path: packages/at_client
at_onboarding_cli:
git:
url: https://github.com/atsign-foundation/at_libraries.git
path: packages/at_onboarding_cli
ref: apkam_onboarding_changes
And then generate a new atsigns with register_cli(apkam_onbording_changes) branch
Run the following commands for the 2 atsigns
atTalkLOgs.txt
attalkreceiverlogs.txt
Expected behavior
Messages sent and received should be displayed.
Screenshots
attalk.mp4
Smartphones
No response
Were you using an atApplication when the bug was found?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: