You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 6, 2019. It is now read-only.
circles-api branch: ecs-deploy (with the bug/web3-connection-drop branch of metatx-server instead of the package)
circles-mobile branch: circlestoken-fixes
So I reverted some of my changes to the FE because I thought Ashoka's stuff might be more illuminating.
The current build with fail at the user reducer:
case USER_TOKEN_CREATED:
letlogs=action.txReceipt.data.logslogs=logs.filter(log=>log.address.toLowerCase()===HubContract.address.toLowerCase())letuserAddress='0x'+logs[0].topics[1].substr(-40)lettokenAddress='0x'+logs[0].topics[2].substr(-40)returnObject.assign({},state,{token_address: tokenAddress})
because the metatx-server package returns just the tx hash, and not the receipt, but the receipt does not contain any logs anyway.
The text was updated successfully, but these errors were encountered:
Ok so current setup is this
circles-contracts
branch: feature/relayerPermissionscircles-api
branch: ecs-deploy (with the bug/web3-connection-drop branch ofmetatx-server
instead of the package)circles-mobile
branch: circlestoken-fixesSo I reverted some of my changes to the FE because I thought Ashoka's stuff might be more illuminating.
The current build with fail at the user reducer:
because the
metatx-server
package returns just the tx hash, and not the receipt, but the receipt does not contain anylogs
anyway.The text was updated successfully, but these errors were encountered: