trying to debug iOS Kony projects using Kony studio, have created a new cofiguration according to the tutorial from Kony bootcamp, I am not able to run the project in debug mode, I am getting the below error messages. Attached is the screen shots for reference.
error message :- Failed to get tabs for debugging connection refused
Thanks
Do the below,
first build the project.
Then open the iOS emulator from the studio, by double click on iPhone, this will fire up the xCode project ( make sure xcode is installed )
Run the project from xCode by choosing debug option from the drop down in xCode, using any simulator like iPhone, this will launch the app in the simulator with alert showing to enter the debugger host port. ( i gave the port as 9222 )
click on start and then you will see message as waiting for Kony studio to connect.
Now go back to your Kony studio and right click on the project and debug as iOS application, ( make sure you have configure a configuration in studio and ip address and port matches the same with iOS simulator details ) doing this will launch in debug mode and you will be able to add break points wherever required.
Related
I was using android studio to build an app but know I am unable to close the application. It's just stuck as a permanent screen, whenever I try to delete it, it says the application is still running.
In Visual Studio when I want to run my project, my only choice now is the Android_Accelerated_X86_Oreo emulator. I would like to deploy to my cell phone. I have been able to do that but suddenly I cannot. I have Dev Options enabled and the USB connection is in File Transfer mode. What am I doing wrong?
I have updated Visual Studio to 15.8.4. I code on a PC machine and have a MAC connected via SSH for builds and debuging via the simulator.
Before the simulator would just start up on my MAC. Now a new window comes up on a PC called iOS Simulator which says
Checking server...
Connected...
Checking server... and so on again and again
The connection is established to the MAC and the MAC agent starts successfully. I am even able to deploy the application to the device but when I want to use the simulator this bug occurs.
Has anyone come across this issue? Thanks.
Well,
on the windows machine you must go to Tools -> Options -> Xamarin -> IOs settings and disable simulation on a windows machine. For some reason after the VS update this option enabled itself.
I'm working on Xamarin Forms application in Visual studio 2017 .I wanted to deploy application to android simulator .I try to deploy it debug mode.
i set android project as the startup project
When i deploying i get this warning
No Address and User has been specified in order to establish a connection to a Mac Server, so only the main assembly was compiled for project CMI.IOSApp. Connect to a Mac Server and try again to build the full application.
Go to VS menu Build->Configuration Manager is iOS project tick when you have set your android project as start up project.
So the Build and Deploy checkbox for iOS project should be untick when you are going for Android build.
Whenever I try to debug my UWP projects with the a one of the Windows 10 Phone emulators I get the following error after the emulator opens to the home screen:
DEP6100; The following unexpected error occurred during bootstrapping stage 'Connecting to the device '90F4E8F4-EC5F-4B64-B2E8-6EDE6F813BD3'.': SEHException component has thrown an exception.
The app never starts. I have not entered any code. I simply create a UWP app and then try to debug it with the Windows 10 Phone emulator.
I have already uninstalled and reinstalled VS 2015. I even did a windows 10 repair.
I get this the first time I debug an application. The trick I found is to do the following (precisely)
Make sure that your configuration settings are set to build and debug correctly (yes you need to check this UWP doesn't ship with it correctly configured)
Make sure the emulator is closed
Press the play button in visual studio
As soon as the emulator appears within visual studio, click on the build menu and hit cancel. This will stop deployment but the emulator will continue to boot.
Once the emulator has booted completely and you're able to navigate the OS, you're good to go. You can now run and debug your application normally.
NOTE: Don't close your emulator or you'll have to do this again. Just his stop in visual studio to stop debugging.