Using MonoDevelop, MonoDroid on a Mac 4.0.6
I am attempting running the sample project SearchableDictionary. When I press Debug, the "Select a Device" dialog appears to choose the emulator. Even though the emulator is running, it is not recognized. Each time we run the debug, it tries to run a new instance of the emulator and never installs the app there.
Is there a way to get MonoDroid to attach to a running Emulator, one that it created in the install process?
To get the Android debugging bridge to refresh in general - not just for MonoDroid - try opening a command line (shell) and using:
adb kill-server
adb start-server
This is often required (in my experience)!
See: http://developer.android.com/guide/developing/tools/adb.html for more adb info (Android Debug Bridge)
Related
I'm facing up a strange problem in Puppeteer with authentication.
I've written a script to take some screenshot of a website which required authentication.
In my local computer (windows), when running in command line as node.exe my_script.js; it's working fine (in headless moden which is the default mode).
I've written an upper Java program to manipulate it (dynamically set the path, the node modules path, run the process "nodex.exe my_script.js" every 30minutes, manage timeout of the process,...). It's still working directly running from Eclipse, in headless mode.
Then... I've built/packaged a JAR and running it in a cmd window: java -jar my_jar.jar... and then the script can't authentitcated on the website in headless mode (the answser page just write a message like "you need to be authenticated", which is managed by the http server).
To check what happen, I've just add an option in my nodejs script (so I do not modify my java upper program code) to run chrome in non headless mode; with option headless : false. And... it's working!
I let the option to run in non headless mode, and I create a Windows service to run my jar via a bat file, with the help of nssm... Just to test. I'm really happy to see that all is running fine without seeing any chrome GUI (maybe Windows disable GUI for service, don't know how).
Have I maybe missed something? Or is there a bug in Puppeteer or Chrome to manage authentication in headless mode?
Regards
Alex
Here's the details:
Created a blank Universal Windows App in Visual Studio 2015
Set to ARM, Debug
Attempt to deploy to a Lumia 925 Running Windows 10.0.10166.0
Phone is in 'Developer Mode'
I unlocked the phone using the Windows Phone Developer Registration (8.1) tool. Do I need one for Win10?
I first get the following error:
Error : DEP3321 : To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.10240.0 or higher. You currently are running version 10.0.10166.0. Please update your OS, or change your deployment target to a device with the appropriate version.
Now I found a solution for this first error here so I changed the following in the App1.csproj file:
<TargetPlatformMinVersion>10.0.10240.0</TargetPlatformMinVersion>
to
<TargetPlatformMinVersion>10.0.10166.0</TargetPlatformMinVersion>
Now I get the following error when I try and deploy the app to the phone and I can't find a solution:
Error : DEP0001 : Unexpected Error: Element not found. (Exception from HRESULT: 0x80070490)
Anyone have any idea how to resolve this? I can deploy the app fine to the emulator, just not to my physical phone running Windows 10.
For me I had to turn on the Windows Phone ip over USB Transport
go to run -> services.msc -> [look for it].
If any of these answer not solved your problems, here is what I've done:
Reset the phone (it's dev phone, so it's okay to reset, not losing any data)
DO NOT choose recovery. Start clean
After all waiting (installing app, get settings set), plug it in and try to deploy again.
And it's just worked
The idea come from: https://social.msdn.microsoft.com/Forums/en-US/d2340565-a80a-4f1c-8a0c-ba8ad5ce34b1/cannt-deploy-wp-81-app-to-phone-using-vs-2013-error-dep0001-unexpected-error-element-not?forum=wptools
What worked for me was resetting the phone to factory defaults ( and erasing all data... a true reset). The phone came with 8.1, when I reset it however, it was reset to windows 10 base. I re-enabled developer mode on the phone and I can deploy my apps to the phone now.
I had tried all the other suggestions with no luck.
The error is telling you that the version on your phone is older than what the tools support and that you'll need to upgrade it. Can you try checking for updates on the phone and bringing it up to 10.0.10240.0? There are likely breaking changes between 10166 and 10240 that prevent the VS RTM tools from working with older versions.
Update: we have announced a newer build of Win10 mobile, which will work with the win10 tools. More information is available here:
http://blogs.windows.com/bloggingwindows/2015/08/12/announcing-windows-10-mobile-insider-preview-build10512/
Apparently 10.0.10166.0 is a pre-release Mobile Insider Preview Build.
You just need to decrease Target Min version to 10166.
Unfortunately, you can't do this from Project settings.
Bu you can do it manually.
Follow these steps (Worked in my case with Nokia Lumia 520 Windows 10 Mobile Insider build 10.0.10166.0):
Right click on your project in Visual Studio.
Select "Unload Project", it will now appears as ProjectName
(unavailable).
Right click on the unloaded project and select "Edit
ProjectName.csproj"
Locate the <TargetPlatformVersion> and <TargetPlatformMinVersion>
items in the first <PropertyGroup>.
Change the <TargetPlatformMinVersion> value to 10.0.10166.0.
Now Save and Close the file.
Right click on the project again and select "Reload Project"
Rebuild the project and deploy to device.
When I tried to deploy my app in Release mode to Windows Phone 10 I got the following error:
Error : DEP0001 : Unexpected Error: Element not found. (Exception from HRESULT: 0x80070490)
I tried a few things but what ended up working was quite simple: I built and ran the Debug mode of my app. Then without uninstalling the app I switched the configuration to Release and built and ran it on the phone and then it worked!
Whoever ends here because they are getting
Error : DEP0001 : Unexpected Error: Element not found. (Exception from HRESULT: 0x80070490)
after trying to deploy a UWP app (but deploying on emulators work) and the Windows Phone ip over USB Transport service is started, first and foremost try reseting the phone to fabric settings. It worked for me and some others in this thread, so my advice is to start with this before spending lots of hours chasing ghosts.
I tried it with Visual Studio 2015 Update 2.
After installing the Multi-Device Hybrid Apps (Preview) for Visual Studio CTP2 Extension in Visual Studio 2013 on Windows 7 x64, I am unable to launch a new Multi-Device Hybrid App in Ripple.
Details:
When Installing the Extension I chose not to install Chrome as it was already installed
Opening the solution displays an error message We've detected issues with your system's environment configuration along with Google Chrome - The software is missing from your system. You may have to configure it after installation. A link to the instructions is provided.
On the instruction page the link for chrome is simply to the chrome install page
Chrome is already installed in C:\Users\username\AppData\Local\Google\Chrome\Application\chrome.exe
Attempting to launch the application with the Ripple - Nexus (Galaxy) setting causes the error Chrome must be installed in order to launch the app in Ripple
I am able to launch the app on both the Android emulator and an Android device
What changes do I need to make to my configuration for the project to launch Chrome?
You are seeing this issue because it is currently hard-coded to look for Chrome in
%PROGRAMFILES%\Google\Chrome\Application\chrome.exe
but you have it installed in your Users folder.
To workaround this, please re-install Chrome to your %Program Files% folder.
I have built a simple NaCl application. For running the application I use technique 2 described in Nacl Developer's guide, which means that instead of running a local server I load my application as unpacked extension to chrome. The application runs fine so far.
Now I want to experiment with nacl-gdb and attach my application to it at startup.
In the NaCl Developer's guide there are only instructions on how to attach nacl-gdb on an application that is run with local server(technique 1). I made a search to the internet and I ended up with the following approach in order to attach nacl-gdb for an application that is being ran with technique 2:
I enabled "Native Client GDB-based debugging" flag of Chrome.
I started chrome from a terminal like this: ./chrome "--nacl-gdb=gnome-terminal --
/media/sdb1/leonidasbo/AncientRoot/nacl_sdk/pepper_27/toolchain/linux_x86_glibc/bin/x86_64-nacl-gdb"
When Chrome launched, I navigated to my application.
With this approach, Chrome automatically started nacl-gdb when I opened my application.
However nacl-gdb tried to attach but with no success. The output was the following:
*This GDB was configured as "--host=x86_64-unknown-linux-gnu --target=x86_64-nacl".
Reading symbols from /opt/google/chrome/nacl_irt_x86_64.nexe...(no debugging symbols found)...done.
Don't know how to attach. Try "help target".
(gdb)*
It seems that gdb cannot attach to my application. I tried executing "target exec /path/to/my.nexe", but nothing changed.
Am I missing something here? Is there any other way to debug applications loaded as unpacked extensions with nacl-gdb?
My OS is Ubuntu 12.04 and I am using pepper_27 of nacl_sdk. Chrome version is 27.0.1453.93.
Thanks
I assume you were using this guide, which I was using earlier as well. It is out of date. These are the real instructions. It seems that the way you attach the debugger has completely changed, and it is no longer possible to use --nacl-gdb (that is planned for removal). You must manually attach the debugger by following these steps.
The full guide is here, but I'll summarize:
Launch Chrome with chrome --enable-nacl --enable-nacl-debug --no-sandbox --disable-hang-monitor.
Run <NACL_SDK_ROOT>/toolchain/win_x86_newlib/bin/x86_64-nacl-gdb (with no arguments).
Enter these commands into the gdb prompt:
(gdb) nacl-manifest <path-to-your-.nmf-file>
(gdb) nacl-irt <CHROME-DIR>/nacl_irt_x86_64.nexe
(gdb) target remote localhost:4014
Now you can use gdb as normal. (If you just want to run the application until it crashes, start by typing continue.)
Is it normal not to have the Google Chrome browser on a google TV emulator in a Linux machine with KVM enabled?
When launching an Intent from my application that hits a web page,
I get the error message "No activity found to handle intent {act=android.intent.action.VIEW, dat=http://...}" and I have tried several web addresses.
The code from My Activity is this and it works fine in other android platforms:
Intent myIntent= new Intent(Intent.ACTION_VIEW,
Uri.parse( "http://www.test.com");
startActivity(myIntent);
Am I missing some step to install the Google Chrome browser? On the other hand I can not find the Google Market application neither.
Sadly it is normal not to have the Chrome browser installed with the emulator. This does make it a bit of a pain to do things like you are trying currently. I'm not sure if there are plans for adding Chrome to the emulator in the future, but in the meantime, it is possible to install Browser.apk (the Android browser) to the emulator (via adb install Browser.apk, which you can either build from AOSP or possibly pull from a device or standard Android emulator via adb pull /system/app/Browser.apk - I think this is the default Browser location on devices).
Once Browser.apk is installed you should be able to test these things as you would expect.
So the steps are:
Start an emulator with Android 3.1 running
adb -s device_id pull /system/app/Browser.apk
adb -s device_id install Browser.apk
In the Android smart TV emulator, I've tried the simplest method to download the Chrome browser.
Drag and drop the APK onto the emulator after downloading it from the provided link. After you will allow from to Settings > Device Preferences > Security & Restrictions > Unknown sources
Chrome APK Download URL
Second
Alternate you can follow the article link