fix: Push notifications toggle

[usame-algan]

What it solves

Resolves #4253

How this PR fixes it

• Fix: ignore failed json parse safe-gateway-typescript-sdk#189 changed the response from being undefined to be an empty object so we check for isEmpty instead of null.

How to test it

1. Open a Safe
2. Go to Notification settings
3. Turn on notifications
4. Sign the message
5. Observe the Toggle turns on

Screenshots

Checklist

• I've tested the branch on mobile 📱
• I've documented how it affects the analytics (if at all) 📊
• I've written a unit/e2e test for it (if applicable) 🧑‍💻

[github-actions]

Branch preview

✅ Deploy successful!

Website:
https://fix_notification_toggle--walletweb.review.5afe.dev/home?safe=eth:0xA77DE01e157f9f57C7c4A326eeE9C4874D0598b6

Storybook:
https://fix_notification_toggle--walletweb.review.5afe.dev/storybook/

[github-actions]

📦 Next.js Bundle Analysis for safe-wallet-web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

One Page Changed Size

The following page changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load
/settings/notifications	27.03 KB (🟡 +10 B)	981.51 KB

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	78.22% (+0.01% 🔼)	11993/15333
🔴	Branches	58.27% (+0.02% 🔼)	3087/5298
🟡	Functions	65.27%	1889/2894
🟡	Lines	79.73% (+0.01% 🔼)	10824/13576

Test suite run success

1484 tests passing in 203 suites.

Report generated by 🧪jest coverage report action from f2e13ab

[jmealy]

Why do we need this check? If we get to this point then we've gotten a 200, no?

[usame-algan]

I also think so otherwise if it threw we would end up in the catch. I assume this was added in case the response is successful but not empty. For now I would leave it as is since the notifications are being reworked on the service side so we will have to touch this again anyway.

[liliya-soroka]

Verified
Toggle works but , notifications are not received.
The issue was reported to the protocol team