Scroll Network - Safe SDK could not be initialized

[la1234512345]

Issue Category

Other

What happened?

When the user tries to create a transaction even for simple send of ETH, he gets this error:

On the dev console

• Tried to have him change to atleast have RPCs, and tried using mobile browser as well, same error
• User is using Rabby but had him try Metamask as the signer as well, no hardware wallets, same error
• User is not using VPN nor does have access to one
• User is located in Lima,Peru

Date and time this happened or you first noticed this issue

02/06/2024

Network

Scroll

Safe Address

0xA0A1EF804DA2927C2F1Ff55EE498afbe819C9190

Token Address

No response

Token Type

None

Transactions

No response

[inahlikenoother]

I have another user experiencing the issue when trying to send out ETH
Safe: https://app.safe.global/home?safe=scr:0x3A17f10b4A5d64b3583960430521bC1E530D5d03

[liliya-soroka]

checking...

[liliya-soroka]

Could you get more details from the user:

1. signer wallet
2. rpc in the signer wallet

I can not reproduce the issue and don't see any additional information from the user about the connected wallet

[inahlikenoother]

Could you get more details from the user:

1. signer wallet

2. rpc in the signer wallet

I can not reproduce the issue and don't see any additional information from the user about the connected wallet

Hi @liliya-soroka , first user responded:
signer wallet: 0xe147d670f92887F507dCCd2c7777255370795F3e (Rabby)
RPCs used: https://scroll.blockpi.network/v1/rpc/public , https://scroll-mainnet.chainstacklabs.com/ , https://scroll.drpc.org/

[inahlikenoother]

Could you get more details from the user:

1. signer wallet

2. rpc in the signer wallet

I can not reproduce the issue and don't see any additional information from the user about the connected wallet

For second user:
signer wallet: 0x127aD227fB8a9F3B12984175260Dfc165CCDa8C8 (Rabby, also tried in MetaMask)
RPC used: https://rpc.scroll.io/

[liliya-soroka]

Dear support team, could you help us get more details for debuging? I will lead you how to do it for this issue, as we can not reproduce it on our side.
On the first screenshot, there is an error in the console related to the PRC https://rpc.scroll.io/. As the site can not get access to the RPC, our SDK can not be initialized. To get more details about CORS error for the https://rpc.scroll.io/ RPC, could you ask the user,when there is an CORS error for the RPC in console:

1. open Networks tab in the dev tool

2. find the request to RPC https://rpc.scroll.io/ nd click on it 3. check header to see the response status/ payload and response

[inahlikenoother]

1. in

Thank you Liliya, will ask both users who are experiencing the issue and will update here.

[inahlikenoother]

Hi team, for user with Safe scr:0x3A17f10b4A5d64b3583960430521bC1E530D5d03 confirmed that it's already working and was able to execute a transaction already 🙏

Still waiting for response from the first user with Safe scr:0xA0A1EF804DA2927C2F1Ff55EE498afbe819C9190

[liliya-soroka]

thank you , good to know.
the user had 429 error - rate limit error. The information about the response to the RPC request was provided to the Scroll team for their official RPC https://rpc.scroll.io/

[inahlikenoother]

thank you , good to know. the user had 429 error - rate limit error. The information about the response to the RPC request was provided to the Scroll team for their official RPC https://rpc.scroll.io/

Thank you Liliya. Here is a screenshot of the first user who had this issue with Safe scr:0xA0A1EF804DA2927C2F1Ff55EE498afbe819C9190 they just provided it today

[liliya-soroka]

thank you . I see that this is the same 429 too many requests. We have sent the information to the scroll team

[anitapatel20241]

k you . I see that this is the same 429 too many requests. We have sent the information to the scroll t

I'm the wallet owner. Where can I follow the issue with the scroll team? I'm surprised only me is complaining as I tried several wallets and all of them get the same error, now even when connecting to safe using scroll.

[anitapatel20241]

@liliya-soroka It just worked today. Seems the scroll team finally solved their issue. Thank you very much for your kind assistance with this.

[phoebe-serveth]

User confirmed it's working now, closing this ticket.