I have a Roku Channel and it has live as well as non-live content, content is playing well for most of the Roku Devices but on Roku Ultra it's failing.
I am experiencing the following error:
<Component: roAssociativeArray> =
{
code: -6
message: "buffer:loop:unset:DRM exception: processLicense: [sess.lic.rep] KeyAdd failed : 99999(Cdm::kUnexpectedError):extra:etype:buffer"
}
Can anyone help me on this issue?
I looked over the internet for many threads but non was helpful for my case.
I don't know whether this will be helpful to resolve the issue, but I experienced similar kind of issue once. As far as I know DRM libraries are downloaded separately after firmware update on Roku. So, in case you did a factory reset recently and running the side-loaded app now, there may be chances that libraries are not downloaded completely. You can try for manual system software update and see if this resolves the issue. This worked for me. Also, partner success suggested to install one channel having widevine integration and running that channel as one step to resolve the issue, although I didn't need it. You can try this step also along with system software update.
Related
I'm developing a VSCode Extension where you can develop CircuitPython code. I want it to be able to upload your code to your pico, or whatever microcontroller you're using.
For this I need to detect all usb drives that are connected, I've tried libraries like node-usb, usb-detection, etc. But they always give some kind of error, for usb-detection for example you need to rebuild the library with this command:
./node_modules/.bin/electron-rebuild
But then I get greeted with this:
text here: https://pastebin.com/E7bjtWgP
I have absolutely no idea what anything of this means, I've installed vs build tools 2022, 2017 and even added it to my community installation.
After that I tried the usb library. Which again, greets me very kindly with:
I've also tried some other libraries but they all give a similar result. Some do this:
And I've also seen some very questionable things like this:
I've been googling, and debugging now for roughly 4 hours and atm I'm tired so I'll probably try again in a couple of hours.
EDIT:
I've made an entirely new project, moved over all the code and it now works. I have absolutely no idea what the problem was but at least its working now.
i am using B2C provider for DNN and trying to install it as extension and it's throwing error https://i.stack.imgur.com/6faW1.png
i am trying to use multiple version as well but not installed properly and using source from https://github.com/intelequia/dnn.azureadb2cprovider/releases
Please help me out.
There was an issue in the DNN manifest file that has been solved on v1.4.7 (release https://github.com/intelequia/dnn.azureadb2cprovider/releases/tag/v1.4.7). Tracking the issue at https://github.com/intelequia/dnn.azureadb2cprovider/issues/19
I wrote the answer below before seeing this: https://github.com/intelequia/dnn.azureadb2cprovider/issues/19
Perhaps this is pertinent to your question. You might want to check with Ryan Moore (moorecreative" to see if he was able to resolve the issue.
First, please bear in mind that I am not familiar with this particular extension, but it seems as if it is "just another" authentication provide for DNN.
I'm also a little confused. The error message indicates that you've already installed th Intelequia AzureB2C provider. Is that true?
You also say "I am using" and then "trying to install it as an extension." If you are using it, that means that it is already installed as an extension, so a second attempt to install it should throw an error. But, I would think that the installer should see that problem earlier in the process.
Finally, you say "i am trying to use multiple version as well." A provider should be installed only once, and that is what the error message is telling you.
Once you have installed an authentication provider you typically enable it for a portal, and it becomes part of the authentication process.
You should read the documentation carefully, and make sure that you are trying to use the provider as the developer intended.
I am currently developing my first hololens 2 application. In it, I create an interactable with box collider at runtime. In the Unity editor I can grab and move it around, but on Hololens, if I try to grab it, nothing happens. Does anyone have any leads on why this could be?
EDIT: The Example App is installed and Hand Tracking works as intended. The issue seems to not be caused by faulty sensors
Properties (at runtime, after instantiating):
It is recommended to double-check the Unity Project Setting to troubleshoot, please follow this doc to declare the appropriate capabilities. And then you need to configure the XR Plugin. For XR SDK, please follow this link: Getting started with MRTK and XR SDK, for Legacy XR, have a look at For Legacy XR.
After this, please try deploying the scene Assets/MRTK/Examples/Demos/HandTracking/Scenes/HandInteractionExamples.unity to your device. Do you see the same behavior? This will help narrow down if it's an issue with your configuration or an issue with your scene.
Besides, we always recommend the latest Unity LTS (Long Term Support) stream as the best version to develop MR app, and the current recommendation is to use Unity 2019.4: https://unity3d.com/unity/qa/lts-releases
I have issues after last update of BixbyStudio to version 6.10.0-r19i.8185 after submission as public or private:
When using simuator (or device) Im getting an error message: Missing a mock for Installed Apps. Add "appId": "com.samsung.android.bixby.service" and "appVersion": "1" to the apps.json file. For more info: https://bixbydevelopers.com/dev/docs/dev-guide/developers/ide.simulator#mock-installed-apps. When I go to this url there is no any inforation about this apps.json. Do you have information where I can put this file and can read more about it?
I have capsule with audio:
capsule {
id (my.app)
version (0.4.0)
format (3)
targets {
target (bixby-mobile-en-US)
}
capsule-imports {
import (bixby.audioPlayer) {
version (0.3.1)
as (audioPlayer)
}
}
}
which generates from that BixbyStudio for me deprecation warning
import '0.3.1-bixby.audioPlayer' does not declare itself as 'library' and will not be importable in the future, but im using same version from that document https://bixbydevelopers.com/dev/docs/sample-capsules/samples/audio
Please explain what is wrong here
Thanks a lot for your answers!
Support for testing audio library in Simulator is not available yet. However, you should be able to test the same on an actual device.
The next iteration of Simulator is expected to support audio.bixbyPlayer in a couple of weeks from now.
Re: import '0.3.1-bixby.audioPlayer' does not declare itself as 'library' and will not be importable in the future, you can ignore this warning for now.
Using audio player with simulator is a feature not yet available, but on-device testing should work. This new feature will be included in future release. However, I cannot confirm a definitive date.
No mocking in IDE is supported at the moment, this is a feature not yet available. There is NO way to invoke audio player or any other installed apps in simulator.
To confirm the audio player feature is working correctly on device. Please download example.meow and do private submission (you may need to change namespace) on your device. This is a large repository, the example.meow capsule is in subfolder audio. After confirming example.meow is working correctly, you can follow the syntax as an example in your capsule.
Good news! With the new 19I release and version (0.3.2), we finally got rid of the warning. And so is many other library capsules, please update your IDE and use the new version published here.
I'm also seeing this error also and can't find any information about where this file should be placed.
Missing a mock for Installed Apps. Add "appId": "com.samsung.android.bixby.service" and "appVersion": "1" to the apps.json file.
I'm trying to run sample projects (viz. BestSellers and Conference) that are present in MvvmCross v3 branch. I resolved the strong assembly reference issues successfully. However each time I run a sample project, I get System.TypeLoadException in MvxFullBinding and MvxValueConverterRegistryFiller classes.
Exception in MvxFullBinding class:
Exception in MvxValueConverterRegistryFiller class:
Is anybody able to run the sample projects successfully? How do I get around these exceptions?
It looks like you're running this as the 'Touch' projects from Visual Studio? In which case you are way ahead of what I've managed to achieve.
If that is correct, then I suspect that what you are seeing is that you have:
built proper PCLs built in VS/Windows against the portable reference assemblies
but these cannot be executed against the current MonoTouch/Xamarin.iOS runtime.
If you try, you may see issues like: iOS black screen and MissingMethodException: Method not found: 'System.Type.op_Equality'
For some more info see 'almost portable binaries' on http://slodge.blogspot.co.uk/2013/01/almost-portable-binaries.html
There is 'proper' PCL support currently being worked on within XamLabs - so I am hopeful that there may be a solution to this problem arriving in the Xamarin.Android Alpha channel any day now - but don't expect this to be painless initially.
Of course, I might be wrong on this - this really is new territory and I will be fascinated to hear/read about your adventures. If you want to try to find more detail, then it may help to try looking deeper into the exception details, and looking into the console log trace on your mac.
For these two particular exceptions, I can confirm that both samples...
... although that is when I'm working on my Mac.