I was trying to modify the icon in the manifest file.
Then when I tried to debug, I get the error:
The application could not be launched for debugging.
Ensure that the target device screen is unlocked.
What I have to do?
Similar issue is also presented here:
http://blogs.msdn.com/b/wsdevsol/archive/2013/08/17/top-5-commonly-encountered-issues-and-solutions-using-the-windows-phone-8-emulator.aspx
It seems you are not debugging with the emulator (as you suggest). You need to change the target device to one of the emulators.
Related
Hi I'm getting the error
Error creating WebGL context.
Uncaught TypeError: Cannot read property 'getExtension' of null
This is happening on google chrome 71 but I find it odd because if I open up dev tool and refresh the page it works perfectly fine I'm at a loss to what is causing this any idea's ?
It's worked perfectly fine untill today nothing has changed on the PC or browser. My drivers are all up to date, webgl is enabled...
if you have two GPU installed on your system you might want to try to enable
Override software rendering list
in chrome://flags/
I'll leave this here for anyone else apparently it's a browser and graphic card issue
mrdoob: The graphics card is only one of the reasons why the context
can't be created
https://github.com/mrdoob/three.js/issues/4927
This seems to be why unless anyone else has any other ideas...
The issue is on going and not fixed it would be interesting to know why this happens though and why opening dev tools and refreshing resolves the issue for me.
EDIT-
Apparently for me this was due to my graphic card being blacklisted because it's old.
The fix for me was manually enabling WebGL acceleration under Chrome’s feature flags: chrome://flags/
I have encountered this several times with THREE.js. It arises for me once memory resources are shared, abandoned, or overwhelmed, for example:
I have a good render loop but then I introduce long tasks.
I perform extensive, continuous testing. As I modify live settings in Chrome Inspector, THREE does not reflect all changes without fail. Memory may not be released until I restart.
I leave the program running overnight. The next morning the browser is froze, black, OOM...
I use multiple instances of a resource, for example
Web Audio and Magenta Music. The quality may perceptibly degrade and
throw its own errors, but... I will also encounter worse silent
errors. For example when I also steam music in another tab, or click
audio/video media on Twitter... frozen browser, black screen, WebGL
context loss.
I just wanted to comment that I saw this due to other unrelated errors in my app that got thrown first.
I updated my graphic drivers (NVIDIA) and didn't restart chrome nor the PC, and was having this issue.
I just restarted the PC and now it's fine.
This was resolved for me by simply installing the latest and restarting my browser - thought I'd add it here to hopefully save some future soul from wasting an hour like i did.
Error creating webGL Context in three.js.min ver 93
I had the same problem with Chrome version 104.5112.102 and managed to fix it by going to Chrome, Settings, and switching off the
Use hardware acceleration when available.
the graphics card is an old GE Force 8600 card running on Windows 10.
For me, I restarted my computer and the error did not appear again. You can try doing this before you do anything more complicated.
I'm using Sikuli (sikulixapi-1.1.0).
I have 2 monitors. When I use my primary monitor, everything is ok. When I also use the second monitor, it does not work.
I make a screenshot on the second monitor and I wrote this:
Screen s = new Screen(1);
Error
Possible cause in case you did not touch the mouse while script was
running: Mouse actions are blocked generally or by the frontmost
application. You might try to run the SikuliX stuff as admin.
You seem to be having issues with the multimoitor setup.
A similar question was asked on launchpad and can be found here:
https://answers.launchpad.net/sikuli/+question/295379
The basic advice was "Make sure you are using the latest version of 1.1.1 in your java context"
I have looked here, with no avail. Since the answer is not satisfactory, I decided to ask a new one. I have created a new device type by looking at the code for other virtio devices, primarily balloon, rng and crypto.
But I'm facing a problem that I'm not sure how to resolve. I get an error saying 'virtio-bus' bus not found for device 'my-virtio-device'. And I do not know what to do about it since I have not explicitly defined a bus for my device. Virtio does it for me.
Once I'm through with this, I intend to write about it in stackoverflow documentation. I seem to find nothing on creating new virtio devices in qemu anywhere!
Well the problem seems to be that virtio-bus is an abstract bus. So we cannot use the device directly. I had to extend VirtIOPCIDevice and define my device. VirtIOPCIDevice is attached to virtio-pci-bus. This works and my device now shows up in the guest with the lspci command.
I hope the short version helps. Of course, as promised in the question, I intend to write all about how I created a new virtio device in QEMU once I've finished my project.
I am making a Windows Phone 8.1(winrt flavor) application and stuck in problem about PushNotification.
await PushNotificationChannelManager.CreatePushNotificationChannelForApplicationAsync();
This function returns PushNotificationChannel and it usually works well. But in some our devices, this function throws 0x880403E9 error.
MSDN says,
0x880403E9 The notification platform is in the process of reconnecting back to the WNS cloud due to a earlier network connectivity change. Apps should retry the channel request later using an exponential back-off strategy.
I think retrying the request can never solve this problem. The function always throws the exception. During a month. We even implemented exponential retrying strategy.
The worse fact is, the our broken devices worked well with the function before. But once it has been broken(?) by mysterious reason, it is never fixed itself. -First time we've got this problem, we did factory-reset the device and the problem fixed. But in other devices, reset was not a solution.
Somebody says updating lastest version might solve this problem, but it is not. Even in Windows Phone 8.1 Update 1(8.10.14157.200), the problem still occurs.
Is there anyone know about this problem?
Microsoft answered this question via email.
The problem happened when,
you don't have USIM card or
exhausted your data or
3G/LTE network does'nt work by some problems
Even if you are connected to network with wifi, the problem still occurs. I think Windows Phone 8.1 is always trying to process the push notification by 3G/LTE network if you turn 3G/LTE data network on.
If you can't use 3G/LTE network by given reasons, try to turn off data connection at system settings. Then push notification will be proceed via wifi network.
And they said, this is not going to be fixed even in Windows Phone 8.1 GDR2. Could be with Windows 10.
I had this problem as well and the answer above fixed it.
Just want to add that there might be a problem with roaming as well. I´m working in another country then my own and I got this problem. So if the three points above is ok, check that you are not using data roaming.
This is how you do it on Windows Phone 7 http://blog.jerrynixon.com/2011/11/mango-sample-lock-and-run.html is it possible in Windows 8?
This sample is showing you how to implement the functionality so your app will still "run" when the device is locked. It only seems to work with a kind of "background tasks" which makes it not exactly the same as it is for Windows Phone.
http://code.msdn.microsoft.com/windowsapps/Lock-screen-apps-sample-9843dc3a
Please note that an app that can run when the device is locked should have at least one of the following background tasks:
Control Channel
Timer
Push Notification
Here is some more info on the lockscreen: http://msdn.microsoft.com/library/windows/apps/Hh779720
UPDATE:
As far as I have found there is no exact behaviour like in Windows phone to run your app under the lockscreen. There are a few recent posts on the MSDN blogs which explain the background model http://blogs.msdn.com/b/windowsappdev/archive/2012/05/16/being-productive-when-your-app-is-offscreen.aspx?wa=wsignin1.0
Sorry to see that at this moment there is no way to make it work under the lockscreen