Stuck at Fetching BTC address

[bonsfi]

Description:

After signing first Metamask transaction the dapp gets stuck with "fetching BTC address"

Steps to reproduce the behavior:

1. Go to tbtc dapp
2. Start the process and get the first metmask transaction correct at
   https://ropsten.etherscan.io/tx/0x524a357fd66357219ddc623551f77aa58e63b1eb3ed5ee348379c5b7ddcaf94a
3. Then impossible to get to next step because "fetching BTC address" screen gets stuck

Expected behavior:

Having a BTC address to deposit

Environment details:

OS: MacOS Catalina
Web Browser: Google Chrome, Version 83.0.4103.116 (Official Build) (64-bit)
Wallet: Metamask (Chrome extension), Version 7.7.9

Additional context:

Please see messages from Console for better understanding:

Uncaught TypeError: e is not a function
at inpage.js:1
at inpage.js:1
at i (inpage.js:1)
at inpage.js:1
at inpage.js:1
at c (inpage.js:1)
at inpage.js:1
at We (inpage.js:1)
at Object. (inpage.js:1)
at e.exports._runReturnHandlersUp (inpage.js:1)
inpage.js:1 MetaMask - RPC Error: The method undefined does not exist/is not available Object
(anonymous) @ inpage.js:1
inpage.js:1 Uncaught TypeError: e is not a function
at inpage.js:1
at inpage.js:1
at i (inpage.js:1)
at inpage.js:1
at inpage.js:1
at c (inpage.js:1)
at inpage.js:1
at We (inpage.js:1)
at Object. (inpage.js:1)
at e.exports._runReturnHandlersUp (inpage.js:1)
inpage.js:1 MetaMask - RPC Error: The method undefined does not exist/is not available Object
(anonymous) @ inpage.js:1
inpage.js:1 Uncaught TypeError: e is not a function
at inpage.js:1
at inpage.js:1
at i (inpage.js:1)
at inpage.js:1
at inpage.js:1
at c (inpage.js:1)
at inpage.js:1
at We (inpage.js:1)
at Object. (inpage.js:1)
at e.exports._runReturnHandlersUp (inpage.js:1)
inpage.js:1 MetaMask - RPC Error: The method undefined does not exist/is not available Object
(anonymous) @ inpage.js:1
inpage.js:1 Uncaught TypeError: e is not a function
at inpage.js:1
at inpage.js:1
at i (inpage.js:1)
at inpage.js:1
at inpage.js:1
at c (inpage.js:1)
at inpage.js:1
at We (inpage.js:1)
at Object. (inpage.js:1)
at e.exports._runReturnHandlersUp (inpage.js:1)
DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/contentscript.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/inpage.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME

[culgin]

I noticed when I am stuck at this stage, there was an internal transaction error in the deposit transaction,
https://ropsten.etherscan.io/tx/0xa56eb8dd6d7eb012cc1feb5e6d6f112825677231981b4a797319cf0df24a7cdf

I do not have the same console error though.

OS: Windows 10
Web Browser: Firefox, 78.0.2 (64-bit)
Wallet: Metamask (Firefox extension), Version 8.0.4

[Shadowfiend]

This seems like you may have picked up the page in the middle of a deploy. Have y'all seen the issue recently?

@culgin on your additional tidbit---do you have more than one example of transactions that look like that?

[culgin]

@Shadowfiend Here is another similar transaction,
https://ropsten.etherscan.io/tx/0xc5143225cd09db2c4514fa0ea54ab91672e5e918d298f3874a96e26b7f5b3c34#internal

[VVyvrn]

I can confirm experienced this "stuck on fetching BTC" problem, and contract shows internal transaction errors.

https://ropsten.etherscan.io/tx/0xff8a847d5c4f435ad902e2bae56d92643ecdf0d3e4429e06aa39cba79d391419#internal

Steps to reproduce as described above.

Environment: MacOS 10.15.6
Brave Browser Version 1.11.104 Chromium: 84.0.4147.105 (Official Build) (64-bit)
Built-in Brave Metamask wallet

[VVyvrn]

Same issue continuing. Didn't have a log last time, so here's an example:
tbtc-dapp-console-log-1596857606550.txt

Symptoms as described by OP, however my console log looks different...