Embark.Names requires a synced node

[3esmit]

Bug Report

Summary

When I use 'embark upload livenet' it always gives me this error when using Embark Names:

It works only when 'embark upload livenet' connects to a node that was running for some time and have the state loaded (synced node).

Current behavior

TBD

How to reproduce

TBD

Expected behavior

Embark.Names don't need a synced node, just needs to know what is the configuration to use for that particular network. Also, it should know all network addresses, e.g. If the dapp is multichain, it would need to be deployed a different app for each different chain.

I suggest adding this as constants that have to be defined in the namesystem.js, otherwise Embark.Names would attempt to deploy them, and all the addresses for all networks should be available for the UI, which would inform its chainID and get the correct provider.

$ embark run --nodashboard --logfile log.txt --loglevel trace

Please provide additional information about your system

OS: Linux Embark Version: 5.2.3 Node Version: 10.17.0 NPM Version: 6.11.3

Sometimes issues are related to Embark's installation. Can you provide information on how Embark was installed?

As dependency of project (run with npx embark)