Guardian Project Dev (ARCHIVED SITE)

05/07/2014

07:26 pm ChatSecure:Android Bug #3343: Group Chat: short right aligned messages are not fully right aligned

For some reason the 'received' messages passed by smack contain a whole heap of '\t' and whitespace characters. This...

05/05/2014

08:13 pm ChatSecure:Android Bug #3343 (New): Group Chat: short right aligned messages are not fully right aligned

When in a group chat, any messages by oneself are aligned to the right and not prefixed with the chat nickname.
Fo...

04/28/2014

06:10 pm ChatSecure:Android Bug #3289: Group Chat: ActionBar changes to non-group chat layout when non group chat is also open

Fix added with pull request 443 (https://github.com/guardianproject/ChatSecureAndroid/pull/443)

06:03 pm ChatSecure:Android Revision a108301c (chatsecureandroid): bug 3289 - ActionBar changes to non-group chat layout when...

04/25/2014

12:38 pm ChatSecure:Android Bug #3289: Group Chat: ActionBar changes to non-group chat layout when non group chat is also open

After some debugging I believe the error to be in ChatView.java - Method updateWarningView() - Line 1323.
The Meth...

04/23/2014

08:13 pm ChatSecure:Android Bug #3289 (New): Group Chat: ActionBar changes to non-group chat layout when non group chat is al...

After initiating a group chat (by joining an existing MUC) the action bar looks as it should for group chats (no 'loc...

06:55 pm ChatSecure:Android Bug #3194: Dark Theme: Message View not dark on HTC One M7

Bug is fixed since the latest update - can be closed.

04/14/2014

06:17 pm ChatSecure:Android Revision 7ad7ec54 (chatsecureandroid): Possible solution for bug 3110 - using a single AccountLis...

Signed-off-by: n8fr8 <nathan@freitas.net>

06:14 pm ChatSecure:Android Revision 28c80d77 (chatsecureandroid): Bug #3111 - return missing string signed_out_prompt_with_e...

Signed-off-by: n8fr8 <nathan@freitas.net>

04/05/2014

12:34 pm ChatSecure:Android Bug #3144: Invitation to MultiUserChat (GroupChat) always accepted blindly as standard chat

The message listener will in fact receive exactly the same packet (same object ID in memory) - thus we can ignore it ...