Ref: #830
We noticed problems with connecting Xverse and Unisat wallets in the dApp on production. Users are redirected to the Chrome store even though they have the extension installed. It started happening after I initially tried to connect with an invalid network selected in the wallet. The bug is that the window.unisat and window.XverseProviders.BitcoinProvider have undefined values. The orangekit package refers to these fields under the hood and the isInstalled function always returns false.
NOTE:
We noticed different behavior in development and production builds. In the production build window.unisat and window.XverseProviders.BitcoinProvider are undefined even though they are installed. This weird bug can be only reproduced on the production build. It doesn't exist in development mode. We managed to fix it in #830, but it's more of a workaround to unblock production. It requires further investigation to understand exactly what is going on and determine whether it is a bug on orangekit or our side.
Ref: #830
We noticed problems with connecting Xverse and Unisat wallets in the dApp on production. Users are redirected to the Chrome store even though they have the extension installed. It started happening after I initially tried to connect with an invalid network selected in the wallet. The bug is that the
window.unisat andwindow.XverseProviders.BitcoinProviderhave undefined values. The orangekit package refers to these fields under the hood and the isInstalled function always returns false.NOTE:
We noticed different behavior in development and production builds. In the production build
window.unisatandwindow.XverseProviders.BitcoinProviderareundefinedeven though they are installed. This weird bug can be only reproduced on the production build. It doesn't exist in development mode. We managed to fix it in #830, but it's more of a workaround to unblock production. It requires further investigation to understand exactly what is going on and determine whether it is a bug on orangekit or our side.