We're integrated Unisat with our dApp. One of our users have a reported an issue where after triggering transaction in dapp, the Unisat opens with the Cannot read properties of null (reading '1') error like this:
Also we've noticed something that looks like a non-latin character on the below screenshot provided by our user (after (reading '1') in the stack field):
Can you help us with the investigation? We're not sure where the problem lies and if there's something that can be done to mitigate it.
GGG888GGG
commented
2 months ago
We're integrated Unisat with our dApp. One of our users have a reported an issue where after triggering transaction in dapp, the Unisat opens with the
Cannot read properties of null (reading '1')error like this:Our user uses Korean in their OS. I suspect this may be somehow related to the issue, as two other tickets I found with the similar problem (https://github.com/unisat-wallet/extension/issues/150, https://github.com/unisat-wallet/extension/issues/143) also look like tickets created from OSes that use non-latin based alphabets.
Also we've noticed something that looks like a non-latin character on the below screenshot provided by our user (after
(reading '1')in thestackfield):Can you help us with the investigation? We're not sure where the problem lies and if there's something that can be done to mitigate it.