Order Unfunded error on mesh:8

[SvenMeyer]

Context

• 0x-lauch-kit running on a external machine running ubuntu 19.04 using mesh:7-0xv3 on Kovan testnet (42)
• modified another 0x-launch-kit-frontend only instance to support a new token, contract is deployed on (and only !) Kovan testnet.
  Contract address for all other networks was set to the kovan address , although they do not exist there - that was required because otherwise I got another error and it did not work at all.

    "tokens": [
        {
            "symbol": "feo1",
            "name": "Iron Ore Token Type1",
            "primaryColor": "#333333",
            "icon": "assets/icons/zrx.svg",
            "addresses": {
                "1": "0x1621aec5d5b2e6ec6d9b58399e9d5253af86df5f",
                "3": "0x1621aec5d5b2e6ec6d9b58399e9d5253af86df5f",
                "4": "0x1621aec5d5b2e6ec6d9b58399e9d5253af86df5f",
                "42": "0x1621aec5d5b2e6ec6d9b58399e9d5253af86df5f",
                "50": "0x1621aec5d5b2e6ec6d9b58399e9d5253af86df5f"
            },
            "decimals": 18,
            "displayDecimals": 4
        },

Everything was working fine

https://github.com/SvenMeyer/commx-frontend

On external machine running the 0x-lauch-kit with the backend :

• changed within docker-compose.ymlto mesh:latest
• restarted 0x-lauch-kit docker-compose up

Accessed 0x-launch-kit backend (on on a external machine running ubuntu 19.04) using the same modified 0x-frontend (with support for custom token).
Got error message when trying to create order for the custom token - all other existing standard token were working fine.

[albrow]

Thanks @SvenMeyer we're looking into this.

[dekz]

@SvenMeyer are you still using 0x Mesh 8? This is not officially supported with Launch kit as it still is on Mesh 7.

[SvenMeyer]

no, as described above, I had to revert to mesh:7-0xv3 (in docker-compose.yml) to get it back to work.