Setting configuration to Android on Android Studio I can easily debug by running
debug 'android'
Unfortunately setting configuration to desktop and running debug 'desktop' doesn't seams to work. It only display the following message without stopping at the break points
Listening to connection, address 127.0.0.1:55558, transport 'socket'
Can someone help?
It is very easy - everything is describe here in libgdx page:
https://libgdx.badlogicgames.com/documentation/gettingstarted/Running%20and%20Debugging.html#running-desktop-project-in-intellij-android-studio
Short version:
You should run app by DesktopLuncher class
If app crash - check your run configuration your asset folder. It is probably wrong. Set correct folder and everything should work good :).
Related
I see a lot of posts how to debug posts and talks on how debug node application and they mostly points to vs code and other command line tools.
As a fan of IntelliJ and WebStorm IDE, is anything I am missing which can save my day while debugging my Node.js application?
Please see https://blog.jetbrains.com/webstorm/2014/05/guide-to-node-js-development-with-webstorm/ - this post is not new, but still relevant
Jetbrains has a write up of how to debug Node.js applications that is a good starting point:
https://www.jetbrains.com/help/idea/running-and-debugging-node-js.html
The biggest issue that I've run into is that none of the provided solutions automatically restart your application when changes are made. I've worked around this by using their remote debug functionality and attaching to a server running with nodemon. However, I still have to manually restart the remote debug job in IntelliJ as it does not automatically reconnect when the remote debug server restarts.
There is an open YouTrack request to add this functionality, but Jetbrain's recommendation is to instead use their Live Edit functionality.
Live Edit is bundled by default with Webstorm, but has to be installed on IntelliJ Ultimate. I have not tried using Live Edit with a Node.js application, but their documentation says that it should work.
So I have setup my Xbox One as a dev device and actually was able to run my app on my Xbox, but in order to use some new APIs to turn off scaling and what not I had to change my app target version to Build 14332. Unfortunately, after doing this, I am now not able to publish or debug my app to my Xbox and I am not getting very helpful clues as to why not.
I even reverted the target version back to Build 10240 but I am still getting this error:
Severity Code Description Project File Line Suppression State
Error DEP0700 : Registration of the app failed. Deployment Register
operation with target volume C: on Package
MyCompany.MyApp_1.1.19.0_x64__5wbv4ypmprn7c from:
(AppxManifest.xml) failed with error 0x80070002. See
http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app
deployment issues. (0x80073cf9) MyCompany.MyApp
EDIT: I found a work around. Restart my Xbox One. Literally, every time I run my app, I have to restart my Xbox One! :(
I came across the same issue, and while restarting the console didn't help me, I did find another workaround: go to Dev Home and clicked Remove all Visual Studio pairings. I was able to deploy right after doing that.
I've ran into the really similar problem, however with running on the remote machine. The solution was the same as Pedro Pombeiro did on his Xbox One. I opened Windows Settings > Update & Security > For developers and Unpair All. Problem was solved and I could deploy and run the app on remote PC.
My UWP app seems to have trouble waking up when it was prelaunched. The problem is that it's stuck at the ExtendedSplashscreen when prelaunched. I'd like to debug this, but I haven't found any way in Visual Studio to simulate the startup when the app is prelaunched. I've found an option to do the prelaunch itself, but that's not what I want.
Am I stuck with deploying the app in release mode and using logs?
you need to use "Debug installed app package" option, and disable auto launch.
https://msdn.microsoft.com/en-us/library/hh781607.aspx#BKMK_Start_an_installed_app_in_the_debugger
I am developing an iPad application with Xamarin.iOS and MVVMcross. So I have a PCL with my View-Model and my Model, and an iOS project with the view. I use Visual Studio.
Before, I used Xamarin.iOS 6.3.6 beta version, and when I tried to launch the app on the device, an .app file was created and getting it with my Ipad, I could launch the application (impossible to launch directly from Visual Studio).
Yesterday, I uploaded Xamarin.iOS to 6.4.1. On simulator, everything's okay. When I try to launch the application on device, now the app is directly installed but the build stop and the following error appear in the debug output :
Failed to load AOT module '<my PCL>' while running in aot-only mode: doesn't match assembly.
And if I click on my app icon on the device,a black screen appear and disappear immediately.
Does someone know why this error appear?
This looks like something was cached somewhere or not updated correctly.
Here are a few ideas to try:
Delete the app from the device.
Clean & Rebuild your app.
Build & install from Xamarin Studio on your Mac.
Copy the Debug configuration to a new configuration (DebugTest for instance), and run that configuration instead.
I regularly get the same issue here.
The workaround that I use is to switch the platform in the Visual Studio build Configuration Manager to "iPhoneSimulator", run a quick debug session on that, then switch the platform back to "iPhone", and the problem disappears for a while.
Unfortunately I have no intelligent reason as to why this works. It seems to be doing a better job of the "Clean and Rebuild".
After reading a similar bug, I found that clearing the mtbs folder on the OS X host which is located at $HOME/Library/Caches/Xamarin/mtbs/ fixes this problem for me.
I have to do it so frequently I just have a PuTTY session open on my Windows box to clear the folder. I do hope that Xamarin fixes this issue soon.
Make sure Linker Behaviour is set to Don't Link
Clean, rebuild, remove old version from app.
Worked for me at least.
This happened to me after I upgraded to XCode 5/iOS7. I noticed a warning that I hadn't installed XCode Command Line Tools. After I did that I rebuilt the application and it now runs.
I just had this problem and got it to work again by opening the Apple project properties and changing the provisioning profile identity from "Distribution" to "Developer".
My workaround on Mac is to
Close Solution in XS
Quit XS. Command-Q
Reopen it and reopen solution.
After that it usually works again.
I'm trying to open my debugger for an Android project. The emulator opens fine, but the debugger is hanging and thus never fully loads. I keep getting this message, that never goes away:
"Attempting to connect debugger to 'com.example.android.myApp' on port 8616" (The connection never completes).
I am using Linux Ubuntu 10.10.
Thank you all for your help. :)
Matt
set the following flad in your AndroidManifest.xml in the tag application
android:debuggable="true"
Note following Article: Eclipse Android: Could not open Selected VM debug port (8700)
This aswell: Could not open Selected VM debug port (8700)