-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Changes to sync codephrase #22242
Closed
AlexeyBarabash opened this issue
Apr 12, 2022
· 5 comments
· Fixed by brave/brave-core#12300 or brave/brave-core#13483
Closed
Changes to sync codephrase #22242
AlexeyBarabash opened this issue
Apr 12, 2022
· 5 comments
· Fixed by brave/brave-core#12300 or brave/brave-core#13483
Labels
feature/sync
OS/Android
Fixes related to Android browser functionality
OS/Desktop
QA Pass - Android ARM
QA Pass - Android Tab
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-All-Platforms
QA/Test-Plan-Specified
QA/Yes
release-notes/include
Milestone
Comments
AlexeyBarabash
added
OS/Android
Fixes related to Android browser functionality
OS/Desktop
labels
Apr 12, 2022
25 tasks
AlexeyBarabash
added a commit
to brave/brave-core
that referenced
this issue
Apr 14, 2022
AlexeyBarabash
added a commit
to brave/brave-core
that referenced
this issue
Apr 19, 2022
AlexeyBarabash
added a commit
to brave/brave-core
that referenced
this issue
Apr 20, 2022
AlexeyBarabash
added a commit
to brave/brave-core
that referenced
this issue
Apr 26, 2022
AlexeyBarabash
added a commit
to brave/brave-core
that referenced
this issue
May 13, 2022
iOS issue to track here |
AlexeyBarabash
added a commit
to brave/brave-core
that referenced
this issue
May 25, 2022
25 tasks
This was referenced May 30, 2022
stephendonner
added
QA/Test-All-Platforms
QA/Test-Plan-Specified
QA/In-Progress
Indicates that QA is currently in progress for that particular issue
and removed
QA/In-Progress
Indicates that QA is currently in progress for that particular issue
labels
Jun 9, 2022
Verification
|
Brave | 1.41.74 Chromium: 103.0.5060.53 (Official Build) beta (x86_64) |
---|---|
Revision | a1711811edd74ff1cf2150f36ffa3b0dae40b17f-refs/branch-heads/5060@{#853} |
OS | macOS Version 11.6.7 (Build 20G630) |
NOTE: Android's tests here were run on June 29th; original desktop tests were run on June 21st, hence the desktop/Android date discrepancies in the notes.
Case I: Old sync words are accepted before sync words sunset date - PASSED
- Created a new sync chain on
1.40.105
desktop browser (24 words) - Connected
1.41.74
desktop browser to the chain - Connected
1.41.84
Android browser to the chain via code words - Connected
1.41.84
Android browser to the chain va QR code
example | example | example | example | example |
---|---|---|---|---|
Case II. Old sync words are NOT accepted after sync words sunset date - PASSED
- Create chain on
1.39.122
desktop browser (24 words) - Modify current date on the client (2nd) desktop to
August 2, 2022
- Try to connect
1.41.x
desktop browser to the chain - it should sayThis code was generated by a deprecated version of Brave, please upgrade your other device first.
- Try to connect
1.41.x
Android to the chain via code words; it should say `Sync could not be setup [This code was generated by a deprecated version of Brave, please upgrade your other device first]
example | example | example | example | example |
---|---|---|---|---|
Case III. Normal flow between new (v2
) versions - PASSED
- Created sync chain on
1.41.59
desktop version (25 words) - Connected
1.41.x
desktop to chain via code words - Connected
1.41.x
Android to chain via code words
Sync chain | new client joined | Synch chain updated | Android client |
---|---|---|---|
Case IV. Expired error - PASSED
- Create sync chain on
1.41.x
desktop version (25 words) - Adjust time on 2nd desktop device 2 days forward (
June 23, 2022
in my case) - Connect new browser desktop to chain via words - it should say
This code has expired. Please generate a new one on your other device and try again.
- Adjust time on Android device 2 days forward (
July 1, 2022
in my case) - Connected
1.41.x
Android device to chain via code words - it saidThis code has expired. Please generate a new one on your other device and try again.
example | example | example | example | example | example | example |
---|---|---|---|---|---|---|
Case V. Too-far-in-the-future codes - PASSED
- Create sync chain on
1.41.x
desktop version (25 words) - Adjust time on 2nd desktop device 2 days backwards (
June 19, 2022
in my case) - Connect new browser desktop to chain via words - it should say
This code is invalid. Please check that the time and timezone are set correctly on your device.
- Adjust time on Android device 2 days backwards (
June 27, 2022
) in my case) - Connect
1.41.x
Android browser to Sync chain via code words; it saidThis code is invalid. Please check that the time and timezone are set correctly on your device.
example | example | example | example | example | example |
---|---|---|---|---|---|
Case VI. General errors for incorrect codes - PASSED
Verification
Filed #23772 Case I: Old sync words are accepted before sync words sunset date - PASSED
Case II. Old sync words are NOT accepted after sync words sunset date- PASSED
Case III. Normal flow between new (
|
Ex1 | Ex2 | Ex3 | Ex4 | Ex5 | Ex6 |
---|---|---|---|---|---|
Case IV. Expired error - PASSED
- Create sync chain on
1.41.x
desktop version (25 words) - Adjust time on 2nd desktop device 2 days forward (
June 23, 2022
in my case) - Connect new browser desktop to chain via words - it should say
This code has expired. Please generate a new one on your other device and try again.
- Confirmed - Adjust time on Android device 2 days forward
- Connect new browser Android to chain via words - it also should say
This code has expired. Please generate a new one on your other device and try again.
- Confirmed
Ex1 | Ex2 | Ex3 | Android1 | Android2 |
---|---|---|---|---|
Case V. Too-far-in-the-future codes - PASSED
- Create sync chain on
1.41.x
desktop version (25 words) - Adjust time on 2nd desktop device 2 days backwards (
June 19, 2022
in my case) - Connect new browser desktop to chain via words - it should say
This code is invalid. Please check that the time and timezone are set correctly on your device.
- Confirmed - Adjust time on 2nd Android device 2 days backwards;
- Connect new browser Android to chain via words - it also should also say
This code is invalid. Please check that the time and timezone are set correctly on your device. - Confirmed
Ex1 | Ex2 | Ex3 | Ex4 | Ex5 | Ex6 |
---|---|---|---|---|---|
Case VI. General errors for incorrect codes - PASSED
- Try to enter the sync chain on
1.41.x
desktop with wordsAAA BBB CCC
, etc.- it should sayThis code is invalid
Confirmed - Try to enter the sync chain on new Android with words AAA BBB CCC - it should also say
- Wrong sync code Confirmed
- Try to enter the sync chain on
1.41.x
desktop with 24 words - it should sayThis code is invalid
- Try to enter the sync chain on
1.41.x
desktop with 25 words - it should sayThis code is invalid
- Try to enter the sync chain on
1.41.x
desktop with 26 words - it should sayThis code is invalid
Ex1 | Ex2 | android | 24words-error | 25words-error | 26words-error |
---|---|---|---|---|---|
Verification
|
Brave | 1.41.80 Chromium: 103.0.5060.53 (Official Build) beta (64-bit) |
---|---|
Revision | a1711811edd74ff1cf2150f36ffa3b0dae40b17f-refs/branch-heads/5060@{#853} |
OS | Linux |
Case I: Old sync words are accepted before sync words sunset date - PASSED
- Created a new sync chain on
1.40.105
desktop browser (24 words) - Connected
1.41.74
desktop browser to the chain
example | example | example | example |
---|---|---|---|
Case II. Old sync words are NOT accepted after sync words sunset date - PASSED
- Create chain on
1.39.122
desktop browser (24 words) - Modify current date on the client (2nd) desktop to
August 2, 2022
- Try to connect
1.41.x
desktop browser to the chain - it should sayThis code was generated by a deprecated version of Brave, please upgrade your other device first.
example | example | example | example |
---|---|---|---|
Case III. Normal flow between new (v2
) versions - PASSED
- Create sync chain on
1.41.59
desktop version (25 words) - Connect new browser desktop to chain via words - it should succeed
Sync chain | new client joined | Sync chain updated |
---|---|---|
Case IV. Expired error - PASSED
- Create sync chain on
1.41.x
desktop version (25 words) - Adjust time on 2nd desktop device 2 days forward (
June 29, 2022
in my case) - Connect new browser desktop to chain via words - it should say
This code has expired. Please generate a new one on your other device and try again.
example | example | example |
---|---|---|
Case V. Too-far-in-the-future codes - PASSED
- Create sync chain on
1.41.x
desktop version (25 words) - Adjust time on 2nd desktop device 2 days backwards (
June 25, 2022
in my case) - Connect new browser desktop to chain via words - it should say
This code is invalid. Please check that the time and timezone are set correctly on your device.
example | example | example | example |
---|---|---|---|
Case VI. General errors for incorrect codes - PASSED
Verification passed on Oppo Reno 5(Android 12) /Samsung Tab A (Android 10) running 1.41.94 x64 build Case 1: Sync between devices running v2 version with cross time zones
Case 2: Old sync words are accepted before sync words sunset date
Case 3: Old sync words are NOT accepted after sync words sunset date (Partial Pass)
Case 4: Case for expired error
Case 5: Case for too far in the future error
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feature/sync
OS/Android
Fixes related to Android browser functionality
OS/Desktop
QA Pass - Android ARM
QA Pass - Android Tab
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-All-Platforms
QA/Test-Plan-Specified
QA/Yes
release-notes/include
See details at https://github.com/brave/internal/issues/869, Android and Desktop part
The text was updated successfully, but these errors were encountered: