Error on chromecast receiver app PLAYBACK/104 - html

I have an html5 receiver app that I'm writing for a client who already has a sender app. On playing a video for a second time, I get this error:
[cast.player.api.Player] error
[cast.player.api.Host] error: cast.player.api.ErrorCode.PLAYBACK/104
I can't tell if this error is coming from my implementation of the media library or from the sender app. Any guidance?

You can see in the Media Player Library Error Codes that this error means "The media element fired MediaError.MEDIA_ERR_SRC_NOT_SUPPORTED error." The suggested solution from the docs is to Validate developer data segment, ensure the codecs are included in Cast supported formats. You can read more about the cast.player.api here.

Related

Cordova/Chromecast: "For some reason, not attempting to join route"

I have a simple Cordova app with a video HTML5 element. I try to cast this video to a Chromecast. It won't display the Chromecast icon as default (if Chromecast is available) so I using a plugin.
I'm using the "cordova-plugin-chromecast". By calling chrome.cast.initialize, the next error will be logged:
"For some reason, not attempting to join route Chromecast, null, false".
And I cannot call a session.
Chromecast is connected, confirmed by the Google Home app on the device.
Why this log error?
If you're integrating Chromecast/Google Cast into Cordova, this plugin is the most suggested one - cordova-plugin-connectsdk. Check this related SO post for more details.

Attempt to postMessage on disconnected port

I was following this guide on native messaging, but now I've come to a stand-still. The developer console on Firefox keeps giving me the same error:
"Attempt to postMessage on disconnected port" along with "Webconsole context has changed" before it.
I've checked the registries, the ping_pong registry key is in the correct place,
HKEY_LOCAL_MACHINE\\SOFTWARE\\Mozilla\\NativeMessagingHosts\\ping_pong,
and it's value is pointing to the location of my manifest.json file.
My extension id and "allowed_extensions" match.
I found this, and it did stop at the end saying I don't have a python script in the batch file, but that shouldn't be the cause of my error messages.
I have Firefox Quantum 61.0.2, if that's of any use.
What am I doing wrong?
This is a generic error and it means the native messaging host configuration is wrong. The specific error is logged in the Browser Console (Firefox Menu --> Web Developer --> Browser Console) and it is much more helpful.
(For me, the specific error was a typo in the native messaging manifest.)
(Discussed in: https://github.com/mdn/webextensions-examples/issues/266)

JS error on Chrome (with Device Toolbar enable)

When I turn on the tablet mode or the phone mode in Chrome, I get a javascript error :
Uncaught TypeError: Failed to execute 'elementFromPoint' on 'Document': The provided double value is non-finite.
at HTMLHtmlElement.avp.disableTouchSafari (viewer3D.min.js:18)
I've just update Chrome to the last version.
Any idea?
This might an issue of Forge Viewer. Apologizing for any inconvenience caused.
I have logged a request LMV-3401 [Autodesk.Viewing.Private.disableTouchSafari() reports error while viewing model with Chrome DevTools' Device Mode in macOS] to our development team to allocate time to investigate. As it requires further exploration and possibly a modification to our Viewer, please make a note of this number for future reference.
You are welcome to request an update on the status of this request or to provide additional information on it at any time quoting this request number via forge.help#autodesk.com.
However, I think this error didn't affect main features of Viewer. At the meanwhile, I think a real mobile device will help you in this case since this error didn't show up while testing on my Ipad.
Cheers,

Error uploading app to Windows Store with WindowsPhoneReservedAppInfo.xml file

We have referred to this MSDN article for help on locking down the hardware buttons on our device.
The article is pretty straightforward and I managed to generate a prov.xml file with the help of our manufacture however when we try and upload our app to the Windows Store we get the following error:
Package acceptance validation error: File WindowsPhoneReservedAppInfo.xml is invalid: The 'Id' attribute is invalid - The value 'ID_CAP_ENTERPRISE_SHARED_DATA' is invalid according to its datatype 'http://schemas.microsoft.com/phone/2013/windowsphonereservedappinfo:ST_SoftwareCapability' - The Enumeration constraint failed.
I would have thought we would be required to include the WindowsPhoneReservedAppInfo.xml as described in the article above so that when we download the app we can lockdown the hardware buttons.
It's worth noting that if you don't have this file and attempt to lockdown you get the following error:
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
For anyone interested in the code that does the lockdown here it is (although the code works I just thought I would try and give a bit of context):
Dim _GUID As Guid = Windows.Embedded.DeviceLockdown.DeviceLockdownProfile.GetCurrentLockdownProfile()
If Windows.Embedded.DeviceLockdown.DeviceLockdownProfile.GetLockdownProfileInformation(_GUID).Name <> "Associate" Then
For Each G As Guid In Windows.Embedded.DeviceLockdown.DeviceLockdownProfile.GetSupportedLockdownProfiles()
If (Windows.Embedded.DeviceLockdown.DeviceLockdownProfile.GetLockdownProfileInformation(G).Name.Equals("Associate", StringComparison.CurrentCultureIgnoreCase)) Then
Await Windows.Embedded.DeviceLockdown.DeviceLockdownProfile.ApplyLockdownProfileAsync(G)
End If
Next
End If
Catch ex As Exception
End Try
We use the role Associate in the prov.xml file. The prov.xml file does lockdown the device as we want it too and that only works if we have the WindowsPhoneReservedAppInfo.xml file as described in the MSDN article so I can't understand why we can't upload to the Windows Store.
Does anyone have any ideas on how I should be uploading our app to the Windows Store?
I've spoken with our manufacturer and they have said this:
I have a strong feeling this cannot be used in a store app due to Microsoft rules…. So it looks like you can only use this in an Enterprise signed application (Which you then side load onto the device or download using a MDM).
That being the case I will have to look into MDM.

Validation error code 2011 wp8 while submitting app to the store

My app validation failed due to error 2011 (Windows Phone 8 App).
I got the following error for a no. of times:
2011: The background agent can’t use Microsoft.Phone.Controls.PhoneApplicationFrame::RemoveBackEntry, which assembly MyApp.dll is trying to use. Update your file and then try again.
Can anybody tell as to how to get rid of this error and pass the validation?
Thanx in advance.
You can't use some API in Background Agents - MSDN. And one which you cannot use is:
System.Windows.Navigation -> All APIs in this namespace are unsupported.
And as you can see PhoneApplicationFrame.RemoveBackEntry returns System.Windows.Navigation.JournalEntry.