[Bug]: Error appears in the console when the PolKaGate snap send button is clicked

[hjetpoluru]

Describe the bug

A bug has been identified where an error message is displayed in the console upon clicking the send button in the PolKaGate snap.

Expected behavior

Send screen should appear without any errors

Screenshots/Recordings

Steps to reproduce

1. Add PolkaGate snap from the directory.
2. Navigate to the extension app and select on the PolkaGate snap, click on the send button
3. Observe the error in the console.

Error messages or log output

Error#4: Cannot read properties of undefined (reading 'genesisHash')

Detection stage

In production (default)

Version

12.11.0

Build type

Flask

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

No response

[Nick-1979]

Hi @hjetpoluru ,

This error does not affect users. The console error occurs only for users who do not have any tokens to transfer, so it appears in the console without impacting functionality. However, this issue has been addressed in the upcoming version, which will be released soon.

Thanks for the report!

[hjetpoluru]

@Nick-1979, thanks for looking into the issue. Do let me know about the upcoming version and I will close the ticket accordingly.

Another minor issue in the Contact US link does not work. Could you please take a look.

Update - It takes a really long time for the email ID to load: mailto:[email protected]. I feel that you could include the actual email address instead.

Screen.Recording.2025-01-29.at.10.46.39.AM.mov

[hjetpoluru]

I have raised separate bug for email is not displayed in the dialog - #29977

[Nick-1979]

@hjetpoluru

Version 2.0.0 has already been submitted for allowlisting, which includes a fix for the console log issue.

Regarding the Contact Us issue, this is the intended behavior of the Link component—it doesn’t display the email address directly but opens a new email dialog when clicked, based on your OS’s default email application. As a result, this appears to be a component-level behavior rather than an issue on our end. It may need to be addressed within the Link component itself.

Screen.Recording.2025-01-30.at.10.31.09.mov