production tickets is broken

[cellog]

I just bought my ticket to the nft meetup, and the page froze on "Payment sent". Investigating further yielded the following:

This is in web3Service:

  async getTransaction(transactionHash, defaults) {
    return Promise.all([this.provider.getBlockNumber(), this.provider.getTransaction(transactionHash)]).then(async ([blockNumber, blockTransaction]) => {
      // Let's find the type of contract before we can get its version
      const to = blockTransaction ? blockTransaction.to : defaults.to;

The defaults array does not have to set in it!

The defaults is set in web3Middleware:

        // When a new transaction was created, retrieve it
        if (action.type === NEW_TRANSACTION) {
          web3Service.getTransaction(
            action.transaction.hash,
            action.transaction
          )
        }

This is totally standard, the paywall does the same thing. The NEW_TRANSACTION action was dispatched from:

    walletService.on(
      'transaction.new',
      (transactionHash, from, to, input, type, status) => {
        // At this point we know that a wallet was found, because a new transaction
        // cannot be created without it
        dispatch(gotWallet())
        dispatch(
          newTransaction({
            hash: transactionHash,
            to,
            from,
            input,
            type: transactionTypeMapping(type),
            status,
            network: getState().network.name,
          })
        )
      }
    )

This implies that walletService sent out a 'transaction.new' event without a filled in to field. However, the state is correct:

Unfortunately, the redux action that was the basis of this scrolled away before I figured out I needed to look at it.

[julien51]

I think the to thing might be a different bug. Probably a transaction from locksmith on a different chain rinkeby vs. mainnet.

[cellog]

I saw the same error with a new event I created on staging in coinbase wallet FYI