I've been struggling with this for the past day. I seem to be stuck with a weird bug in Eclipse where it decides to step through and exec sections that I've entirely deleted or commented. It also chooses to ignore all the instructions that I've actually added today. I've tried removing all breakpoints, clearing my bin directory, resetting my emulator, but nothing works.
Any help is much appreciated!
Thanks,
Teja.
It depends on the OS you are debugging for...
5.0 + the sim is hot-swappable, and the menu option: Project-BlackBerry-Clean Simulator actually cleans the simulator
Do you have "Build Automatically" checked? You should (for this anywho)
if you select to Debug while it is running, it will build and resume near to the point it left off (if it still exists after your code edits anyway)
under 5.0, you need to kill the old sim, run the clean.bat as mentioned above and restart the sim
Although upon re-reading your post, sounds more like your build is not making it to the sim, and it is executing the app you already placed on it... Run the sim's clean.bat and check again... Are you sure you have a successful build?
I don't know if this is the solution to your problem but here are a few useful tips:
1.If you make changes to the code and save them while you have started the debugger i.e. have started Eclipse in Debug mode(Debug as...) the debugger won't recognize the changes. You have to recompile, repackage and then restart the debugger.
2.After making the changes to your code it isn't enough to just build the project. You also have to select the project and from the Project menu then Blackberry->Package Projects. After doing this try to start the debugger.
Hope this helps.
try to clean your emulator if you haven't done this yet. Go to emulator folder and use clean.bat to clean the emulator this will remove all applications you installed on emulator.
Whenever I make changes to the BB code I need to do a clean build in Eclipse, sounds silly but it works for me. Otherwise I get the behavior you describe...
Related
Anyone have an idea about this
Error launching remote program: No such file or directory (/Users/muself/Library/Developer/Xcode/DerivedData/myproject-hlelojuljidnnagbdqzliazpdgmn/Build/Products/Debug-iphoneos/myproject.app/myproject).
The project was working fine with the previous Xcode versions. I have just updated the Xcode to Version 4.3.2 (4E2002), & the error start coming.
I have search on the web, and tried a lot of the options like
Quit Xcode, clear the Derived Data folder, restart the Xcode.
Rename the project,
Reset the device,etc
I also tried this on another machine but did not work, the same problem occurs.
But one thing i have some other projects as well and they are working fine.
Thanks for at least reading this.
First try restarting Xcode. If it doesn't work, then try hard reset of your device. This happens to me when I change the bundle identifier of my app.
This solution,I found of the above problem its working fine for me.:)
have you tried to "validate settings" (button on the bottom of project settings)? Do you use some static libs in your app? – Vov4yk
Check your deployment target. I am running Xcode 4.5, and it gave me that cryptic message, while the reason was that my iPad is running version 5.1.1, and my app was set with deployment target of 6.0.
I also get same problem. This below solution works for me.
Thats really annoying. This error happens in a number of different situations. Sometime restarting the Xcode, fixes the problem. If not, follow these steps:
Disconnect your device.
Delete the app from your device.
Quit xcode (Don't just simply close the window, quit it)
Delete derived data folder (~/Library/Developer/Xcode/DerivedData/APPNAME -gbrvhlvwmpiobxdujegtghggrffp - or something like that)
Now start Xcode, connect device and run the project. It should work fine.
Source: http://dhilipsiva.com/2012/07/24/xcode-could-not-launch-app-no-such-file-or-directory-error.html
Hard reset of the device fixed it for me. i.e. power off and back on.
Quitting Xcode, disconnecting, reconnecting the device etc didn't.
The error occurred just after I had created a new project with the a duplicate Bundle Identifier to another. Both apps coexist OK on the device/ in Xcode, but this does seem to cause the above issue.
I saw this when I let the build configuration set up as ad-hoc. After I put it back to Debug it worked fine.
I'm having some issue launching a blackberry application with an
"Error 102 Reload Software Invalid code in filesystem"
popping up on the simulator. I've cleaned and deleted all the required files from all the simulators in the RIM simulator folders (run clean.bat) and in the eclipse folders. I've also cleaned it through the clean option through the eclipse environment. However even after all this I still get the error. I've been researching online and for the most part all the solutions seem to say "run clean.bat, and restart your simulator" or "delete .dmp files". This however does not work for me. I can't say whether this is due to the code since I did not code the first portion, it was left for me to continue off. I was able to run the simulator with the application showing a few times but all of a sudden it stopped (and I hadn't coded anything yet). Does anyone perhaps know any methods on how to get it to work or what is causing this?
Deleted .dmp files on the simulator folder
Cleaned the simulator using eclipse
Cleaned the proyect
Then I run it and worked again.
Hope that this help
Run clean.bat inside the simulator folder and remove any .dmp files also. Finally in the simulator window go to File > Reset to Factory Defaults. Done!
In xcode 4.2, sometimes when you're going to run your ios proj on simulator, the status windows says "Attaching to myapp", and just gets stuck there... until you cancel.
Now, this has been asked before:
XCode 4 hangs at "Attaching to (app name)"
and surprisingly, besides the accepted answer on that thread, there are at least 10 other possible solutions others have been adding, all for the same issue, people says one of them worked while the others didn't...
please note, this is not a sequence of steps. each one is a possible solution:
1- restart xcode and/or restart simulator (reset content and settings) and/or restart computer.
2- click on project name in project navigator. in build settings tab, go to packaging and make sure that "Product Name" is the same that the one xcode says simulator is attaching to when running. if they are different, it will fail.
3- go to your projectname.xcodeproj folder. inside there delete anything named with your userid. when you reopen xcode those files will be recreated and it should work…
4- Manually delete the build directory for your project.
5- Go to organizer window. select Projects, select your app in the left hand side and then delete over "Derived Data"
6- Check Launch option is set to "Automatically" in Product->Edit Scheme, "Run" scheme.
7- In Project->"Edit Schemes"->Run. Change the Debugger from GDB to None (this doesn't make sense to me..).
8- Kill the process gdb-i386-apple-darwin from Activity Monitor. this is assuming gdb is not responding.
9- In "Product"->Edit Scheme. in Run, click yourappname.app, choose other, navigate to your .app in your project. now run.
10- Check that you don't have two different Info.plist in your project. if you do, remove the bad one.
In my case, none of them do the job. My project builds succesfully, everything seems fine, .plist, bundle identifier, name, etc.. and still can't pass the "attaching" part. i don't understand the reason of this, so any suggestions to fix it and possibly understand the problem i'll really appreciate it.
New projects were failing to launch in the simulator, getting stuck on the attach step.
This seems to be after Xcode 4.3 was installed, but I can't recall the last new project I created.
This is what worked for me, the clue coming from this thread...
Project->"Edit Schemes"->Run. Change the Debugger from LLDB to GDB
Another computer with the same version of Xcode works fine. Maybe my LLDB is corrupt?
Did you recently upgrade to OSX 10.7.2? I started having the same problem after I upgraded. I noticed that the Simulator always get stuck if I'm connected to a Wi-Fi network that forces Captive Portal authentication. This happens with other apps as well (Chrome, Safari). I'm not really sure why this happens, but I did read that 10.7.2 has issues with Captive Portal authentication.
Anyway, in my case, I repaired disk permission from Disk Utility and rebooted my machine. This seems to resolve the issue.
Just rebooting the computer worked for me.
Tried all the solutions but none applied to my case. XCode 4.2, OS X 10.6.8
Found that the Info.plist bundle identifier had been accidentally deleted when adding a custom app icon. Adding that back fixed the problem.
Anyway that's my fix, hope it helps someone.
Also before figuring out that, found I could start the simulator from another app and then use the app icon on the simulator for the app that would not attach, and start it up that way.
seems like there seem to be a lot of things causing this, but one thing that worked for me was simply cleaning out the build folder by pressing Cmd+Option+Shift+K or alternately if you select the Product dropdown in the toolbar and hold the Option button you should see the "Clean Build Folder" option appear
I also tried all solutions in that topic but all failed. But finally it was found out that what was went wrong.
What made this issue occurred is that some settings in Target->Build Settings was got modified by me for including C headers. And after I added all C headers and make it built. This issue occurred.
It might be only works on the situation I described before.
I just created an empty project and check all items in Target->Build Settings between the attaching-stuck app and the empty one. It was found that some items in the attaching-stuck one was different from the empty one.
So I deleted it and make it attached successfully.
It seems different in my case and also solved in a different way. If you got stuck every time after drop some files or folders into your project with the 'Create folder references for any added folders' way, this will be the solution.
Click the project node(the root node) on Xcode's project navigator and select target node. It's under the 'TARGETS'. Then click the 'Build Phases' tab. There are 4 sections of some list and you can click the triangle to expand the list.
You need to concentrate on the 'Compile Sources' and 'Copy Bundle Resources' section. Code files like .m must be placed on the 'Compile Sources' section and are compiled automatically. Resource files like .jpg must be placed on the 'Copy Bundle Resources' section and are copied into the project's package.
So, if the dropped files and folders are not in the 'Copy Bundle Resources' list, just drag it form the project navigator and drop onto the list. That will solve the problem.
If it doesn't work, delete all the referenced files and folders, click '+' button on the resource (or compile) section and click 'Add other...' button. Then you can include files and folders as the 'Create folder references for any added folders' way. I think the 'drag and drop' works well after the '+ button' way is done once.
In addition, 'Resource' may not allowed for folder name.
I experienced the 'stuck' problem every time when I attach files and folders as reference on Xcode 4.2 ~ 4.3.3. Reinstalling mac was a useless effort for me.
I have noted in Lion that when the iOS sim locks up or hangs the app,
that if I go to a shell, and do ps -ef |grep SDK, I will
see many, many processes running associated with the simulator.
I tried to kill off these processes but they rapidly respawn
and the only solution then is to reboot. Also, in the ps output,
you will also see instances of your app running as well.
So the Simulator issue is caused by previously running processes
that appear to block the correct running of the latest one.
I guess Apple will have a fix for this eventually, as it is quite onerous.
Rebooting works for me, too, but this shouldn't be necessary. I'd recommend filing a bug at bugreport.apple.com. You can duplicate the one I created - the more it's duplicated, the more likely Apple is to fix the problem.
I tried all of the solutions above but without luck ...
When I search for simular problem here :
Xcode error: failed to launch [directory] -- invalid host string: 'localhost'
I found it fixed my problem!
Hope this helps those who are still searching for a clue .
Upgrading to XCode 4.6.2 resolved this issue for me
Even if the app is not attaching after cleaning the project, changing the app name, restart the by resetting the simulator, and if you are using LLDB compiler, it is because the LLDB compiler is not able to connect to the local debug server in order to solve this, take a look at this
Why does the LLDB Debugger constantly fail to attach?
This really solves your problem!
So... this is beyond strange.
I had an app that was running perfectly fine in simulator and on device. I've actually already submitted the app and it is for sale in the App Store.
Today I went back in and made a few changes for an update.
The app now will not load on my device and it won't load in the simulator.
In the simulator it says "Attaching to app_name" (it lists the actual app name) and it stays on this process of "Attaching" indefinitely, while the Simulator screen is entirely black.
When running the app on the device it says "Build Succeeded", then "Finished running app_name" without anything ever showing up on the device.
I restarted XCode and tried restarting my computer, but still no luck...
Other apps do work, but not this one.
Any ideas?
EDIT: I just started a brand new project, copied over all the assets and code, tried running and STILL the same thing happened. I thought for sure creating the project anew would work...
FINAL EDIT: After running "Clean", deleting the DerivedData folder, and restarting my computer a SECOND time, the new project (with all assets copied over) is now working. The original project still does not work. So I am not sure what caused the issue and what fixed the issue, but for me at least I can now move on. What do I do with this thread? Can it just be deleted? Thanks everyone who chimed in to try and help!
Tried above options but didn't work for me.
Finally, Just Resetting Simulator did the trick.
In the options move the DerivedData into your project directory. Whenever I have problems with xcode4 I just quit it and delete this directory. It contains the builds and caches of the background compiles that xcode4 does.
Deleting this folder usually fixes all problems I get.
Try cleaning your project. In Xcode 4: Product menu >> Clean.
Why don't you try this one.you can quit the simulator and run the project again.This works for me
There are a lot of different solutions people suggest for this:
Do a clean
Reset simulator
Do a 'clean build folder' (hold down option key when selecting clean)
Remove ~/Library/Developer Tools/Xcode/Derived Data/YourProject*
Remove your 'xcuserdata' directory inside your .xcodeproj directory
I just spent an hour trying different combinations of the items above, doing all of them, ... nothing worked. My app would either 1) Immediately start and quit before launch screen would show up, or 2) Hang at launch screen. The simulator took forever to reset, sometimes wouldn't respond to a Quit, ... Just really odd stuff going on.
This solved my problem: Reboot machine.
(It blows my mind this had to be done on Mac OS, but it worked. This may have something to do with upgrading to XCode 4.6 and not rebooting since then, I'm not sure... But I'm back running again)
Tried all posts here without success. Then I found something that worked for me:
I had a ~3000 resources folder in my Xcode Project.
At first I had them as "folder reference", which made XCode unable to launch the app.
When I switched them to be a "group" in the project, the error was gone.
I still needed to restart Xcode and the Simulator and rebuild, but it worked.
When I create a new window based application, I get:
Failed to launch simulated
application: iOS Simulator failed to
install the application.
I tried to do what this post suggest, but didn't work
Any suggestions? I haven't tried re-installing xcode yet.
Choose Reset Content and Settings in the File menu of the Simulator.
Build Clean in Xcode
Then try again.
I'm not sure why, but rebooting my machine seemed to fix it.
I had the same problem. A reboot also did the trick, but then I realized that the directory
~/Library/Application Support/iPhone Simulator/6.1/
looked "different" after the reboot (Directory "Root" was missing). So I tried to reproduce the error by deleting the directory or parts of it. The simulator each time recreated the directory and worked fine. Maybe the reboot is not really needed just recreating the mentioned directory would also help.
Try to delete project.xcworkspace file and xcuserdata dirctory in your project
It seems that the processes don't get cleaned up properly each time you stop the app with ps aux in Terminal showing a large number of processes representing your app on the simulator.
I expect some kind of upper limit is reached with the number of processes / memory. (Indeed I have found that XCode will fail to build because some posix resource can't be found because there isn't memory to load it)
A machine restart clears all of these dead processes and allows room for new ones. For me, I only have to do this after about 2-3 weeks of not turning my computer off, but I suppose what resources you have and how often you use the Simulator will affect it.
If someone knows how to clear all these dead processes without restarting, that would be useful please, killall ... doesn't seem to have worked for me, but feel free to add to this answer.
Simply go the info.plist file property and set 'Copy to Output Directory' to 'Copy Always' it will resolve your problem.