I am not able to play the video in pip mode. I am using Cefsharp version 71. Do I need to enable any flag for supporting pip mode in Cefsharp? Video is not getting displayed in pip mode but audio is getting played.
However, in normal mode video is working fine.
Related
I'm at the bottom of the J curve as far as Android development goes, but I can't even get the demo app to work on my Android TV. I build the TV device blank activity in Android Studio, and it works fine in an emulator. I have a banner(320x180pixels), android.hardware.touchscreen(false), android.software.leanback(true), and LEANBACK_LAUNCHER in the intent.
The APK (which I have signed with V2 and marked as a release) installs with warnings from playprotect (which I can't shut off in this locked-down TV) but cannot be opened. I have sideloaded other APK's via the same method. I have also tried not signing the APK.
The TV is an Axis 1832S running Android 7.1.1. I CAN put it into developer mode if that helps.
Does anyone have any hints, or a simple 'hello world' apk that works that I can try?
I'm trying to port my iOS app to Mac using macCatalyst, and I'm having problem with Siri Shortcuts. The code complies and runs, but when I try to add shortcut using INUIAddVoiceShortcutViewController I'm seeing 'Shortcuts unavailable.'
Using
INVoiceShortcutCenter.shared.getAllVoiceShortcuts returns error [Intents] -[INVoiceShortcutCenter getAllVoiceShortcutsWithCompletion:]_block_invoke Error from -getVoiceShortcutsWithCompletion: Error Domain=NSCocoaErrorDomain Code=4099 "Couldn’t communicate with a helper application."
Any ideas what's I'm doing wrong? Same code works perfectly fine on iOS.
The Intents framework is unavailable at runtime on macOS except for WidgetKit support. The APIs are available at compile time in the Mac Catalyst environment to reduce the amount of changes required to compile for Mac Catalyst. Calling into the APIs as part of the shared code path between iOS and Mac Catalyst is fine, they will just return an error for Mac Catalyst, as you're seeing.
Posted 11 hours ago by edford
I am trying to create enterprise build for apple watch project by xcode 6.3
I tried to build by archive and by auto-build (shenzhen tool)
When I run it at iPhone, it crashes immediately but with ad-hoc build it's work fine.
I've found that Xcode Automatic selections do not work properly for code signing and provisioning profile when used with Apple Watch; sometimes it makes the wrong choice and you only notice when it has problems installing and launching.
For each of the App, App Extension, and Watch App, select the code signing certificate and provisioning profile explicitly (not automatic) in the pop up list.
For issues upon launch on the device (from spring board) the device console gives good information. Install iOS Console, from lemonjar.com to easily see such information.
I'm trying to use the latest Google NaCl SDK. Following the instructions at https://developers.google.com/native-client/pepper18/devguide/tutorial
I downloaded the naclsdk tool from their site, ran update, and got a pepper_18 folder.
I set NACL_SDK_ROOT to the pepper_18 folder, went in to 'examples' and ran make. Everything seemed to compile just fine.
I started Chrome, looked in about: flags and about: plugins, and verified that NaCl is enabled. I installed the SDK Examples app (from: https://developers.google.com/native-client/pepper18/sdk/examples) and that works just fine.
Then I tried to run my locally built and hosted examples, going to http://localhost: 5301. The HTML loads fine but the NaCl content does not load. In the hello world examples, it says "Status: LOADING..." forever.
I double checked the HTTP server logs and I don't see any errors there. Is there another place I should be looking for logged errors?
Check for version mismatch
In Chrome navigate to about:version and check that the major version of Chrome is at least that of the Pepper version you used to build your examples.
Check the JavaScript console in Chrome for any errors
You can find it by clicking the wrench icon in the upper right-hand corner in Chrome and selecting Tools -> JavaScript Console.
Inspect the NaCl module for further information
In the JavaScript console, you can also inspect the embed element of the NaCl module. E.g., if the embed tag has id="nacl_module" you can inspect it by typing
theModule = document.getElementById('nacl_module');
theModule.lastError;
Check Chrome's output to stdout/stderr
On Mac or Linux start Chrome from the terminal and look at the output on the console. E.g., on the Mac, you'd typically go
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --enable-nacl
On Windows, Chrome does not write to the terminal if started from a command prompt. For this reason you need to redirect stdout/stderr from Chrome by setting the environment variables NACLLOG, NACL_EXE_STDOUT, and NACL_EXE_STDERR. Point them to different files, e.g.,
NACLLOG = c:\my_project\nacl.log
NACL_EXE_STDOUT = c:\my_project\nacl_stdout.log
NACL_EXE_STDERR = c:\my_project\nacl_stderr.log
Then (re-)start Chrome (making sure these environment variables are in effect).
Connect a debugger
Instructions on using the debugging support (currently only 64-bit Windows and 64-bit Linux) are available at https://developers.google.com/native-client/pepper18/beta-docs/debugging.
Restarting Chrome means closing all windows
When developing for Native Client one often restarts Chrome. It is important to close all Chrome windows; otherwise it hasn't actually restarted.
I muddled through a few issues which I will document in case they help others:
Neglected to 'make' the examples (got a clue to make them from the asker's description).
Chrome would not let me run non-store chrome apps. Went to chrome://flags and enabled Native Client and Native Client GDB-based debugging.
The JavaScript console said the demo's nmf file under .../debug/ was missing. I changed the make config to build Debug instead of Release based on this.
Chrome console complained NativeClient: NaCl module load failed: ServiceRuntime: failed to start; NaCl's GDB debug stub requires --no-sandbox flag on Windows. See crbug…. Tried running Chrome from cmd with --no-sandbox. This results in an alert You are using an unsupported command-line flag: --nosandbox. Stability and security will suffer. The aforementioned error went away, but the examples still would not run - no UI.
Went back to chrome://flags and disabled Native Client GDB-based debugging.
Then most of the examples worked. The Google Drive demo complains Error: must be run as a packged app.
have you confirmed that you've run httpd.py from the examples folder? This script creates the localhost:5103 server that the apps can be ran from.
Also, what OS are you using?
~Main
I just finished my installation of Adobe Flash Builder 4. I've definitely installed the most recent flash player from Adobe's website onto my computer. Also, in the run configurations of flash builder 4, I changed the source path from the .html file to the .swf file that is generated. I don't need to test it in a web browser, I just want to run the swf in flash player.
I only have 1 .as file in my actionscript project and there is no code written in it other than the package, class and main function statements. When I run the .html file, it runs fine, and debugs fine. However, when I switch the source path to the .swf file, it runs fine but doesn't debug!
When I debug it, the progress gets stuck at 57% and it says "Waiting for Adobe Flash Player to connect to debugger..." in the "Progress" tab. After a few minutes a window pops up that says:
"Failed to connect. The session has timed out. Ensure that you have run the application with debugging on and that I have the debugger version of flash player."
What can I do to fix this? I am on an intel Mac running OS 10.6.5.
Thanks
You say you installed the most recent Flash Player, but you don't say if you by that mean the debug player. The "Flash Player 10.1 Plugin content debugger" and "Flash Player 10.1 Projector content debugger" can be downloader at http://www.adobe.com/support/flashplayer/downloads.html
This might solve your problem
http://blog.air4android.com/?p=59
HTH
I had exactly that symptom.
I cleaned all related projects, removed bin-debug and bin-release, cleaned the cache, reinstalled the debug version of the player. It didn't help. I was about to reinstall FlashBuilder.
Then I displayed the javascript console. I saw there is a syntax error in my index.template. As a result, the application was never started, so the screen remained blank and the debugger failed to connect.
I fixed the silly error and it worked again! Basically, that message tells you the application failed to start.
Make sure you're not using Chrome. At time of writing Flash Player debugger does not work in Chrome.
I had this problem and simply switched the web browser to Safari in Flash Builder preferences.
what worked for me finally was copying the swfobject.js to the bin-debug folder. I don't know why it wasn't there, but that fixed the problem.
you do, of course, have to run a flash debugger version in your browser.