mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-12-02 14:15:06 +01:00
4ef908aeb2
This reverts commit f5265c24ab.
Apparently it wasn't unnecessary after all. The Lock page served a few
different purposes. First, it was used to safeguard the seed phrase, in
case the user was interrupted after setting a password. Otherwise
anyone could open MetaMask and see the seed phrase without verifying
the password. Second, the submit function for the initialization unlock
screen also returned the seed phrase, so that it could be set in React
state for the confirmation step. Third, the submit function was also
responsible for navigating back to the seed phrase reveal page.
Removing the lock page had the effect of causing an infinite render
loop if onboarding was interrupted in the "Create" flow after setting
a password but before seed phrase confirmation. That redirect loop has
now been fixed.
27 lines
648 B
JavaScript
27 lines
648 B
JavaScript
import React, { PureComponent } from 'react'
|
|
import PropTypes from 'prop-types'
|
|
import Loading from '../../components/ui/loading-screen'
|
|
import { DEFAULT_ROUTE } from '../../helpers/constants/routes'
|
|
|
|
export default class Lock extends PureComponent {
|
|
static propTypes = {
|
|
history: PropTypes.object,
|
|
isUnlocked: PropTypes.bool,
|
|
lockMetamask: PropTypes.func,
|
|
}
|
|
|
|
componentDidMount() {
|
|
const { lockMetamask, isUnlocked, history } = this.props
|
|
|
|
if (isUnlocked) {
|
|
lockMetamask().then(() => history.push(DEFAULT_ROUTE))
|
|
} else {
|
|
history.replace(DEFAULT_ROUTE)
|
|
}
|
|
}
|
|
|
|
render() {
|
|
return <Loading />
|
|
}
|
|
}
|