-
Notifications
You must be signed in to change notification settings - Fork 523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError in NotificationsList Component on Service Worker Subscription Fetch #8006
Labels
Comments
Hi, @coronasafe/care-frontend-maintainers, This issue has been automatically marked as stale because it has not had any recent activity. |
Hey, I would like to fix this issue. Please assign it to me. |
@Yadavanurag13 The issue had been assigned to you, not sure if you missed the assignment. |
@gigincg Sorry, I forgot to mention this in our previous chat. I removed my assignment 3 weeks earlier. |
6 tasks
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
A TypeError occurred within the NotificationsList component of our application, specifically during the execution of the initialSubscriptionState function. This error impacts users on the Chrome Mobile iOS browser, as seen in a recent log from our production environment.
Description
When the function initialSubscriptionState tries to fetch the subscription status from the service worker, it fails because the subscription object returned by pushManager.getSubscription() is unexpectedly undefined. This indicates that the service worker might not be properly initialized or the pushManager is not available in the current browser context at the time of invocation.
Steps to Reproduce
Expected Behavior
The application should safely check for the availability of the service worker and gracefully handle cases where the push manager's subscription object is undefined.
Actual Behavior
The application encounters a TypeError and may impact the user experience by halting subsequent JavaScript execution, potentially leading to a partially rendered or non-responsive page.
The text was updated successfully, but these errors were encountered: