I'm using Xcode 6.0.1 on Mavericks and experiencing crash every time I try to inspect UI and:
unfold the view hierarchy
rotate the 3D inspection view
But it's not just crash. It literally restarts my Macbook Pro.
I had the same problem, and I was able to narrow it down to an issue with the discrete graphics card on my Macbook Pro (it has the hybrid integrated Intel / discrete Nvidia chips). When forcing my Macbook Pro to use the integrated Intel chip exclusively, it no longer crashed.
You can get gfxcardstatus to force your Mac to use the integrated chip exclusively.
If you use Homebrew Cask,
brew cask install gfxcardstatus
and then select 'Integrated only' from the app's menu bar icon before inspecting the UI.
It is bug for new Xcode with old System Maverick. I install new Yosemite and all working on my MacBook 2009.
Related
All I've done is unpack the zip, and when I try to open Android Studio, it crashes immediately. I see the icon in the dock for two seconds tops, before it crashes.
I also tried using the latest Canary build and have the same results.
I checked and apparently JDK comes bundled with it, so I don't need that installed in advance.
Am definitely using the M1 / ARM build for macOS running macOS Monterey Beta.
The traceback error is incredibly long and I am unable to pin where the issue lies, and I'm not sure that I should really post the entire thing. Where I am confused is that this is a relatively new Macbook Air on the M1 chip with hardly anything installed on it, so I don't understand what the conflict is or where to begin here...
Fixed by upgrading to the latest beta.
I created a react native app using react native cli.
When I use finder to navigate into ios folder I can see podfile.....however when I open the project in xcode I cant see it anywhere.
Any idea why?
UPDATE 4/29 - I tried answer below to "Open the xcworkspace file with Xcode not the xcproj one"....and this did not work. Regardless of which file I use to open, I still dont see podfile (or xcworkspace file for that matter)
Im using Xcode 12.5.....and a macbook air with the new M1 chip (I mention this because the M1 chip has been causing me a host of other problems like not being able to download IOS simulator)
Open the xcworkspace file with Xcode not the xcproj one.
I ended up exchanging my macbook air with M1 chip....for an older one with Intel chip. All the issues I was facing before are no longer.
My advice is to not purchase any laptop with M1 chip until Apple have had time to figure out all the bugs that occur for developers (M1 chip was only launched last Nov and theres still SO many issues for devs).
I have a MacBook pro(mid-2012)with following configuration(8GB RAM, MacOS Sierra, and 512 GB HDD). I updated my Xcode version from 8.2 to 8.2.1. After updating to that version system not responding properly (till 8.2 it works properly), I have to wait 5 or more minutes for one click. So please help me on that to fix that issue. For that performance issue,
Note: I reinstall MacOS twice but getting the same performance issue again and again when I open Xcode before that it works properly.
Steps to Reproduce:
Open Xcode with any existing project and open simulator from Xcode developer tools then you will see that system is not responding properly.
Expected Results:
If it will work till 8.2 then it will also work in Xcode 8.2.1 in MacBook pro
Following is my system configuration and activity monitor results.
CPU Usage
enter image description here
2: https://i.stack.imgur.com/0lEj3.png system configurtion
4: https://i.stack.imgur.com/WdoZW.png before xcode start
after xcode and simulator both starts cpu usage in activity monitor
CPU usage when both are running.
Check your "Activity Monitor" Mac App, monitor which tasks are taking more memory (%CPU). Try to force quit unused apps / tasks. And try again.
Finder -> Applications -> Activity Monitor
I have a macbook pro(middle-2012) in my home, and I can not use it to write the code any more, because it is too slow, I promise, if you replace a newer macbook pro, I think the issue will not comes.
In my company, I use the company's Macbook pro(2015) or Mac Mini(2014 late), with Xcode 8.2.1.
These there will not get slow, improve the configuration of your hardware.
I have installed the developer preview of the new operating system Yosemite. Xcode 5.1.1 and then I did the 10.10 update. After performing the update and restarting, when I open Xcode 5.1.1 I get this cyan circle with a cross hair in side of it. I cannot move it around nor close it.
Is there anyone that knows how to remove it or is experiencing the same issue.
My screen shot is available at this link:
http://i.stack.imgur.com/sK7JK.jpg
You're using a pre-release OS with a version of Xcode that doesn't officially support the OS Version so there is a good chance of you finding that things don't work as expected.
You should probably download Xcode 6 Beta 2 from the iOS/Mac Dev Centre and use that instead as it is designed for 10.10.
Xcode 5.1 is theoretically useless on the developer preview anyway as you cannot submit apps to the app store that have been compiled on a machine running a pre-release OS.
Recently i upgraded to mountain lion.I want to open my old projects in older version of xcode 4.3 and i don't want to use xcode 5 for some reason.
Is there any way to open xcode 4.3 only. I have installation file of xcode 4.3 if its needed to reinstall.
It gives alert "This installation of Xcode 4.3.2 requires Mac OS X 10.7 Lion."
I know how to run my projects in other versions with old simulators... but only need 4.3
Any Suggestions?
Ignore the snarky comments by people like matheszabi; there are good reasons to support the millions of units of older devices. Tip: If you are looking at picking up older devices, you'll want to target iOS 4.2.1 not 4.3, as every device supporting 4.3 can be upgraded to iOS 5. See Highest Version of iOS Supported.
Virtualizer
To answer your question, "Any suggestions?": Use a virtualizer like Parallels, Fusion, or VirtualBox to run Lion, Mountain Lion, or Mavericks in a virtual environment. This arrangement has many advantages, including resisting the pushing and shoving of Apple to constantly upgrade our OS, Xcode, and iOS targets.
Another advantage is a pristine working environment with its own clean Keychain, Desktop, and so forth having only items related to Xcode project(s). All my own personal stuff is kept to the real Mac. I think of the real Mac like I do my home, with personal property, while I think of the virtual Mac as my office space, my cubicle, having only work-related items.
The one thing you'll need is memory (RAM). If you want a 3 or 4 gig virtual Mac, you'll need about that much space unused on your Mac. By unused, I mean the green colored piece of pie in Activity Monitor.
My Experience
For my current project, I run Xcode 4.6.3 targeting iOS 5 & 6 in Parallels 8 (9 is now available) on a Mac mini (Late 2012) with 16 gigs of memory and i7 quad-core with 8 virtual cores driven by Mountain Lion 10.8.5 on the real Mac, while the virtual Mac has 4 gigs of memory and 2 cores. For the most part this works very well. A few bugs, but no show-stoppers.
The only bad bug is that copying text from the real Mac and pasting into the virtual Mac appends an extra mysterious invisible character that wreaks havoc, including preventing compiling of Objective-C code. I routinely do searches for that evil character, and try to make a habit of hitting Backspace after pasting text brought over from the real Mac.
Another bug: Horizontal scrolling by finger-swiping on my Apple Magic Mouse does not work in the virtual environment.
But Parallels 8 + Mountain Lion + Xcode 4.6.3 works well. You can plug in an iOS device for direct debugging via USB cable – Parallels asks whether you want the connected device to be seen by the real Mac or the virtual Mac.
I've also run earlier versions of Xcode 4 on Lion (besides Mountain Lion) in Parallels 8.
With this arrangement, I am free to consider upgrading my real Mac to Mavericks while keeping my Parallels 8 + Mountain Lion + Xcode 4.6.3 work environment intact. Though, I may need to shell out some money to upgrade my Parallels 8 to the new version 9. No such thing as a free lunch! (But this arrangement comes close)
Backups
Tell Time Machine to avoid backing up the 20-50 gig file that is your virtual Mac's hard disk. Instead, do an occasional backup of that large file. More often, make a backup of your import work files and Xcode project, copying off to Dropbox, Google Drive, or external hard drive or SD card. If that file that is your virtual Mac's hard disk ever gets corrupted, you may lose everything. So backup religiously – though I'm sure you do so anyways now. ;-)
Looks like Xcode 4.3 doesn't know about Mountain Lion, the fix would be downloading and installing Xcode 4.6.2 from developer center, which surely supports it.