This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(214.4, 5%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJG%3C/text%3E%3C/svg%3E)
We have a Blazor Hybrid application that uses WebRTC for voice calling. The WebRTC calling piece runs as javascript hosted in the BlazorWebView. We are attempting to connect calls when the app is not started/running. We have setup push notifications to notify the user of the incoming call, and the push notification successfully starts the application in the background. However, it looks like the BlazorWebView is not initialized until MainActivity is created, so we can't actually begin the process of connecting the call until the user opens the app and brings it to the foreground. Is there a way to initialize the BlazorWebView explicitly on app startup without requiring that MainActivity be created first?
![](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)
no. the webview is a UI component and is created by the hosting foreground activity. A better design would be to have the hosting app access the telecom sdk, and expose to the Blazor app.
https://developer.android.com/develop/connectivity/telecom/selfManaged
![](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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
By the way, if you want to invoke the native telecom sdk directly in MAUI, you can use Conditional compilation to wrap the native android code.
Thanks for the suggestions. Unfortunately we are tied to the webrtc implementation at the moment, which requires the use of the webview to fully connect the call. My understanding is that I could use the Telecom SDK to display a nice calling UI to the user but I would still need the webview to perform the actual connection/voice/video, etc. Some further reading of the source code looks like MainActivity and the BlazorWebView are pretty tightly coupled, so I think we are going to just have to live with some background calling limitations for now until we can move to a native voice sdk that doesn't require javascript.
Yes, for now, keeping the application alive is a better way to go.
No, the Maui app would expose an api wrapper around the telecom sdk, which your blazor code uses instead of webrtc.
note: this api would only be available to JavaScript, and you would use jsinterop