• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode 8 and iOS 8
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 8 and iOS 8


  • Subject: Re: Xcode 8 and iOS 8
  • From: Alex Zavatone <email@hidden>
  • Date: Tue, 11 Oct 2016 14:08:14 -0500


On Oct 11, 2016, at 1:56 PM, Jens Alfke wrote:


On Oct 11, 2016, at 11:47 AM, Alex Zavatone <email@hidden> wrote:

With this data, it's clear to me that Xcode 8 has a pretty significant issue with building to iOS 8, one that should be apparent to anyone who tried to build and run their app on iOS 8 from Xcode 8, as long as their app has view controller that features a method known as viewDidLoad within it.

Just because you get this bug, doesn�t mean that everyone else does.

I am aware of this.  However, three separate projects all exhibited similar crashes when we attempted to run them on iOS 8, leading me to think that. "since the app is crashing in random places and across 3 completely different code bases, should I spend the time to collect and list each crash or just ask if this is a well known issue."


Consider that, if this were true, you�d be hearing a lot about it from lots of developers; it would perhaps even make it to dev-centric news sites like Daring Fireball. Users still on iOS 8 would be complaining that every app that updates starts crashing afterwards. It�s pretty unlikely that Apple would even ship a GM release of Xcode with such a glaring bug.

I think it�s a lot more likely that there�s something specific to your app. Maybe you�ve got a random memory-smashing bug that somehow never manifested before, but is triggered by some change in the way Clang generates code. Or maybe something very specific that you�re doing is triggering a code-gen bug in Clang, or there�s an obscure API you use that Xcode is generating incorrect calling code for.

Have you run your app with the Address Sanitizer? That�s where I�d start.


This report details at least part of what I am seeing.  And to your advice, using the address sanitizer gets him crashing at main more often.

http://stackoverflow.com/questions/39735353/exc-bad-access-only-on-xcode-8-running-ios-8

I'm going to pursue the sRGB path since changing the deployment target to > 8.1.3 is not an option for me since I only have an iOS 8 device that is at 8.1.3.

Thanks guys.  

Muchos thankos.
- Alex Zavatone
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Xcode 8 and iOS 8 (From: Alex Zavatone <email@hidden>)
 >Re: Xcode 8 and iOS 8 (From: Quincey Morris <email@hidden>)
 >Re: Xcode 8 and iOS 8 (From: Alex Zavatone <email@hidden>)
 >Re: Xcode 8 and iOS 8 (From: Jens Alfke <email@hidden>)

  • Prev by Date: Re: Xcode 8 and iOS 8
  • Next by Date: Re: SVN Warnings in Xcode
  • Previous by thread: Re: Xcode 8 and iOS 8
  • Next by thread: Re: Xcode 8 and iOS 8
  • Index(es):
    • Date
    • Thread