Closed WietzeSlagman closed 6 months ago
What type of error are you observing now (that differs from the one it checks)? I'm not sure if the error changed because app.inter.trade and psm.inter.trade still function properly.
This should be fixed now. We removed the error callback on watchLatest
and changed the chain storage watcher to emit an undefined value for vstorage paths with no data instead of giving back an error. Now we just check if the value is missing to know if the smart wallet exists. Other types of errors, like network/500-errors when doing queries, are now surfaced in the error callback passed to makeAgoricChainStorageWatcher
.
closes: #50 refs: #42
Description
Ensure that the chainStorageWatcher does not throw when there is no smart-wallet present.
Initial fix with additional checks in #42 no longer works, most likely due to updated wallet factory?
Security Considerations
Assuming an error with
!lastPaths
is always going to be a smart-wallet not provisionedScaling Considerations
Documentation Considerations
Testing Considerations
Tests still pass