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

Fix description of verified sessions (PSG-991) #7533

Merged
merged 5 commits into from
Nov 9, 2022

Conversation

onurays
Copy link
Contributor

@onurays onurays commented Nov 7, 2022

Type of change

  • Feature
  • Bugfix
  • Technical
  • Other :

Content

We needed to create new string key to deprecate translations of other languages.

Motivation and context

Screenshots / GIFs

Tests

  • Enable new session management from Labs settings
  • Navigate to Settings > Security & Privacy > Show All Sessions
  • Click View Details button of the verified current session section
  • Click "Learn more" and see the new description in bottom sheet
  • The same result is applied to session details of a verified session in other sessions section

Tested devices

  • Physical
  • Emulator
  • OS version(s):

Checklist

@onurays onurays requested review from a team and bmarty and removed request for a team November 7, 2022 11:51
Copy link
Contributor

@mnaturel mnaturel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Can you add more details about the change into the PR description?

@@ -3373,7 +3373,9 @@
<string name="device_manager_learn_more_sessions_unverified_title">Unverified sessions</string>
<string name="device_manager_learn_more_sessions_unverified">Unverified sessions are sessions that have logged in with your credentials but not been cross-verified.\n\nYou should make especially certain that you recognise these sessions as they could represent an unauthorised use of your account.</string>
<string name="device_manager_learn_more_sessions_verified_title">Verified sessions</string>
<!-- TODO TO BE REMOVED -->
<string name="device_manager_learn_more_sessions_verified">Verified sessions have logged in with your credentials and then been verified, either using your secure passphrase or by cross-verifying.\n\nThis means they hold encryption keys for your previous messages, and confirm to other users you are communicating with that these sessions are really you.</string>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tools:ignore="UnusedResources" needs to be added on the key which has to be removed.

@onurays
Copy link
Contributor Author

onurays commented Nov 7, 2022

LGTM. Can you add more details about the change into the PR description?

Thank you, test steps are added.

Copy link
Member

@bmarty bmarty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a small remark about the wording, else LGTM.

<string name="device_manager_learn_more_sessions_verified">Verified sessions have logged in with your credentials and then been verified, either using your secure passphrase or by cross-verifying.\n\nThis means they hold encryption keys for your previous messages, and confirm to other users you are communicating with that these sessions are really you.</string>
<string name="device_manager_learn_more_sessions_verified_description">Verified sessions are anywhere you are using ${app_name} after entering your passphrase or confirming your identity with another verified session.\n\nThis means that you have all the keys needed to unlock your encrypted messages and confirm to other users that you trust this session.</string>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other sessions are not necessarily using Element (${app_name} here). To check with product, because it is maybe a bit technical to replace with a Matrix client, even if this is more true.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we could use "anywhere you are using this account"? @jakewb-b WDYT?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

anywhere you are using this account

Yes, that's ideal. Thanks for spotting that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, done.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should also warn other platforms of this change so that we use the same text everywhere to be consistent.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@onurays in case you have done so already, could you update our internal task that tracks this to reflect the wording change? If some platforms have already done this task, they may need a separate ticket.

@sonarcloud
Copy link

sonarcloud bot commented Nov 9, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 1 Code Smell

0.0% 0.0% Coverage
0.0% 0.0% Duplication

@onurays onurays merged commit 76b179e into develop Nov 9, 2022
@onurays onurays deleted the feature/ons/fix_device_manager_verified_desc branch November 9, 2022 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants