Page MenuHomePhabricator

[native] Show version unsupported when opened QR screen
AcceptedPublic

Authored by bartek on Mon, Nov 25, 3:54 AM.
Tags
None
Referenced Files
F3386167: D14037.diff
Fri, Nov 29, 3:30 AM
Unknown Object (File)
Wed, Nov 27, 3:29 PM
Unknown Object (File)
Wed, Nov 27, 3:29 PM
Unknown Object (File)
Wed, Nov 27, 3:29 PM
Unknown Object (File)
Wed, Nov 27, 3:29 PM
Unknown Object (File)
Wed, Nov 27, 3:29 PM
Unknown Object (File)
Wed, Nov 27, 3:29 PM
Unknown Object (File)
Wed, Nov 27, 3:29 PM
Subscribers

Details

Reviewers
kamil
angelika
Summary

The QR screen is now for dev-only, but it's theoretically possible to access it via deep link.

For now, the clients aren't able to do it because there are no such QR codes to scan, but in the future after device list launch, they might try doing it on old client versions.
We should display the unsupported version message.

Depends on D14036

Test Plan

Changed isDev condition and opened the QR scanner screen. I was logged out and a message was displayed.

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

bartek held this revision as a draft.
bartek published this revision for review.Mon, Nov 25, 5:09 AM
native/profile/secondary-device-qr-code-scanner.react.js
102

Instead of having isDev checks littered across the codebase, we should create a single constant that controls whether secondary device auth is enabled. (I think @tomek may have already done this?)

The point of having a single "gate" variable is to make sure we don't forget about one of these locations when we're launching the feature.

native/profile/secondary-device-qr-code-scanner.react.js
102

I've just landed a diff where the flag usingRestoreFlow is introduced

kamil requested changes to this revision.Tue, Nov 26, 2:45 AM

I would put this check somewhere earlier in the logic, e.g. in DeepLinksContextProvider.

Requesting to consider this and use usingRestoreFlow

This revision now requires changes to proceed.Tue, Nov 26, 2:45 AM

Move check to deep link context. Use the usingRestoreFlow constant

This revision is now accepted and ready to land.Thu, Nov 28, 1:34 AM