This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I tested the SignalR solution in Xamarin Forms and .net core backend and it works great:
https://montemagno.com/real-time-communication-for-mobile-with-signalr/
However, I am wondering how to keep receiving the messages when the app is in background mode, as this solution (in the link) only works when you have the app open on the chat page....
Do I need to implement my own push notifications? If that is the case it defeats the purpose of SignalR so I hope there is another way that I haven't found yet :)
Thanks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 76%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
In iOS it is not possible to keep the signalr connection alive while in the background. From what I've read (never tried it) if you use continuous tracking in the app, iOS will allow signalr to stay alive so it can send tracking data to the backend server.
With Android you can create a foreground service. This will allow signalr to stay alive in the background. So it's only iOS you will have a problem with in the background.
You will need to handle signalr hub connections in OnSleep and OnResume. Depending on how you handle the connection, when your clients come out of the background, they may create a new connection, it could time out, or it could deliver all the backlogged messages to the client at one time.
There is a solution to address this problem:
Since signalR disconnects when the app goes to the background and some time passes. The OnResume and OnSleep events are where you have to do all the magic. When it goes to OnSleep it disconnects SignalR and when you return to OnResume you reconnect it and check the new messages.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 10%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMC%3C/text%3E%3C/svg%3E)
Hi Stesvis-5434,
in fact it is possible to receive messages in background mode, all you need is whether a Background Worker for UWP apps :
https://learn.microsoft.com/en-us/dotnet/api/system.componentmodel.backgroundworker?view=net-5.0
or another example is Service Workers in PWA :
https://learn.microsoft.com/en-us/microsoft-edge/progressive-web-apps-chromium/serviceworker
it depend more on the platform you are using, for example here is an article about creating an Android service using xamarin:
https://learn.microsoft.com/en-us/xamarin/android/app-fundamentals/services/creating-a-service/
Hope it helps!
Best Regards.
Thanks for your reply!
This is for iOS and Android.
The problem is that, i think that in iOS you can't run background services anymore?
Okey, I see it is more related to the iOS platform features, but for sure there is a way to deal with this constraint for example I saw in the documentation a topic about backgrounding:
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Signal/r will not work when the mobile app is not active. The server can log messages, and the mobile app can ask for a replay of messages it missed when it becomes active. as mobile internet connections are flaky, you will need this feature even when active.
If you want mobile o/s to notify the user when there is activity, then you want use the mobile o/s notification services.
note: even with a PWA most browsers will shutdown the websocket connection if the PWA is not the active tab.