High number of xcodebuild processes get created when I click RUN - iphone

XCODE version: 4.6.2
This is what happens when I click on RUN.
Message: "Running 1 of 1 custom shell scripts" and the progress bar just halts.
Then just creates a lot of xcodebuild processes(I can see the processes getting spawned in Activity monitor).
I quit XCODE from Activity monitor, but still the xcodebuild processes keep getting created.
As a background my app had a few warnings before i hit the RUN button in XCODE. Any clue how I can debug this without restarting my Mac everytime?

Related

Flutter cannot connect to emulator in VSCode. Waiting for a connection from Flutter

I can see the device list on VSCode in Windows.
And I can select any one.
And the emulator is opening.
But I can see a single message. "Waiting for a connection from Flutter.."
Application does not open.
It doesn't get any errors either. Waiting like this.
Make sure that your API level you're running your device on is the
same as what you have installed on Android Studio.
1.1 Click on the SDK Manager button around the top right corner of AS (The icon is a box with a down arrow next to it).
1.2 Choose the same API level as your device, (When I didn't do this I had a partial install and it took some time to compile), then
click apply and wait for it to install.
We're going to run the project to our avd or mobile device from the directory of ourproject.
2.1 Open up the Command Prompt (preferably as Admin), and chage the directoy to where your project is, the command should look something
like this:
cd Documents/flutterprojects/yourflutterproject.
2.2 Finally type the command flutter run.
Restart the Emulator by holding the power Button and Selecting restart and then try again.
if that failed to work, simply restart your computer.

How can i know an application running in debug or run mode in eclipse

I do start/stop my application more than 15 to 20 times every day. Every time i start app in debug mode only. But some times the debug(break points) would not work, then i will get confuse that is my app running in debug or run mode.
Do you have any idea to find out.
Even some times, I started my app in debug mode and it runs in debug mode for some time, suddenly works as run mode, it would not consider my break points. so, if i restart my app in debug mode only, i can do debug again.
While the application is running, open the Debug view in Eclipse. If all that you see in the tree is a path to your Java distribution under the project name then you are in run mode. If you are in debug mode then you will see the above information plus all the threads that are currently running in your application.
When you launch your application, the mode into which it runs is indicated in the "server" panel, like this :
or
Sometimes, when the debug mode doesn't work(for example it can't start), I remove all the break points, then I set them again.
Make sure what you run 1st.
Debug mode should display you code with variables in debug tab in eclipse while program is running.
Is your application a standalone application or a server hosted application which you remote debug? In both cases as soon as the debugger is connected to whatever local or remote process the signs left to your debuger icon get enabled. Those are in a row a few arrows (Step back, Step into, Step over) a green Arrow for Resume, a Suspend Icon, one for Stop and one for Disconnect.
If you open the debug View (Window->Show View->Other... type in "Debug") you should as well see if your Debugger is currently connected to any process.

Couldn't register com.XXXXX.deviceapp with the bootstrap server

I am getting this error while running in device please do need full help to solve this;
Couldn't register com.XXXXX.deviceapp with the bootstrap server. Error: unknown error code. This generally means that another instance of this process was already running or is hung in the debugger.Program received signal: “SIGABRT”.
I have had this happen where I needed to restart the phone before error would go away.
Deleteing the app, restarting Xcode, clean build, didn't do anything. I shut the phone down and bought it back up and the error went away.
Most annoying bug.
Only solution at this point:
If you're trying to run on a device: Shut off and restart device
If you're trying to run in simulator on Mac: restart your Mac
You can also do a Force Quit on the process via the Activity Monitor.
I've run into that with the simulator and the only solution I've found is to reboot the computer running Xcode.
kill all Simulator processes, that can cause this error as well.
using following terminal command
kill -9 `ps ax | grep Simulator | grep -v grep | awk '{print $1}'`
Reference
This seems to happen with the LLDB debugger when an app is paused at a breakpoint and the app is run again from xcode. The result is a zombie process on either the device or the development machine (when debugging in the simulator).
Only way to resolve seems to be a restart of the iDevice or the machine running the simulator.
Stopping the app completely before running it again in the debugger appears to prevent the problem from happening.
I managed to solve the issue by deleting my device form the Xcode 4.4 Organizer:
disconnect your device from your computer.
in Xcode: Window => Organizer
Choose the first tab ("Devices") from the top panel
Right click your device from the list at the left side of the Organizer, and choose "remove from organizer"

Applescript Xcode to clean, build and install on iPhone device

I'm trying to applescript XCode into building and launching on device. My script is as follows:
tell application "Xcode"
open "tmp:iphone:myproject:Project.xcodeproj"
tell project "Project"
clean
build
launch
end tell
end tell
My project consists of two targets, MainTarget and a SideTarget, the SideTarget is added as a direct dependency of MainTarget. I noticed that when my applescript runs on a pre-cleaned project (removing the build folder) only 65 files are compiled compared to when I press the "Build & Run" button in XCode 130 files are compiled.
The "launch" command in the script seems to be ignored when running the applescript - it simply does not launch on the device. The status in the bottom bar when the script is complete is "Build succeeded". What is the difference between "build" followed by "launch" compared to pressing the "Build & Run" button in the XCode top bar?
The project launches fine on device when building and running through XCode.
My main issue is that I can't get the applescript to launch on device. I do not know where things go wrong. Has anyone successfully scripted XCode to launch on device?
I've had this same problem. launch just does not work. You'll have to use debug instead.
Also, debug blocks forever, so invoke it with timeout and catch the timeout error and ignore it.
build and build and run are two separate commands within Xcode's GUI (v3.1.4 with build and go (run) and build and debug being the remainder). But the Dictionary for Xcode only shows build as being supported via Applescript. I would say both of these commands are the same as they are in the GUI, and in a perfect AS world we would see build and run in the Dictionary to make it more clear.
My question is whether launch is really building the app or just launching the previously built executable.

error issue on the debugging process

In Eclipse®, on the Run menu, click Debug Configurations or Run Configurations.
Expand the BlackBerry Simulator item.
Perform one of the following tasks:
To work with an existing launch configuration, under BlackBerry Simulator, click a launch configuration.
To work with a new launch configuration, right-click BlackBerry Simulator, and click New.
Click the Simulator tab.
Click the General tab.
Click run
i have followed all the steps above but still i am getting the error failed to connect to the remote VM.Connection time out.org.eclipse.jdi.TimeoutException
can anyboby help me in this issue
Do you see this every time you launch your test?
This thread mentions:
For the 8530 simulator just try it again.
I get that message sometimes when I am running too many apps/low memory (I do a lot)/just started Eclipse/etc.
Often if I run it a second, sometimes third time it works and continues to work after that.