Search results for

LLDB crash

29,555 results found

Post

Replies

Boosts

Views

Activity

Reply to Testing app versioning
I think the ad-hoc installation process most closely mimics the App Store distribution. So I would start by installing an ad-hoc build of your old version, then installing an ad-hoc build of the new version over top.The app crashing on an update is a sign that your application data, which is preserved from the old version, was in a format that your new code didn't handle properly. Apps do not normally crash when updated unless there are bugs.
Jun ’15
NSPersistentDocument initWithType Crashes Compiler
I have an existing document-based Core Data application that I converted to Swift 2 in Xcode 7. After converting the project, the compiler crashes every time I build the project. I narrowed the problem down to the convenience init method I override in my NSPersistentDocument subclass. If I comment out the init method, the project builds.But if I have the convenience init method in my code, the compiler crashes, even if the only thing the init method does is call self's init method.convenience init(type typeName: (String!)) { self.init() }What changes do I have to make to the convenience init method to prevent the Swift compiler from crashing when building the project?
3
0
519
Jun ’15
Reply to Compiler crash
As an update, I tried enabling the module optimization on another, smaller project, and it does not result in a crash.In my crashing project I am mixing objc and swift modules. I wonder if that could be it.
Topic: Programming Languages SubTopic: Swift Tags:
Jun ’15
on device only - dyld: Library not loaded
My app workspace has a subproject that compiles a framework, which the app obviously depends on. If I run my iOS8 compiled app on an iOS9 iPhone, works fine. If I compile for iOS9 and run on simulator, runs fine.But - if I run iOS9 compiled app on a device, it crashes on launch. Specifically, console complains that dyld: Library not loaded [snip] Reason: no suitable image found.Anybody else run into this with iOS9 ? Or ideas around it?
2
0
619
Jun ’15
Avoid Swift importing Objective-C as Implicitly Unwrapped by Default
This continues the discussion from https://devforums.apple.com/thread/271101Summary:In a mixed Swift/Objective-C project, when Objective-C code is brought to Swift as implicitly unwrapped optional by default [1]E.g. the Objective-C method signature: - (NSString *)giveMeAStringwill be seen by Swift like this:func giveMeAString() -> NSString!The method giveMeAString might return nilAs Swift unwraps the method result implicitly, the following code will crash: // Objective-C - (NSString *)giveMeAString { return nil; } // Swift func thisWillCrash() { let string = someObjectiveCObject.giveMeAString() let length = string.length // crash }The bad thing is that the compiler does not give any warnings in this caseOf course the Objective-C code could be annotated with nullability annotations to avoid these issues, but it is unrealistic to do it at once for a large code base (as also seen for Apple SDKs)This issue makes a mixed Swift/Objective-C app much more error prone than a pure Objective-C or a
10
0
2.2k
Jun ’15
iOS 9 beta: setting it up as a daily driver
OK, so you read the part about it's only to be installed for development purposes and figured that was the dead hand of Steve reaching up to keep you from having fun right?Unfortunately: it wasn't.Right now they aren't kidding and you need to understand something to use iOS 9 beta as your daily driver: a development device has the beta installed and a development app. It doesn't have 1024 apps and 100GB of it's 128GB of storage filled up with movies, photos etc... nor is it plugged into every social network and email account known toThe Cloud. And it's chock full of bugs that developers don't care about because they're focused on making siri work with their app.Got it?So if you still want to make a daily driver out of iOS 9 beta, because you know, you are wink-wink-nudge-nudge testing the bits to help find bugs for Apple instead of fixing up your own code....For the first day you will need to treat it like a WIndows OS Desktop.Keep it plugged into power. (Desktop)Keep rebooting it. (Windows OS)Ideally you sho
0
0
669
Jun ’15
Reply to Source code for WWDC app?
The WWDC App is not available but was dicussed in session 226 Advanced NSOperations.In a follow-up discussion I had at CloudKit Labs shortly after Session 715, CloudKit Tips and Tricks, I discovered there is no reference app for CloudKit. Instead, I was directed to refer to the Sample Code discussed in session 226 Advanced NSOperations. The Sample Code is called Earthquakes.Unfortunately, I've not been able to get that to run correctly using XCode 7 and IOS 9. It runs on my device but doesn't do anything upon launch except to show an empty UITableView. A refresh swipe results in a crash.
Topic: App & System Services SubTopic: Core OS Tags:
Jun ’15
Reply to OS X image editing action extension has no affect in Mail.app
Haven't done an action extension in a bit. See this old thread: https://devforums.apple.com/message/1105124#1105124There's a post in there from someone who says images will work in Mail if you pass back NSData for the image instead of an NSImage object. The poster claims though, that passing back NSData in TextEdit will crash the app. No idea if they made any changes since or 'patched it'. Maybe Pixelmater passes back NSData.... you can try that and see if it works in TextEdit too (if indeed it does work..again I didn't try it myself).
Topic: UI Frameworks SubTopic: AppKit Tags:
Jun ’15
Reply to Can't fetch JSON due to NSInvalidArgumentException
Looking at that code, I would suspect the data is nil error is coming from some other place, not from your NSURLSession completion block. If you are positive that's where the crash is, then if error is nil and data is nil, there must be an error HTTP response. Perhaps you're using the iOS 9 SDK and are getting tripped up by App Tranport Security. I do think you need to code more defensively there (check if data is nil, and check the HTTP response code).Anyway here's one big thing that won't work with that code: NSURLSession is an asynchronous API. The completion block has not yet been called (most likely the request hasn't even gone out) by the time you hit that code that's attempting to parse the result. It's like you asked your roommate to go to the store and get some beer and put it in the fridge, then immediately went to the fridge and tried to pour out a beer. It's just not there yet. You need to defer all that parsing stuff until after the result comes in (i.e. put it in a separate method and c
Jun ’15
Audio is not working.
Hi, I am trying to incoporate audio into an app that I'm making and I use the simulator to test but the second it gets on it goes back to the project screen with a line highlighted and a thread error below it sayingThread 1:EXC_BAD_INSTRUCTION(code=EXC_I386_INVOP,subcode=0x0)and another error in the debug area sayingfatal error: unexpectedly found nil while unwrapping an Optional value (lldb)The code i am using is this/ ViewController.swift *********************** Created by Marco Simonelli on 26/04/2015. Copyright (c) 2015 Antonio Enterprises. All rights reserved. */ import UIKit import AVFoundation class ViewController: UIViewController { var ButtonAudioURL = NSURL(fileURLWithPath: NSBundle.mainBundle().pathForResource(TURDY BIRD BACKGROUND T1 copy, ofType: wav)!) var ButtonAudioPlayer = AVAudioPlayer() override func viewDidLoad() { super.viewDidLoad() / ButtonAudioPlayer = AVAudioPlayer(contentsOfURL: ButtonAudioURL, error: nil) } override func didReceiveMemoryWarning() { super.didReceiveMemoryWar
3
0
1k
Jun ’15