User Denied Transaction Error doesn't get caught in callback function although it logs by inpage.js in console.

[AntonCorbijn]

Bug Reports:
After installed latest version (4.7.0) of Metamask, when rejecting transaction, MetaMask throws error "User denied transaction signature" by inpage.js in chrome console but it was not caught in callback as exception.

• Expected Behavior
  I would expect to catch the error inside of callback. For example
  TestContract.callFunction({from: defaultAddress}, function (err, res) {
  // handle err here
  console.log(err)
  });
• Actual Behavior
  I got nothing from console.log(err) although I can see "User denied transaction signature" error log by inpage.js in console.
• Browser Used
  Chrome V66.0.3359.181
• Operating System Used
  OSX 10.11.6
  

[Artod]

Same issue

[andrewsource147]

Same, team please look at this. I added try catch but it didn't work

[Arctek]

This breaks a number of dApps as it leaves them in an unresolved state, waiting for the promise to fulfill or throw.

[jjingrong]

+1
This was working pre 4.7.0

[wjmelements]

Perhaps 71a6e97

[wjmelements]

I will try a build that reverts #4384

[yuxulong00]

Same issue

[wjmelements]

I am somewhat confident that this is related to createErrorMiddleware from #4245

[wjmelements]

whoops it's from ce28344, not 4245

[wjmelements]

#4199

[wjmelements]

This is a dupe of #4431