Skip to content
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

Blazor Server-side Loses Connection Upon Extended Phone Lock #41791

Closed
1 task done
Mike-E-angelo opened this issue May 22, 2022 · 2 comments
Closed
1 task done

Blazor Server-side Loses Connection Upon Extended Phone Lock #41791

Mike-E-angelo opened this issue May 22, 2022 · 2 comments
Labels
area-blazor Includes: Blazor, Razor Components feature-blazor-server ✔️ Resolution: Duplicate Resolved as a duplicate of another issue Status: Resolved

Comments

@Mike-E-angelo
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

This is based on this thread in the .NET Twitter Community/Group:
https://twitter.com/BuildItBusk/status/1528325252366884865

It appears that when a phone is locked for an extended period of time (10-20 minutes) and unlocked when visiting a Blazor server-side application, the connection is lost and it is not automatically reloaded, resulting in a poor user experience.

The connection appears to reconnect if locked for a few minutes, but for extended periods of time the connection gets lost altogether.

Describe the solution you'd like

When thinking of sites such as Twitter, Facebook, etc, which all use WebSockets, this issue does not occur to them and is accounted for with their own mechanisms. Ideally, this should also be easily addressed/configured with Blazor server-side applications as well. If the connection is lost, there should be the option to:

  1. Ask the user to reload (current/default)
  2. Automatically refresh the browser for the user without prompting
  3. Attempt to re-establish/reconnect/recreate the connection without having the need to refresh the browser at all

Number 3 is the most ideal and should arguably be the default in future versions.

Additional context

Thank you for all your great work out there. I for one cannot underscore enough how much you are changing lives for the better with your efforts. :)

@javiercn
Copy link
Member

@Mike-E-angelo thanks for contacting us.

This scenario is something we would like to cover as part of #30344

I'm going to mark this issue as a dupe, and I would suggest you upvote the referenced issue instead.

@javiercn javiercn added ✔️ Resolution: Duplicate Resolved as a duplicate of another issue feature-blazor-server labels May 23, 2022
@ghost ghost added the Status: Resolved label May 23, 2022
@Mike-E-angelo
Copy link
Author

Great, thank you for the update and efforts out there @javiercn. 👍🙏

@ghost ghost locked as resolved and limited conversation to collaborators Jun 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components feature-blazor-server ✔️ Resolution: Duplicate Resolved as a duplicate of another issue Status: Resolved
Projects
None yet
Development

No branches or pull requests

3 participants