-
-
Notifications
You must be signed in to change notification settings - Fork 276
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
feat(mobile): native connect popup POC #14262
Conversation
a2c79b0
to
68b50f7
Compare
} | ||
|
||
if (discoveryActive) { | ||
return <Loader size="large" title="Discovery running, pls wait :(" />; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's follow up on this later
@Nodonisko We think this PR would be useful to be in |
/rebase |
Start rebasing: https://github.com/trezor/trezor-suite/actions/runs/11012717275 |
5572148
to
47deadd
Compare
suite-native/module-connect-popup/src/components/ButtonRequestsOverlay.tsx
Outdated
Show resolved
Hide resolved
suite-native/module-connect-popup/src/components/ConnectPopupDebugOptions.tsx
Outdated
Show resolved
Hide resolved
...-native/module-authorize-device/src/screens/passphrase/PassphraseFeatureUnlockFormScreen.tsx
Outdated
Show resolved
Hide resolved
Good job, overall it looks really nice! |
47deadd
to
5d301f8
Compare
Can you please maybe add some video how does it looks like now? |
suite-native/module-authorize-device/src/hooks/useOnDeviceReadyNavigation.ts
Outdated
Show resolved
Hide resolved
0441279
to
afb76de
Compare
suite-native/module-authorize-device/src/hooks/useOnDeviceReadyNavigation.ts
Show resolved
Hide resolved
suite-native/module-connect-popup/src/hooks/useConnectPopupNavigation.ts
Show resolved
Hide resolved
suite-native/module-connect-popup/src/screens/ConnectPopupScreen.tsx
Outdated
Show resolved
Hide resolved
Very good job guys :) Please, what is the best way to test it? How can I play with it? |
Best way to test it the whole process is to run |
const getButtonRequestComponent = (request: ButtonRequest) => { | ||
if (request.code === 'ButtonRequest_Address') { | ||
return ( | ||
<Box paddingBottom="extraLarge" key={request.code}> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: request.code
may not be unique, there can be multiple button request with the same code on the device...
@@ -150,6 +156,7 @@ export const PassphraseForm = ({ inputLabel, onFocus }: PassphraseFormProps) => | |||
horizontalMargin={FORM_CARD_PADDING} | |||
/> | |||
<EnterPassphraseOnTrezorButton /> | |||
{noPassphraseEnabled && <NoPassphraseButton />} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's just a workaround, right? I guess in the end we should not request passphrase for standard wallets and user will have to choose the wallet before processing the request. Another workaround for all devices except T1 is entering passphrase on Trezor (you can enter empty passphrase there)...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't mind this workaround, it does not affect the regular flow, so we can merge it.
lgtm |
5dea4aa
to
ef51c96
Compare
55ee24f
to
c7f9d1f
Compare
Description
Don't forget to run
yarn prebuild
if you do any changes toapp.config.ts
Related Issue
Resolve
Screenshots:
Screen.Recording.2024-09-24.at.14.09.50.mov