Colin Constable

Unsigned repo

1

Following Ubuntu instructions shows an unsigned repo so breaks on apt update etc.. Looking forward to using in either case thanks..

Pad block errors on initial notifications

28

**Describe the bug** When sending the first notification when using atTalk the first messages fail due to pad block failures. **To Reproduce** Steps to reproduce the behavior: 1. First I...

Multiple updates of the same data when receiving a notification...

5

**Describe the bug** When sending a single notification on a regular basis the receiving atsign gets the data but it uses more bandwidth than expecting and gives an error: 'Error...

Demo code on atsign.dev no longer compiles cleanly

7

**Describe the bug** Error when following the instructions on atsign.dev **To Reproduce** Steps to reproduce the behavior: 1. First go to https://atsign.dev/docs/get-started/tryatplatform/ 2. When running the app compile time errors...

Background notifications on the @platform

5

Lead: @cconstab **Is your feature request related to a problem? Please describe.** Currently the @ application needs to be active to receive notifications. This causes problems when for example a...

Notifications sent to self never get a callback.

5

**Describe the bug** If an @ sign sends a notification to itself (to notify another client on the same @ sign the call back never gets called. This could be...

Connection to root fails and the exception is not caught

13

**Describe the bug** If you have a long running program the connection to root may well fail (it may also fail to secondaries) **To Reproduce** Steps to reproduce the behavior:...

at_client "crashes" when decryptionService.decrypt() returns a null

7

**Describe the bug** This was originally noticed in spacechat with some @ signs working just fine and others not logging in or not seeing chats. **To Reproduce** Steps to reproduce...

Notifications being marked as delivered but client app does not see them

4

**Describe the bug** Confirmation of notification is received by the sending app (presumably to the secondary being sent to) but the client app does not see the notification. **To Reproduce**...