Sorry if this thread is in the wrong forum. Couldn't find a suitable one.I've added a new UITest target, running it in a 9.0 simulator..The app runs, but when I hit my first button, I get this when I'm trying to record my suite.[UITextEffectsWindow _adjustPointForHostedDisplay:hasTarget:inset:]: unrecognized selector sent to instance
Search results for
LLDB crash
29,559 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Interesting. Yeah, that's really weird. Have you checked out the Zombie Objects or Address Sanitizer features? They might be able to help you pinpoint your problem. Both are accessible when you edit your scheme, head to the Run action and click on the Diagnostics tab. After enabling them, run your app. Now when it crashes, you'll get a detailed readout on what went wrong.Say, did you check to see if anything was wrong with your source file? Take a look in the File Inspector. Maybe also create another Swift file with a function in it that does the same thing as your setup code, and call that function from your original file. Other than that, I'm just as stumped as you are.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Recently released a test flight build for the Apple Watch app. However, that is now crashing with the below crash log on the iPhone.. Thing to note is that the previous build did not crash.iPhone is 6+ with iOS 8.3 (12F70) and Apple Watch is version 1.0 (12S507)Apple Watch crash pastebin
I do not have any third-party plug-ins and Xcode still crashes with the same error.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Well I've narrowed things down, and it does have to do with turning my watch app into 3 pages. Apparently this line is what makes it crash, even though the CLLocation line is what's being highlighted.let settingsVC = SettingsScreenInterfaceController()That would be my settings page, where I've moved some variables I need to check back in my main IC. I normally use the AppDelegate in the iOS to store variables I'll be using across VCs, but that's not available in the Apple Watch extension. How is one supposed to share variables between ICs in Apple Watch? I clearly must be doing something wrong!
Topic:
App & System Services
SubTopic:
Core OS
Tags:
We have a serious issue while deploying our product to the ipad. Our network will not allow to access internet. While the application deployed to the ipad and connect to the local network, the application takes few seconds/minutes for popup and the crashed immediately.Could anybody have this issue please help me to find a solution.Our WiFi is enabled only for internal network accessSTEPS TO REPRODUCE1. Fresh installation of ipad2. Installed our application3. Wiifi is without internet4. Started the app and it crashes crash contains error Failed tolaunch in TimePLATFORM AND VERSIONiOS 7.1, iOS 8.1 etcIpad Mini, Ipad AirThanks & Regards,Celus berchmans OlayamPhone : +81-80-4801-6547
Since iOS8.4 release, KooTV app received lots of crash report which doesn't appears before.KooTV app use MPMoviePlayerController to play stream HLS.Here is the crash stack information, it there any one crash like this?An AVPlayerItem cannot be associated with more than one instance of AVPlayer (null) ( 0 CoreFoundation 0x0000000184fc02f4 <redacted> + 160 1 libobjc.A.dylib 0x0000000196c8c0e4 objc_exception_throw + 60 2 AVFoundation 0x0000000183794b50 <redacted> + 0 3 AVFoundation 0x0000000183787770 <redacted> + 260 4 AVFoundation 0x00000001837a8f00 <redacted> + 156 5 MediaPlayer 0x00000001873b1d30 <redacted> + 72 6 MediaPlayer 0x000000018731de7c <redacted> + 1396 7 MediaPlayer 0x000000018731d8a4 <redacted> + 1452 8 MediaPlayer 0x000000018731f2fc <redacted> + 36 9 libdispatch.dylib 0x0000000197309994 <redacted> + 24 10 libdispatch.dylib 0x0000000197309954 <redacted> + 16 11 libdispatch.dylib 0x000000019730e20c _dispatch_main_
I'm trying to create a type similar to Array<U>, except that it's indexed by a type T other than Int. To reduce the complexity of the (envisioned) implementation, I planned to use an underlying (sparse array) [U?] variable, and to require T to be RawRepresentible so that its raw values can be used to index the underlying array. This should work well with the intended use case, where T is an 'enum E: Int' type whose cases are sequentially assigned, more or less.However, I can't find a way of writing the type so that it satisfies CollectionType. I don't know how to fix the compiler errors in the following attempted implementation, and it's made triply hard by the fact that this code pretty much crashes SourceKit and the compiler itself (with a segmentation fault: 11). I'm open to any suggestions about how to make this compile, or alternate techniques to achieve approximately the same effect.public struct EnumeratedArrayGenerator<T: RawRepresentable, U>: GeneratorType { public mutating func
This is the cause apparently:Application Specific Information:*** -[NSKeyedUnarchiver initForReadingWithData:]: incomprehensible archive version (-1)abort() calledThat error also crashes GraphicConverter:terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSKeyedUnarchiver initForReadingWithData:]: incomprehensible archive version (-1)'Using FCP X 10.2.1, OSX 10.11 (15A204h), GraphicConverter 9.6.1 & 9.7.2030
Topic:
App & System Services
SubTopic:
Core OS
Tags:
App in debug mode is no any problem but release app is crash in iOS 6 and iOS 7 but there is no problem in iOS 8.We try update many version fix all 'possible' problem, but still crash.My app name is '日盛銀行' and download address is below :日盛銀行 的 日盛銀行https://appsto.re/tw/-EqlF.i
I need to get to a crash log of my iPhone to update a bug report as per https://developer.apple.com/bug-reporting/ios/crash/~Library/Logs/CrashReporter/MobileDeviceBut this path doesn't exist in El Capitan. I'm wondering where it's been moved to. I've synced my iPhone via iTunes already.
Do we have -x like option in lldb, which help us to pass set of lldb command in a file. i know about python scripting in lldb but i am looking for -x like option in lldb which could allow me not to write a python script . Exampleif i do following#lldb(lldb)process attach -n CoRD(lldb)breakpoint set -n tcp_connect(lldb)breakpoint set -n tcp_send(lldb) cthen script test should contain above command in lldb context and should be passed as something like#lldb -x testand it should execute all command from process attach to cis there exists something like this?
Same here... First WatchOS2 beta install here, no apps deployed, just wearing it after install noticed screen went dark. Holding down side button to restart doesn't do anything. It just keeps randomly rebooting, works for a little while inbetween. Putting it on the charger then seems to let it recover. Tried connecting to it via xcode to see if there were any crash logs, but there don't seem to be any. Not sure if that's being hidden from us? Can only Apple tech see the system crash logs, and we can only see our app crash logs? I'm new to this microcosm as you can tell.
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I've been using Xcode 6.3 with El Capitan since El Capitan was released. I updated my Mac yesterday and it said that Xcode 6.3 isnt compatible with this version of OS X, i then downloaded Xcode 6.4 from the Mac App Store and the same thing happens.I then downloaded Xcode 7 beta 2 but it crashes everytime i open it.
Hi,I experienced exactly the same issue after upgrading my phone to 8.4.The watchkit app does start the parent app but unfortunately the iPhone app crashes while performing application:handleWatchKitExtensionRequest: . I analyzed the issue and came to the conclusion that iOS 8.4 no longer calls application:didFinishLaunchingWithOptions: before an initial watchkit extension request. Have a look at https://forums.developer.apple.com/message/19850#19850 which details everything.In my case, we did 3rd party lib initializations in the application:didFinishLaunchingWithOptions: . As a workaround, I extracted the initialization into an extra method. Whenever application:handleWatchKitExtensionRequest: is called, I make sure that the initialization was completed before.Hope this helps!
Topic:
App & System Services
SubTopic:
General
Tags: