Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Unable to Send Lisk: Expected type string but found type null #293

Closed
revelations86 opened this issue Oct 12, 2016 · 2 comments
Closed

Unable to Send Lisk: Expected type string but found type null #293

revelations86 opened this issue Oct 12, 2016 · 2 comments
Assignees
@karmacoma
Labels
type: bug

Comments

@revelations86
Copy link

Hi,

I am attempting to send List from my address, but I keep getting an error of "Expected type string but found type null". If I try to send out from the Lisk Nano client, I get "Invalid transaction timestamp" error. Can you please tell me what I'm doing wrong and how to fix this?
@karmacoma karmacoma mentioned this issue Oct 13, 2016
Closed
@karmacoma karmacoma self-assigned this Oct 13, 2016
@karmacoma
Copy link
Member

Thanks for reporting this bug. The "Expected type string but found type null" error is a bug affecting accounts from which no funds have ever been sent.

This looks to be an issue in https://github.com/LiskHQ/lisk-ui, therefore have moved here: https://github.com/LiskHQ/lisk-ui/issues/75, and we will fix asap.

For Lisk Nano, please ensure your operating system clock is sync with the correct time. This should resolve the "Invalid transaction timestamp" error you are seeing.

Thanks for your patience.

@karmacoma karmacoma reopened this Oct 28, 2016
@karmacoma karmacoma changed the title Unable to Send Lisk Unable to Send Lisk: Expected type string but found type null Oct 28, 2016
@Phoenix1969
Copy link

cool

karmacoma added a commit that referenced this issue Nov 2, 2016
@karmacoma
Backporting changes from development.
6e30d5f 
- Do not apply or undo transaction when syncing (before processing).
- Fixed #293. Expected type string but found type null @Isabello.
- Closed #285. Moved TOP=true param. to config.json @Isabello.
- Fixed state filter on GET /api/peers/ endpoint.
- Using extend consistently for all object extension.
- Handling NaN port in Peers.prototype.inspect.
- Revised and improved schema validations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@karmacoma karmacoma

Labels
type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@karmacoma @Phoenix1969 @revelations86