Core Apps » ChatSecure:Android

Major Progress! Cold start is smoother and works with Paik-provided nickname.

The question is are any of these blockers for shipping on your end, or not? Also, in general, please don't set due dates and target releases for tickets when you are reporting the bug as a user/tester.

0. Cold-start messages to user are fine for typical chat usage, but might be unfamiliar and jarring to Paik user. Will put design input into this >to define a solution for future.

Happy to address in next v14 release.

1. On cold-start: the first-time invocation of ChatSecure for multi-user chat creates a chatroom called "Persian-Paik-Chat", instead of using the >"story_7e....." name provided. Subsequent invocations do use the name provided.

We only use "Persian_Paik_Chat" if that was provided by your side. When you do the general chat, that is the string that is sent. When you say "first time invocation" are you sure you weren't starting up the general group chat option?

2. Failure scenario (consistent): in ChatSecure, leave a multi-user chat (hardware BACK); return to Paik, select any already-was-in-discussion >Paik article to read, and try to enter the discussion again. Fail. Paik launches ChatSecure successfully (get message about joining chat room), >but ChatSecure black-screen-fails (operating system message "Unfortunately, ChatSecure has stopped").

Looking into it. Issue is likely due to the fact that you are asking to join an already-joined multi-user chat option. We didn't design the intent API to handle that at this point.

3. failure scenario: After initial use of ChatSecure for anonymous group discussion, close Paik, then start ChatSecure from home screen. Tap for >menu, and select ACCOUNTS, then select to add a new account. Choose option to add existing account, then Google account. Allow ChatSecure to suck >in all contact info, etc. Leave this account ON/ACTIVE. Quit ChatSecure. Now, restart Paik and ask to join a group discussion. When invoked, >messages from this user use the Google account name, not the anonymous group chat name. This error happened on Galaxy S3, did NOT happen on Nexus

This was specifically targeted to be fixed and tested multiple times. Not sure how it could happen on S3 but not Nexus. This does not seem like a blocking issue either way.

7. Tried many modes (e.g. which user starts a chat vs which user joins an existing chat) but when it DID fail, it always failed. Good News: if >user turns OFF the Google account, this scenario works. So, the mere presence of the Google account did not cause the problem. Presence + turned >on = problem (S3 device).

Will need to do S3 specific testing to reproduce there.

4. During/After using the anonymous account for group discussion, and then "backing out" and returning to Paik, ChatSecure will show an empty >contacts list (instead of showing the one or more chatrooms that this user has joined). Message is displayed saying "No Contacts - tap to invite".

Did this happen when you had setup multiple accounts or just the one created by Paik?

5. Paik supplies nickname "N", ChatSecure changes this to "NXXX" where "XXX" are 3 digits. Bug or feature?

The goal was to avoid any name collision with common nicknames provided by the user in Paik. We did not want to have to go through the process of "sorry that name is taken" etc, so we just generate a random short numeric tag for the end to avoid collision. Feature!