Is it possible to 'simulate interface' in xcode 4.6? The command seems to be missing :-(
I am using Xcode 5 and you can find this feature under Editor-> Simulate Document (not the Edit menu) as others have pointed out.
However, this feature is only available for Mac xibs and is not available for iOS xibs.
I am guessing this was probably the same situation in Xcode 4.6 back when the question was originally asked, hence the confusion in the other questions and comments.
Is it possible to 'simulate interface' in xcode 4.6? The command seems to be missing :-(
It seems, NO
In xcode 4.6, you can find from menu bar:
Editor (NOT Edit) menu >> Simulate Document
This one may be helped :)
Related
There used to be a button called "stay in front" in older versions of ios simulater. I used this often, but in recent updates it seems to be removed. Is there a any way to activate this feature ?
new window menu
old window menu
The option "Stay In Front" for simulator staying on top of all windows is removed from Xcode9 update. Many developers will heartbreak with this including me, but we all know apple has no mercy on developers, and this is not the new thing, we all experience this kind of many things from years. Sorry mates its truth to digest.
Made a report. Please support it, as we all need this functionality
Update 11.01.2018:
Apple closed it as duplicate with no further info. Thank you, Apple.
Update 26.09.2020
They brought it back in Xcode Version 12.0.1 (12A7300)
Thank you, Apple!
Update your Xcode to : v12.0.1
I just recently downloaded the latest public release of Xcode (6.3) and I noticed the storyboard for my app is now low res on my Retina MacBook Pro. Images, text and standard UI elements all appear blurry. On the actual device everything looks fine and code still looks sharp its just while working in the Interface Builder.
Has anybody else noticed this and figured out a way to fix it? This is happening to me in both Swift and Objective-C projects including in Apple's sample projects (Master-Detail Application and etc).
I submitted this as a bug report, and Apple responded by saying that it is the desired appearance. They did not give an explanation, that was all they said.
It appears to be related to a bug in the newest iOS SDK, and as a workaround, they've forced Interface Builder to render everything at 1x. Currently, there doesn't seem to be any solution to this annoying problem other than to wait.
Just installed Xcode version 6.3.2 and this issue appears to have been fixed.
Have you tried re-installation of the same version? That helped once.
Alternatively, can upgrade to newer version, too.
Just updated to Xcode 5 and this is the first error its throwing on the logger for all my apps. Can't seem to understand why this is happening.
2013-09-19 10:46:54.341 MyApp[1156:a0b] Cannot find executable
for CFBundle 0x8a7c7a0 </Applications/Xcode.app/Contents/Developer/Platforms/
iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.0.sdk/
System/Library/AccessibilityBundles/CertUIFramework.axbundle> (not loaded)
Edit (11-11-2013): To everyone reading, once I waiting for a solid working solution to accept and close. The highest voted answer works until you re-open the project only.
Edit (30-09-2014): I can see this has been sorted since XCode 6 has been released! Finally
Final Edit-
Temporary workaround: click iOS Simulator > Reset Content and
Settings... and run again.
This error message may reappear at random. For me, it happens when I
launch a different application. There are several threads in Apple dev
forums and in StackOverflow about this problem, but none have a
definitive answer. This seems to be a SDK error to be fixed in the
next Xcode version.
Updated: October 3.
CREDIT - Please check this answer - Xcode 5 Error CertUIFramework.axbundle
Further Edit
Although this was potentially the issue resolution at the time. I believe some of the newer answers below relating to the better touch tool are in fact the correct resolutions.
After reading Kirill's answer I did some digging as I didn't want to disable BetterTouchTool for everything just the "iOS Simulator" and you can.
Open the "iOS Simulator" and will it as the active app go to the BTT drop-down menu from the top bar (of that screen if you have more than one) and select "Disable BTT for Current App". It will turn to a play icon when it's disabled.
Make sure the app name on the bar is still "iOS Simulator" as mine jumped to "Finder" a few times when I clicked the top bar!
Now re-set the simulator (if it doesn't work) and rebuild. You shouldn't get the error! :)
Don't forget to clear the error if it's still there. ;)
BTT seems to remember what apps it's disabled for (or at least it does when you close and re-open the app that's disabled I haven't tried a system re-boot yet).
Its easy. Go iOS simulator and reset content and setting.
Thanks
If you are using XCode-5 then just reset the simulator "Reset Content and Settings" and run once again
So I was having this error too in Xcode 5 and 5.1. I wanted to figure out if it's Xcode bug or something else, so I did a fresh install of Mavericks 10.9.2 and Xcode 5.1. Everything seemed fine after multiple tests.
Here is where the problem began. I put the apps and settings that I mostly use and the error came back. So I deleted everything and started adding everything one by one. After couple days I had bingo! The problem is with BetterSnapTool and BetterTouchTool
Update 12.12.2014
Just started using Xcode 6.1 and noticed that this bug seems to be gone at least with Xcode 6.1 simulators and BTT 0.9985 versions.
Update:
As GasB pointed out, it is possible to disable BTT for certain apps. So just disable it for iOS Simulator. You just have to remember not to use gestures while using the simulator as that triggers the error message.
Simple solution:
Remove the ticks in preference pane, reset simulator and do clean build. The error message will disappear.
.
I had the same problem and solved it setting the 'Localization native development region' to match my systems region. In my case from 'en' to 'de'. The referenced files are stored in localized versions in your filesystem. So this setting is used to identify the needed version.
You can find that setting in your project settings at 'Info' -> 'Custom iOS Target Properties'.
Resetting the simulator ‘fixes’ it because it turns the accessibility support off. You can normally achieve the same by simply disabling the ‘Accessibility Inspector’ in the ‘Settings’ app.
If, however, you need it enabled, particularly hate this error message, and are feeling adventurous then you can use the following monkey patches to silence the error: https://gist.github.com/alloy/9277316. (Be sure to NOT include this in your release builds.)
Resetting the simulator is a PITA, I found a way to get rid of these messages without having to to this:
go to Settings > Accessibility
turn on Accessibility Inspector
turn off Accessibility Inspector
quit Simulator
I had this problem with Xcode 5 in ML 10.8.5
I re-installed Mountain Lion (in a Parallels' VM), then update ML to 10.8.5.
Then installrd Xcode 5, and it's worked fine.
I think that the error is caused by a third SW installed in ML.
The application Moom is also causing this issue, and I couldn't find a way to disable it for just the iOS Simulator. So for now I disabled it's accessibility features.
I'm on Mavericks (10.9.3) and encountered the same error in xCode(5.1.1).
I tried anything - reinstalling xCode from both AppStore and dmg. Resetting the emulator resulted in the same error and deleting the Simulator SDK folder gave no results too.
The issue on my end was indeed Moom as mentioned by #aorcsik! Disabling it's accessibility, followed by clean (cmd+shift+k) in xCode cleared the error.
Open Disk Utility and apply Repair Disk Permissions in Macintosh HD.
After doing above step, apply Reset Contents and Settings in iOS Simulator.
This above solution can definitely fix your problem.
I had this problem, and none of the answers in this thread could fix it. Mine was simple UI with a UIDatePicker. I resolved it by removing the UIDatePicker and the associated code, then added them in again. Problem solved!
For me it was Keyboard Maestro, adding the simulator to Maestro's exclude list silenced the warnings
I am using a MacBook Pro installed with Xcode 3.2.5 and iOS SDK 4.2. When I launch Interface Builder by clicking the nib file, then I do not see any library window. Anyone has idea on why it is behaving so?
Thanks!
Xcode 4.1 view -> utilities -> show object library
If you choose Library from the Tools menu, or if you press ⇧⌘L, does it not appear?
I had same problem just after updating to XCode 3.2.6 (IB is currently 3.2.6 also).
My machine is configured to work with two display screens but I don't always turn the smaller one on.
I found the library to be present on the second screen.
How it got there I have no idea.
Try switching to a higher display resolution to see if a similar thing happened in your case.
I think the problem is there is no Interface Builder plugin for XCode 4. You probably cannot edit nib file in XCode 4.
In the Xcode menu, choose View > Utilities > Size Inspector.
Make sure the Object library is visible in the pane below the Size inspector. If not, choose View > Utilities > Object Library.
Sometimes my interface builder screen doesn't show up, and I check my sytem resources and kill off some processes. Apparently, 600 or 700 MB of memory left isn't enough for XB to launch
it works using ⇧⌘L in xcode 3.2.6
it seems to me that ever since a recent upgrade to the latest XCode, some behavior changed.
What Used to Be:
Whenever I did a "Build and Run", XCode would ask me to save changes to the opened and changed documents in Interface Builder that belong to that project.
Now:
No questions asked, open IB docs are not saved, and the new build is run without the changes in IB.
In IB, the status light at the bottom of the XIB window is green, indicating at least a sync in the other direction.
I guess this is all a simple preference setting, but you all know that preferences in XCode are as comprehensible as Microsoft Word's.
Thanks for your help
There seem to be a lot of people experiencing this, check out this thread ...
saving-interface-builder-changes-when-building-in-xcode
gary
PS: I am also having this issue since upgrading to 3.2