Is there a current Xcode beta? 7.3.1 is crash happy

Discussion in 'iOS Programming' started by Analog Kid, May 17, 2016.

  1. Analog Kid, May 17, 2016
    Last edited: May 17, 2016

    Analog Kid macrumors 601

    Analog Kid

    Mar 4, 2003
    I've recently gotten back into iOS development, so I don't have a paid Developer account-- which is fine for now, I'm just playing around with ideas locally, but I'm wondering if I should pay up.

    The problem I'm having is that Xcode 7.3.1 has gotten rather unstable-- refusing to compile things, and throwing segfaults when trying to compile one file in particular. I suspect it's because of the move to Swift 2.2, and my use of the simd library and a rather elaborate (probably over-elaborate) set of generics and PATs.

    Problem is that it's hard to tell what the complier doesn't like if it just keeps segfaulting. It works ok in the Playground.

    Add to that the slow parsing of the Swift code and constant complaints that certain lines of code are "too complicated and taking too long to process" and I'm willing to brave a beta.

    So I'm wondering if there is a current Xcode beta available that I might try to use to get past this. Are the betas only visible to paid developers?

    Barring that, is there a way to get back to 7.2 without restoring from backup?
  2. PhoneyDeveloper macrumors 68040


    Sep 2, 2008
    Only paid developers can access betas of Xcode.

    In order to install a particular version of Xcode you need the installer for that version. It's available to paid developers only.

    Finding compiler bugs is usually a straightforward process of commenting out methods until you find the one that causes the problem. Then comment out the code in that method until the problem goes away. Once you figure out the code that's causing the problem you can rewrite it so it still does what you want but doesn't cause the compiler to barf. Sometimes it can be more complicated than that but start with that. File a bug if you can isolate a clear example.
  3. Analog Kid thread starter macrumors 601

    Analog Kid

    Mar 4, 2003
    Thanks for the response.

    Yeah, I'm down to bisecting code as best I can.

    Are you able to say if there is currently a beta of Xcode being circulated? I don't need details on what's in it, just wondering if springing for the $100 or whatever it is will get me any benefit today.
  4. Mascots, May 18, 2016
    Last edited: May 20, 2016

    Mascots macrumors 65832


    Sep 5, 2009
    yeah - at the moment there isn't and more than likely won't be until iOS 10's l̶a̶u̶n̶c̶h̶ beta.

    Though crazier things have happened, I wouldn't hold my breath.
  5. Dranix macrumors 6502a


    Feb 26, 2011
    Gelnhausen, Germany
    I'm pretty sure we get Xcode 8 alpha or beta at WWDC including Swift 3.
  6. Amazing Iceman macrumors 68040

    Amazing Iceman

    Nov 8, 2008
    Florida, U.S.A.
    7.3.1 is not crashing for me. Something else may be causing it to crash.
    Possible causes:
    • Antivirus
    • Git Repository setup and DerivedData folder is inside the project folder.
    • Not enough RAM (Less than 4 GB)
  7. iphonedude2008 macrumors 65816


    Nov 7, 2009
    Irvine, CA
    To preface, there is no beta for devs rn, and if there was it's not like were banned from talking about it (I mean we probably are, but it's not like apple puts NSA secrets in their betas or something).

    Whenever you have crashes with Xcode:

    1. quit and restart. I'm assuming you're not stupid, so let's move on

    2. Delete your entire derived data folder. This thing gets corrupted from time to time, so that may be your problem. Don't be concerned deleting it, it's just indexing and some compiled code, but it'll all get recreated when you build your app again

    3. Check your libraries and dependencies. This is more of a case by case thing, but sometimes sketchy libraries seem fine to Xcode, but when it tries to access parts of them it fails because of bad code

    4. Try making a new project and adding back your old code until it crashes again to find the offending code, if that even is the problem

    5. Give up until some genius posts a magic terminal command that makes no sense but fixes Xcode, solves the p vs. np problem, and ends world hunger

Share This Page