I have been reading the forums and so far none of the solutions suggested works for me. I'm running Xcode 4.4.1 and testing in iPhone 5.1 simulator. The simulator won't open the apps anymore and I'm getting the above error. Any thoughts or solutions pls?
Go to IOS Simulator tool bar and click Reset Content and Settings...
I've met the same problem
1.you can delete the App directy under
~/Library/Application Support/iPhone Simulator/6.0/Applications
and ~/Library/Developer/Xcode/DerivedData
2.then you can start Xcode ; in the menubar you can find Project -> Clean
EDIT: before copy/pasting 1 above change the Simulator Version to what
you are using!
Click on Simulator and reset the simulator by going to the “iOS Simulator” main menu and choose “Reset Content and Settings…
Back in XCode, choose the menu "Product" > "Edit Scheme". On the left menu panel, click on "Run _Your_Project_Name_.app" > "Run _Your_Project_Name.app". The info display on the right should have the "Debug Process As" radio button picked as "Me (your-user-name)". If not, make sure you do not login as root. On Stackoverflow there are many reports of running as root will have problems
Next, still in Xcode, go to the menu "Window" > "Organizer". On the top menu, click on "Projects". Go ahead and delete "Derived Data".
Finally, go to "~/Library/Application Support/iPhone Simulator/6.0/Applications" and delete everything that’s in there
Finally, I found out the problem was I had a folder called "resources" that I used to store all my images. When I changed the name of the folder to something less likely to be used by XCode somewhere else, I did the whole delete derived data/clean/restart XCode and it worked!
Nothing from mentioned above helped me.
But as I found that few moments before, I (or some other entity) had somehow removed records from my /etc/hosts file and I got the same error.
You should check whether you have in your /etc/hosts file the line "127.0.0.1 localhost".
As this line is missing, the LLDB debugger is generating issues.
So just add 127.0.0.1 if you have it missing in your /etc/hosts.
This helped me!
Delete the app on the iOS simulator.
It works for me.
Reset Simulator and quit simulator then Rebuild-Run.Its works for me
Cleaning (either deleting folders, or Product->Clean) did not worked.
I saw that in my .plist the bundle id had been removed. Thanks to git. I checkouted-- the file, and bam! deployed to simulator no problem.
Just sharing...
Sometimes this problem arises from having two targets in a project, both using the same bundle identifier but building products with distinct names.
Deleting the application on the device/simulator solves the problem, as it has been said earlier.
This happend to me after changing the Product name.
After resetting the simulator, cleaning the project, and restarting XCode, nothing worked. After shutting down and restarting the simulator everything worked as expected.
I guess there exists someone who is in case the matter happens only in a project, not in every project and failed to resolve the matter after doing a lot of solutions posted on this Question page, such as 'deleting the App directy under ~/Library/Application Support/iPhone Simulator/6.0/Applications and ~/Library/Developer/Xcode/DerivedData', 'Cleaning all the logs by doing Project -> Clean' and 'Cleaning all the log and contents in the iOS Simulator Menu' and anything else.
Yes, I also finally failed to resolve that.
For you, It might be a solution if you are in the problem I mentioned above:
Create a new project with a similar name, and copy and paste all of your classes and resourse files existing in your previous project folder to the new one and link the references between your new project and the copied files in Xcode.
Then, clean the build logs by pressing 'Shift + Command + K'.
In my case, this made me able to continue my work...
My App didn't have a proper BundleID after deleting some xcconfig files.
I had the same problem and I found that you can't be using the root account on your Mac. If you are logged in as root you are not able to attach process to the Simulator. You have to be logged in as a different account.
Every time I have this issue (that is quite often actualy), I uninstall the app from the simulator (like a user would on the device) and do a clean on XCode. Next build and run works.
I can also reset the simulator content and settings to make it work but this seems like using a bazooka to kill a fly.
This also happens if you prepare your file for enterprise distribution and end up saving the resulting .ipa and .plist in the project directory, thus overwriting your project plist. When that happens you'll know because the version information and main window in your project configuration will be blanked. If this happens restore your old plist from source control... and save your product files elsewhere !
This happens when you switch between versions of xcode.
Simple solution is to quit xcode and simulator.
Relaunch xcode and at the same time clean the simulator befor running. This should solve the problem.
I had this problem because I had another user on the same machine running the iOS simulator. Logging in as the other user and quitting the simulator (and Xcode) solved it in my case.
Step1: ping
$ ping localhost
This should return something like
PING localhost (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.028 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.048 ms
...
If this works, this answer won't fix your problem, try something else.
If ping return something else for example: ping: cannot resolve localhost: Unknown host something is screwed up with your /etc/hosts file, go to Step 2
Step2: Check /etc/hosts
Check that the top of your /etc/hosts file looks like this
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
If it doesn't have these entries in the file, enter them at the top of the file, flush the dns cache using $ dscacheutil -flushcache and go back to Step 1, otherwise continue to Step 3.
Step3: Correct File Format: It should be unix or LF *
$ file /etc/hosts
This should return: /etc/hosts: ASCII English text
If it returns something like /etc/hosts: ASCII English text, with CR line terminators then the file is in the wrong format and is likely being ignored.
Change the file line endings to unix or LF using your favorite text editor.
In Sublime Text 2 this can be done throught the view menue: View > Line Endings > Unix
Flush the dns cache ($ dscacheutil -flushcache) and go back to step 1
Embarrassing late-night moment, but just for completeness... when you click "reset content and settings" on the emulator, of course the big blue default button says "DON'T reset", and the little white other button says "reset". If you're not paying attention it can be quite difficult to remember to read the buttons. I can't believe I'm admitting this but hey, happens to us all (right? :))
I restart the simulator and it worked for me
Some times it happens because you have two projects with same name. Try this:
go to xCode preference choose location and click on DerivedData delete the DerivedData
Reset and force Quit Simulator
Force Quit The Xcode and restart
If it has not worked than restart your PC.
and another one for the record: (none of the suggestions worked for me)
Mountain Lion: XCode 4.6.3
I moved the whole Application to Trash and deleted following other folders
/Users/[USERNAME]/Library/Developer
/Users/[USERNAME]/Library/Caches/com.apple.dt.XCode
/Users/[USERNAME]/Library/Application Support/iPhone Simulator
reboot System and reinstall XCode
Related
I would like to retrieve the welcome screen (and only it) when I start Atom. That way, I'll be able to choose the project I want to work on each time I start Atom (currently, I have to close the project opened the last time).
I already re-enabled the Welcome package in the init.coffee file so I see the welcome screen each time I start Atom, but there are two problems.
First: this screen is now shown every time I open a new window, so every time I open another project than the current one (I use Projects Manager if it matters). It's not very useful, as I only want to see this screen when I start Atom.
Second: I see the welcome screen on start, but only as new tabs in the last opened project, so the problem remains the same.
Has someone a solution?
The setting you are looking for is Settings > Open Empty Editor On Start, which is on the Core Settings page, right under Ignored Names. Make sure to enable this setting, i.e. check the box. Whenever you start Atom from its icon now, it will start with an empty editor, and will not reopen your previously used files.
I came across this problem, too.
But I found that if I had 'openEmptyEditorOnStart: true' in the config.cson file, and each time I quit the Atom I did "Remove Project Folder" in the "Tree View", next time I opened the Atom edit, I can open it without the last opened project.
Hope it helps. :)
Proper configuration to get empty editor on every start:
✔️ Open Empty Editor On Start
✖️ Restore Previous Windows On Start
Just go to File > Reopen Project > Clear Project History. It worked for me.
I just switched of package tree view
Setting/packages tree-view - disable
And when open Atom it is free of project tree
You need to do both in Core settings:
check Open Empty Editor On Start
set Restore Previous Windows On Start to no
I am trying to save a simple HTML file in GitHub's Atom text editor, but I get the following error:
Unable to save file 'C:\Users\Alexander\Desktop\Looking good website\products.html'
EBUSY: resource busy or locked, open 'C:\Users\Alexander\Desktop\Looking good website\products.html'
This seems to be a known issue when I check the atom git repo. See here.
Now somehow even though there are multiple issues opened with the same problem on the atom git repo I don't see a solution.
How do I solve this error?
I am not sure how to replicate this issue but initially the file was saving fine, but now suddenly I have this problem and I don't see any obvious solution.
screenshot :
Can somebody help please?
Re-creation of error ::
Error in Atom :
What i see in process explorer::
For some reason Atom doesn't want to save files, that you have currently open in your Windows Explorer. At least that was the issue on my workspace.
I was able to solve this issue by closing all applications using the file. I was viewing a webpage locally, so I killed the browser and windows explorer then Atom let me save the file.
Hate to necro an old thread but I just ran into this myself and believe I have found the problem; the Preview Pane in Windows Explorer.
Either deselect the file in Explorer after opening or turn off the preview pane altogether.
Get Process Explorer from LINK and use Ctrl+F to find the process keeping the file open (see MS support link)
Then tell me what you see, and I'll expand the answer :)
My anti-virus (Bitdefender) thought atom.exe was an unsafe application so it kicked on Ransomware protection.
Hope this helps somebody
I’ve been having the same issue, and I found what was causing it for me.
I had Windows Defender Ransomware Protection enabled on my computer, and I was trying to save to a protected folder. Even though I had whitelisted the atom app, and didn’t receive the usual warning from Windows, it was preventing me from writing to the location. Disabled Ransomware protection, and suddenly Atom can save there again.
Not sure if you’re in the same boat, but maybe give it a try if you have Ransomware Protection enabled. Or maybe some other anti-virus with the same feature?
Seems to be since updating Aptana 3.4 (3.4.0.201304151603 to be precise) that it regularly freezes up - greys out and displays "Not responding".
It doesn't freeze up straight away, usually after editing and saving for a few minutes. Generally seems to freeze while editing code, usually PHP.
My log file did report issues with the Subversion plugin, but I've since removed this entirely and still face the same issues.
My OS is Windows 7 32-bit.
Any suggestions on how to remedy such problems in Aptana would be greatly appreciated as this renders it pretty useless :(.
Deleting the log file seems to work for me.
Its full of pretty useless stuff for a regular user anyway and when it gets too big - boom: not responding.
Try deleting the log file ( /[yourworkspace]/.metadata/.log ),
emptying your windows temp folder (C:\Users[your user name]\AppData\Local\Temp) and run aptana as an administrator (you can make this default behaviour by editing the properties of the task bar / start menu icon for Aptana)
Maybe a new version will come out with a fix for this OR the option to turn off logging completely. Its the log file causing this issue for sure.
Do you use a git repository? Mine is freezing, too, but when I rename the .git directory to something else, the freezing stops. I'm on Aptana Studio 3, build: 3.4.0.201304151603. It's very annoying because I do use git. I haven't been able to track down exactly what about the git integration is causing this.
So I have been having the same problem with Aptana Studio 3. I have followed this set of instructions found here:
http://youtu.be/RYobTLq_hms?list=UUtL_0WLPWmHZE_HcX48F96w
Or here are the instructions if you do not want a video to watch...
Goto www.JAVA.com/en/download/ and download the newest Java Runtime Environment
Open up C:\Users...\AppData\Local\Aptana Studio 3\AptanaStudio3.ini with anything but notepad (Open with WordPad or Notepad++)
BEFORE the -vmargs line add:
-vm
C:\Program Files (x86)\Java\jre7\bin\javaw.exe
... then SAVE and CLOSE
4 . Finally open Aptana Studio 3. Now your problem should be solved and Aptana should be pointing to the newest version of JAVA.
I hope that this fix helps you as much as it has helped me!
Deleting the log file didn't work for me, but when viewing the log file, it talked about
The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
So I deleted the workspace file (/.metadata/.plugins/org.eclipse.ui.workbench/workbench.xml) which just stores what files you had open when you closed the application and the problem was installed solved (with seeminly no unexpected side-effects)
I still have this problem. It seems more often than not it hangs on startup. Win 7 64bit. One time I deleted the .metadata folder, then recreated a blank one it it worked. but it no longer works. One time I rebooted the system and it worked. The fix that works 1 time doesn't the next.
Adding the lines:
-vm
C:\Program Files (x86)\Java\*javaversion*\bin\
to the .ini file:
C:\Users\*youruser*\AppData\Roaming\Appcelerator\Aptana Studio\AptanaStudio3.ini
solved the freezing issue for me.
I have created a Cordova 2.1.0 app, It ran fine for the first 2-3 times. But now when I am trying to run it through terminal it is giving me the following error.I didn't change anything.
Ankurs-Mac-mini:~ ankur$ /Users/ankur/Desktop/CordovaSMS/cordova/emulate
Ankurs-Mac-mini:~ ankur$ 2012-10-17 16:11:08.695 ios-sim[7032:507] stderrPath:
/Users/ankur/Desktop/CordovaSMS/cordova/console.log
2012-10-17 16:11:08.698 ios-sim[7032:507] stdoutPath:
/Users/ankur/Desktop/CordovaSMS/cordova/console.log
[DEBUG] Session could not be started: Error Domain=DTiPhoneSimulatorErrorDomain
Code=1 "iOS Simulator failed to install the application." UserInfo=0x7fc643902320
{NSLocalizedDescription=iOS Simulator failed to install the application.,
DTiPhoneSimulatorUnderlyingErrorCodeKey=-1}
any help would be appreciated.
Thanks
Solved the problem
Deleting contents of ~/Library/Application Support/iPhone Simulator and re-run the project solved this problem.
or you can simply reset content and setting of the simulator.
Try manually launch the iOS Simulator and from the "iOS Simulator" menu, click "Reset content and settings", then close and rebuild your app.
My solution is:
From menu, iOS Simulator, Reset Content and Settings.
Close XCode 5.0: close project and close it from Dock and re-open the project and launch again, like in Windows :)
I tried everything mentioned above and nothing worked. My problem was iOS 7 specific. I was finally able to resolve the issue by assigning a non-empty value to Bundle versions string, short (CFBundleShortVersionString) in the -Info.plist file. Looks like iOS 7 doesn't like an empty value for the build number. I had a script that auto increments the bundle number by 1 every time I build the project so this field was empty. I just assigned a dummy value there to get it working.
You can also remove the app from the simulator.
This worked for me in iOS6.1
Solved here: https://stackoverflow.com/a/16279286/1927253
I copied a folder into XCode 4.6.2 with the name "Resources". When XCode asked, I created the folder references for any added folders.
Every time I did this, I would have to goto the Derived applications directory, and delete the build directory for my project to get it working again.
Solution: Do not copy a folder by reference into XCode with the name "Resources". Rename it to something else other than Resources.
Very annoying error.
just reset your simulator and re-run your project
Unfortunately none of these solutions solved my problem. I did everything, even restarting my mac but it was still failing. What actually did solve my problem was to go to the Organizer and delete the Derived Data and Snapshots.
Had the same problem after installing XCode 5. Had no iOS 6.1 Sim or SDK. Obtained these. Tried to run the App up under the iOS6.1 Sim and go the failed to install message. Having read through all of the above posts, I decided to simply remove the App from the Simulator and re-istall, re-run from the project window and that solved it for me.
I tried ALL these things and more including reinstalling Xcode 5 and nuking every xcode and simulator preference/application support file with no luck.
Then for the hell of it, I CHANGED my short bundle version string (it already had a value, it was not empty), and it fired right up.
3 hours gone but yeah
All the answers I looked for do not work for me!.
Finally
The only way to make it work is as follows
1.Check the version of titanium being used for the project in tiapp.xml
2.right click the prject in the project explorer window.
3.Select Properties
4.Choose project build path. Select Titanium Mobile SDk all versions of 3.* Tick all of them.
5.Now click apply and re run the project.
None of the above worked for me, I finally compared my info.plist to another project and found that I had somehow deleted the "Executable File = ${EXECUTABLE_NAME}" key/value pair, replacing it fixed the problem for me.
This error occurs on iOS 7.0 if you leave the "Build" empty.
Enter a build number!
What worked for me was to simply delete an old version of the app, which was made in a prior version of Xcode (likely 4, now running 5) from the simulator (tap-hold, jiggle, x).
I encountered this problem while trying to create a build for Facebook application approval. I found that for some reason, when I used the following command line:
xcodebuild -arch i386 -sdk iphonesimulator7.1 -scheme Mana -configuration Release
the files didn't end up in [project root]/build/... (as the instructions on Facebook suggest), but in ~/Library/Developer/Xcode/DerivedData/[app name + unique identifier]/Build/Products.
I'm not sure exactly what's going on here (anyone who knows more please enlighten me!) but I was able to run the files in the DerivedData directory on the simulator. Hopefully they'll also work for Facebook!
I tried everything mentioned above and nothing worked.
Finally the only way to make it work was unsetting DYLD_INSERT_LIBRARIES=/usr/lib/libimckit.dylib
How I did this:
Open terminal and typing "sudo vi /etc/launchd.conf"
Changing
"setenv DYLD_INSERT_LIBRARIES /usr/lib/libimckit.dylib"
to
"unsetenv DYLD_INSERT_LIBRARIES /usr/lib/libimckit.dylib"
Save changes
Reboot your system
In this post [1] explain what DYLD_INSERT_LIBRARIES is for
[1] https://stackoverflow.com/a/26053165/2091181
On Mavericks 10.9.5 using Xcode Version 6.0.1 (6A317) with an iOS SDK supporting 8.0 originally had Simulators all version 8 all getting this error. All the advice above was not working for me. So went to Xcode->Preferences->Downloads and saw as installable (but not yot installed) in the Components section were iOS Simulators 7.1 and/or 7.0. Went ahead and installed the 7.1 Simulators and got extra designations on the Product->Destination list Simulators of version 8.0 and 7.1, and using the 8.0 still had the same error, but the 7.1 Simulators all worked.
I'm on Mac OS X, and I just installed a secondary drive, onto which I placed my user's home directory.
Now, when I launch Aptana/Titanium Studio, it says that specified workspace cannot be created because directory is either invalid or read-only.
What I guess that it's looking after the old file path.
In what file can I change to the new workspace location?
Thanks!
Found a workaround.
I simply added a symbolic link into my users’ folder:
myusername -> /Volumes/Second/Home/
Voilà!
I had the same issue. I tried to change workspace to a read only location and then couldn't restart.
I searched the usual suspects for a pref file but can't find it. I suspect it's stored somewhere deep in the Eclipse framework files.
I solved it by executing
./AptanaStudio3 -data ~Home
from
~/Applications/Aptana Studio 3/AptanaStudio3.app/Contents/MacOS/
to reset Workspace to ~Home
Hope this helps a future seeker
Is Aptana/Titanium Studio closing after the workspace message or you can get to the preference menu? If so you can change the workspace location by going to
Aptana/Titanium Studio > Preferences > General > Startup and Shutdown > Workspaces
Then when you next start the application you will be asked for you workspace location and you can browse to the new location.
You should be able to change it using the config.ini file located at /Application/Titanium Studio/configuration/config.ini.
I have not had reason to do this for Titanium, but I have done in the past for Eclipse and as Titanium/Aptana are basically Eclipse spin offs this should work for them as well.
Just in case anyone faced the same problem and the answer didn't work. My problem was trivial. There was no free space on my HD! (only 2MB). If so, free some space and re-launch Aptana.
(I am wondering why the message was that vague. Why not to say "Free some space" and "free" me from wasting my time!)
I know this is old but I ended up here after copying my Aptana Studio 3 data to a new computer, and placing my Workspace in a different location, which gives the same error that the Workspace can't be opened.
If you installed into the default location (on Windows) and want to tell Aptana where you've moved your Workspace, the file where you can set the path is:
%HOMEPATH%\AppData\Roaming\Appcelerator\Aptana Studio\configuration\.settings\org.eclipse.ui.ide.prefs