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

Can't login #1076

Closed
husam212 opened this Issue May 21, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@husam212

husam212 commented May 21, 2018

After entering the passphrase, once I click on login I get the following error in console.

Error: APIClient requires nodes for initialization. 2 api_client.js:88
	initialize api_client.js:88
	APIClient api_client.js:68
	peerSet peers.js:13:16
	activePeerSet/< peers.js:61:15
	createThunkMiddleware/</</< index.js:11
	activePeerSet index.js:28:25
	onLoginSubmission login.js:73:4
	onFormSubmit login.js:129:4
	onFormSubmit self-hosted:976:17
	callCallback react-dom.development.js:1299
	invokeGuardedCallbackDev react-dom.development.js:1338
	invokeGuardedCallback react-dom.development.js:1195
	invokeGuardedCallbackAndCatchFirstError react-dom.development.js:1209
	executeDispatch react-dom.development.js:1432
	executeDispatchesInOrder react-dom.development.js:1454
	executeDispatchesAndRelease react-dom.development.js:1969
	executeDispatchesAndReleaseTopLevel react-dom.development.js:1980
	forEach self-hosted:261:13
	forEachAccumulated react-dom.development.js:1946
	processEventQueue react-dom.development.js:2139
	runEventQueueInBatch react-dom.development.js:2151
	handleTopLevel react-dom.development.js:2161
	handleTopLevelImpl react-dom.development.js:1800
	batchedUpdates react-dom.development.js:13238
	performFiberBatchedUpdates react-dom.development.js:1646
	stackBatchedUpdates react-dom.development.js:1637
	batchedUpdates react-dom.development.js:1651
	batchedUpdatesWithControlledComponents react-dom.development.js:1664
	dispatchEvent react-dom.development.js:1874
	dispatchEvent self-hosted:1020:17
@slaweet

This comment has been minimized.

Show comment
Hide comment
@slaweet

slaweet May 22, 2018

Member

@husam212 Thank you for reporting the issue.

Can you please provide more information to help us reproduce the issue:

  • What version are you using?
  • What network are you trying to log into?
Member

slaweet commented May 22, 2018

@husam212 Thank you for reporting the issue.

Can you please provide more information to help us reproduce the issue:

  • What version are you using?
  • What network are you trying to log into?
@husam212

This comment has been minimized.

Show comment
Hide comment
@husam212

husam212 May 27, 2018

@slaweet I'm using version 1.3.4 49d1cfa and Mainnet network.

husam212 commented May 27, 2018

@slaweet I'm using version 1.3.4 49d1cfa and Mainnet network.

@slaweet

This comment has been minimized.

Show comment
Hide comment
@slaweet

slaweet May 29, 2018

Member

@husam212 thank you for mentioning the specific commit, that explains a lot. That commit is already from version 2.0.0. We change the version number as the last thing before the release, so it still shows 1.3.4 on that commit. Version 2.0.0 is compatible with Lisk Core 1.0.0 which is not on Mainnet at the moment. So the error is expected.

Member

slaweet commented May 29, 2018

@husam212 thank you for mentioning the specific commit, that explains a lot. That commit is already from version 2.0.0. We change the version number as the last thing before the release, so it still shows 1.3.4 on that commit. Version 2.0.0 is compatible with Lisk Core 1.0.0 which is not on Mainnet at the moment. So the error is expected.

@slaweet slaweet closed this May 29, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment