Dependency: 'omni.services.streamclient.webrtc' = { version='^' } can't be satisfied

As per the title - would like to add webrtc to my kit app. But somehow it can’t find it?

Also it would be good to know why my installed Omniverse USD Composer can find it but when I build a kit app it can’t. What is the difference?

A log excerpt:

2024-10-01 16:43:58 [1,183ms] [Warning] [omni.ext.plugin] [ext: camera] Extensions config 'extension.toml' doesn't exist 'd:/ov/exts/camera' or 'd:/ov/exts/camera/config'
[1.803s] [ext: omni.kit.async_engine-0.0.1] startup
[1.843s] [ext: omni.client-1.2.0] startup
[2.134s] [ext: omni.kit.registry.nucleus-0.0.0] startup
2024-10-01 16:44:02 [5,108ms] [Error] [omni.ext.plugin] Failed to resolve extension dependencies. Failure hints:
        [msft.sphereflake22-1.0.0] dependency: 'omni.services.streamclient.webrtc' = { version='^' } can't be satisfied. Available versions:
         (none found)
 Synced registries:
         - kit/default         : found 596 packages
         - kit/sdk             : found 329 packages
         - kit/community       : found 382 packages
         - kit/prod/sdk        : found 329 packages

I am assuming you are referring to building your kit app using the Kit App Template (KAT) correct ?

Yes, that is correct. I notice that thing is “heavily under construction” these days so might be related to that.

Actually we do not need that webrtc extension any more in the new 106 Kit App. We can now stream “natively” for all apps in the KAT. Just follow this help file on GitHub to learn how to add streaming to your kit app.
kit-app-template/templates/apps/usd_composer at main · NVIDIA-Omniverse/kit-app-template · GitHub

Interesting - and I will look into that. Still puzzling why I can add that extension to USD Composer, but not to my kit app though. Inconsistencies like that make OV somewhat mysterious to me still.

No mystery. Webrtc was published for kit 105, but not kit 106. So it will work for the old composer, but not for the new.

Looking at the documentation for Web RTC Browser Client - I don’t see any indication that this is depreciated for kit 106. I guess we don’t need anything from that link anymore?

But I also see a some information that I would need for kit 106, like which ports to open for a cloud provider, etc. Where is this information for kit 106?

I actually need to know the ports now. I suppose another question is in order.

Did you follow that web link for the native streaming ? That is how we are doing it now.