Debugging

RSS for tag

Discover and resolve issues with your app.

Pinned Posts

Posts under Debugging tag

476 Posts
Sort by:
Post not yet marked as solved
2 Replies
2.2k Views
My application is currently crashing in production in iPhone devices running iOS 15.x. The app will work as normal while running developer mode, enterprise builds and Test Flight builds. Unfortunately, I am unable to reproduce this issue even app is downloaded from the app store. I observed crash is happening at main.m. Can someone help me to reproduce this issue? How to read this crash log file? Please find the crash log details attached. 2022-03-04_14-15-23.6227_+0900-a1899fd803a4ed683466702be71b9d224b4cd5bc.crash
Posted
by
Post not yet marked as solved
0 Replies
2.1k Views
General: DevForums tags: Debugging, LLDB, Graphical Debugger Xcode > Debugging documentation Diagnosing memory, thread, and crash issues early documentation Diagnosing issues using crash reports and device logs documentation Choosing a Network Debugging Tool documentation Testing a release build documentation Isolating Code Signing Problems from Build Problems DevForums post What is an exception? DevForums post Language Exception from RCTFatal DevForums post Standard Memory Debugging Tools DevForums post Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem DevForums post Posting a Crash Report DevForums post Implementing Your Own Crash Reporter DevForums post Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = "eskimo" + "1" + "@" + "apple.com"
Posted
by
Post not yet marked as solved
2 Replies
1.4k Views
I have created my first app with python using py2app and it build my app successfully but when I try to open it, it crash but when I open it's package and run it from this path: myapp.app/contents/macos/myapp it open console and run my app correctly without any error. I can't understand how to read this kind of mac errors. I will be happy if you can help me with that: Error Text
Posted
by
Post not yet marked as solved
7 Replies
939 Views
Hello, have some issues and wondering if someone here can help me out with this. I bought a max'd out Mac mini M1 (2TB SSD) and it turns out its a Dev/debug unit (not DTK). During boot the apple logo is huge and displays some text in the left bottom corner. Apple Internal - Version 11.0 (Build 20A2383) and stuff like "Current phase" First thing I did, I erased the SSD in recovery to install fresh macOS on it, and now I'm stuck. I cannot install any macOS through recovery because it offers only Big Sur and says its not available at this time. Long pressing the power button doesn't display the "Options" menu, it boots right into recovery, so I can't boot from USB and Apple Configurator fails with restore/revive and even trying manually with different macOS IPSWs. AC2 error is: The System cannot be restored on this device. The System install could not be authorized for this device. The build may not be approved for production installs. Any ideas what could I do to have it run macOS again?
Posted
by
Post marked as Apple Recommended
23k Views
Xcode13.4.1 is running properly, but after upgrading Xcode14, the debugging device reports an error: Library not loaded: / usr/lib/swift/libswiftCoreGraphics dylib, I according to the online solutions are tried, can't solve my problem, problem is ios10.3.3 equipment, unable to debug, also is unable to start the application success after packaging, Is this a problem with xcode14 itself?
Posted
by
Post not yet marked as solved
19 Replies
7k Views
Recently I updated to Xcode 14.0. I am building an iOS app to convert recorded audio into text. I got an exception while testing the application from the simulator(iOS 16.0). [SpeechFramework] -[SFSpeechRecognitionTask handleSpeechRecognitionDidFailWithError:]_block_invoke Ignoring subsequent recongition error: Error Domain=kAFAssistantErrorDomain Code=1101 "(null)" Error Domain=kAFAssistantErrorDomain Code=1107 "(null)" I have to know what does the error code means and why this error occurred.
Post not yet marked as solved
3 Replies
846 Views
esta es mi primera aplicacion que se publicara en la tienda, esta hecha con react native porque es el lenguaje que se usar, y porque necesitaba que fuera para compilar tanto para ios como para android. desde mayo que la subi siempre me la cancelan porque hay que afinar detalles, se lo hago y la reenvio pero ya la ultima no me dicen que debo hacerle para que la aprueben, solo me dicen que debo guiarme por varios lineamientos de apple me dan los link para leer las guias, pero no se mucho de aplicaciones moviles entonces este ultimo mensaje de apple es como decirme montate en este cohete prendido y manejado leyendo este manual de 2000 hojas, no se arreglar leyendo lo que no me dicen que debo buscar, les pongo el mensaje a ver si alguien de aca podria ayudarme porfavor esta app es una que me mandaron a hacer en mi oficina y me tienen presion que la termine "We are not able to provide feedback on app concepts or features, but we recommend evaluating your app against the App Store Review Guidelines, as well as the iOS Developer Program License Agreement (PLA), and the Human Interface Guidelines."
Posted
by
Post not yet marked as solved
3 Replies
2.7k Views
We are running into an issue where breakpoints are not resolving on Xcode 14 (The same break points on Xcode 13.4.1 are working fine). They change to an outline when we run our app I have tried all the usual fixes Cleaned the build Cleaned Derived data Restarted Xcode Restarted the machine Re-cloned the repo to see if starting fresh helps I have also tried Removing all symbol stripping Ensuring the DSYM is getting generated and is loaded in the debugger Removing all optimization options Tried the Xcode 14.1 beta What's really strange is the break points will work occasionally and will work for a few runs and then stop working again. Does anyone have any suggestions?
Posted
by
Post not yet marked as solved
14 Replies
3.7k Views
Hi, Our apps currently facing a crash that only happens in iPhone with iOS 16. Unfortunately, we could not reproduce this issue, neither from XCode build or App store build. From third party crash analytics, it happens mostly of background and they highlighted this as the issue. Fatal Exception: NSInvalidArgumentException *** -[__NSArrayM insertObject:atIndex:]: object cannot be nil And the stack trace, it shows: AVFCore __22-[AVPlayer _addLayer:]_block_invoke Pegasus __116-[PGPictureInPictureProxy _endDeactivatingPictureInPictureIfNeededWithAnimationType:stopReason:cleanupHandlerOrNil:]_block_invoke We also attach the full crash log to give full context of the crash. Any idea why this crash happens and is there anything i can do to prevent the crashes from happening again? pegasus.crash
Posted
by
Post not yet marked as solved
1 Replies
668 Views
I am getting random crash from time to time while using SwiftUI but i cannot find a way to get more context into the crash how to find the root cause? didn't even get more info while the crash happened while connected to XCode Version 14.1 (14B47b) OS Version: iPhone OS 16.1 (20B82) Release Type: User Report Version: 104 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x000000019a9edeb4 Termination Reason: SIGNAL 5 Trace/BPT trap: 5 Terminating Process: exc handler [45365] Triggered by Thread: 0 Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 SwiftUI 0x19a9edeb4 0x19a9c3000 + 175796 1 SwiftUI 0x19a9ede98 0x19a9c3000 + 175768 2 SwiftUI 0x19aa02da4 0x19a9c3000 + 261540 3 libswiftCore.dylib 0x1910dd138 Slice.index(after:) + 48 4 SwiftUI 0x19abd4d48 0x19a9c3000 + 2170184 5 SwiftUI 0x19ac16594 0x19a9c3000 + 2438548 6 libswiftCore.dylib 0x190f29678 BidirectionalCollection.index(_:offsetBy:) + 292 7 SwiftUI 0x19a9edd00 0x19a9c3000 + 175360 8 SwiftUI 0x19be30904 0x19a9c3000 + 21420292 9 SwiftUI 0x19bc2ffa8 0x19a9c3000 + 19320744 10 SwiftUI 0x19b7b1034 0x19a9c3000 + 14606388 11 SwiftUI 0x19b7afc20 0x19a9c3000 + 14601248 12 SwiftUI 0x19b7b21e4 0x19a9c3000 + 14610916 13 UIKitCore 0x1994e57d4 -[UICollectionView _selectItemAtIndexPath:animated:scrollPosition:notifyDelegate:deselectPrevious:performCustomSelectionAction:] + 1060 14 UIKitCore 0x1997314d4 -[UICollectionView touchesEnded:withEvent:] + 480 15 UIKitCore 0x1993e7514 forwardTouchMethod + 284 16 UIKitCore 0x1993e7514 forwardTouchMethod + 284 17 UIKitCore 0x1993e7514 forwardTouchMethod + 284 18 UIKitCore 0x1993e7514 forwardTouchMethod + 284 19 UIKitCore 0x1993185e0 _UIGestureEnvironmentUpdate + 5772 20 UIKitCore 0x199b9ce14 -[UIGestureEnvironment _deliverEvent:toGestureRecognizers:usingBlock:] + 288 21 UIKitCore 0x1992dc31c -[UIGestureEnvironment _updateForEvent:window:] + 188 22 UIKitCore 0x1992e0c74 -[UIWindow sendEvent:] + 3268 23 UIKitCore 0x1992dff44 -[UIApplication sendEvent:] + 672 24 UIKitCore 0x1992df600 __dispatchPreprocessedEventFromEventQueue + 7084 25 UIKitCore 0x1993273e4 __processEventQueue + 5632 26 UIKitCore 0x199f790a4 updateCycleEntry + 168 27 UIKitCore 0x199837740 _UIUpdateSequenceRun + 84 28 UIKitCore 0x199e7efd0 schedulerStepScheduledMainSection + 172 29 UIKitCore 0x199e7e19c runloopSourceCallback + 92 30 CoreFoundation 0x1970fdf54 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 31 CoreFoundation 0x19710a32c __CFRunLoopDoSource0 + 176 32 CoreFoundation 0x19708e210 __CFRunLoopDoSources0 + 244 33 CoreFoundation 0x1970a3ba8 __CFRunLoopRun + 836 34 CoreFoundation 0x1970a8ed4 CFRunLoopRunSpecific + 612 35 GraphicsServices 0x1cfb05368 GSEventRunModal + 164 36 UIKitCore 0x1995873d0 -[UIApplication _run] + 888 37 UIKitCore 0x199587034 UIApplicationMain + 340 38 libswiftUIKit.dylib 0x19fb73308 UIApplicationMain(_:_:_:_:) + 104 39 Fyzio Klinik Doctor 0x10445b2d8 static UIApplicationDelegate.main() + 104 40 Fyzio Klinik Doctor 0x10445b260 static AppDelegate.$main() + 44 41 Fyzio Klinik Doctor 0x10445b450 main + 28 42 dyld 0x1b5700960 start + 2528 Thread 1: 0 libsystem_pthread.dylib 0x1e370eb90 start_wqthread + 0
Posted
by
Post marked as solved
3 Replies
3.8k Views
Hello I have a problem with xCode, I have this error : Cannot find « string » in scope. Thank you so much for your help Photos: My code: // //  AuthviewModel.swift //  iSpeak // //  Created by Sayan on 21.11.22. // import Foundation import Firebase class AuthViewModel: ObservableObject {     var manager = FirebaseManager.shared          @Published var isFinishedConnecting: Bool = false     @Published var isAuth: Bool = false     @Published var showError: Bool = false          var errorString: String = ""     var datas: [String: Any] = [:]          var auth: Auth {         return manager.auth     }          init() {         observeAuthentication()     }          func observeAuthentication() {         auth.addStateDidChangeListener(handleChangeListener)     }          func handleChangeListener(auth: Auth, user: User?) {         self.isFinishedConnecting = true         self.isAuth = user != nil     }          func signIn(email: String, password: String) {         guard checkValue(_string: email, value: "adresse email") else { return }         guard checkValue(_string: password, value: "Mot de passe") else { return }              }          func createUser() {              }          func checkValue(_string: String, value: String) -> Bool {         let isNotEmpty = string != ""         self.errorString = !isNotEmpty ? "" : "Merci d'entrer (value) pour continuer"         self.showError = !isNotEmpty         return isNotEmpty     } }
Posted
by
Post marked as solved
8 Replies
12k Views
I  am completely at a loss here - I have a react native app created within expo. It runs perfectly well with expo go. I then built it using eas on my Mac (latest Ventura OS installed) and posted it to app store connect and installed it through TestFlight - it crashed immediately. I'm VERY new to this so it took me a long time to figure out how to troubleshoot this but I ended up finding this in the crash logs: Thread 2 name: Dispatch queue: com.facebook.react.ExceptionsManagerQueue Thread 2 Crashed: 0 libsystem_kernel.dylib 0x2076d8200 __pthread_kill + 8 1 libsystem_pthread.dylib 0x217b3a1ac pthread_kill + 268 2 libsystem_c.dylib 0x1d2111c8c abort + 180 3 libc++abi.dylib 0x217a7ab8c abort_message + 132 4 libc++abi.dylib 0x217a6aa80 demangling_terminate_handler() + 336 5 libobjc.A.dylib 0x1c3e11d3c _objc_terminate() + 144 6 libc++abi.dylib 0x217a79f28 std::__terminate(void (*)()) + 20 7 libc++abi.dylib 0x217a79ec4 std::terminate() + 56 8 libdispatch.dylib 0x1d20adff0 _dispatch_client_callout + 40 9 libdispatch.dylib 0x1d20b5694 _dispatch_lane_serial_drain + 672 10 libdispatch.dylib 0x1d20b61e0 _dispatch_lane_invoke + 384 11 libdispatch.dylib 0x1d20c0e10 _dispatch_workloop_worker_thread + 652 12 libsystem_pthread.dylib 0x217b33df8 _pthread_wqthread + 288 13 libsystem_pthread.dylib 0x217b33b98 start_wqthread + 8 And: Thread 2 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0x0000000217a7e0f5 x5: 0x000000016b4c6430 x6: 0x000000000000006e x7: 0xffffffff00000600 x8: 0xb1cfaa93a40be1da x9: 0xb1cfaa92cf4791da x10: 0x0000000000000200 x11: 0x000000000000000b x12: 0x000000000000000b x13: 0x00000000001ff800 x14: 0x00000000000007fb x15: 0x000000008c033819 x16: 0x0000000000000148 x17: 0x000000016b4c7000 x18: 0x0000000000000000 x19: 0x0000000000000006 x20: 0x0000000000001603 x21: 0x000000016b4c70e0 x22: 0x0000000000000000 x23: 0x000000016b4c70e0 x24: 0x0000000000000000 x25: 0x0000000280c888e8 x26: 0x0000000000000114 x27: 0x0000000000000000 x28: 0x0000000283787840 fp: 0x000000016b4c63a0 lr: 0x0000000217b3a1ac sp: 0x000000016b4c6380 pc: 0x00000002076d8200 cpsr: 0x40001000 far: 0x000000021e5abf50 esr: 0x56000080 Address size fault I  spent an entire day searching for causes surrounding these errors - there were references to this but nothing related to what I was doing. I then went back to the basics - literally: npx create-expo-app TestApp eas build:configure eas build --platform ios And loaded this into a simulator (downloaded the ipa file, changed it to a .zip file, transferred the app file to the simulator) and it immediately crashed again. I've used various versions of expo, node, eas cli, etc - all giving me the same results. I tried using ErrorUtils to send an error to my node server but that didn't work (I might have set it up wrong). I'm not sure how to proceed in troubleshooting this. It seems like the basic process of creating an expo app and having it installable in a simulator or an iPhone isn't working for me. I haven't used (nor do I know how to) Xcode much outside of using the simulators. Any help would be VERY MUCH appreciated.
Posted
by
Post not yet marked as solved
17 Replies
3.9k Views
Hi, I've recently experienced a weird crash that only happening on iOS 16 device (iOS 16.xx - 16.3). Here is the stack trace 0 libobjc.A.dylib 0x00000001bc11ae5c _objc_retain_x0 (in libobjc.A.dylib) + 16 1 UIKitCore 0x00000001c5c06a5c -[UIKeyboardTaskQueue promoteDeferredTaskIfIdle] (in UIKitCore) + 72 2 UIKitCore 0x00000001c5c069e8 -[UIKeyboardTaskQueue performDeferredTaskIfIdle] (in UIKitCore) + 28 3 UIKitCore 0x00000001c54039c8 -[UIKeyboardTaskQueue continueExecutionOnMainThread] (in UIKitCore) + 372 4 Foundation 0x00000001bd21484c ___NSThreadPerformPerform (in Foundation) + 260 5 CoreFoundation 0x00000001c2f31f30 ___CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ (in CoreFoundation) + 24 6 CoreFoundation 0x00000001c2f3e308 ___CFRunLoopDoSource0 (in CoreFoundation) + 172 7 CoreFoundation 0x00000001c2ec222c ___CFRunLoopDoSources0 (in CoreFoundation) + 336 8 CoreFoundation 0x00000001c2ed7b88 ___CFRunLoopRun (in CoreFoundation) + 832 9 CoreFoundation 0x00000001c2edcebc _CFRunLoopRunSpecific (in CoreFoundation) + 608 10 GraphicsServices 0x00000001fcf33364 _GSEventRunModal (in GraphicsServices) + 160 11 UIKitCore 0x00000001c53d2868 -[UIApplication _run] (in UIKitCore) + 884 12 UIKitCore 0x00000001c53d24cc _UIApplicationMain (in UIKitCore) + 336 13 News 0x00000001106d5d1c main (in News) (main.m:23) 14 dyld 0x00000001e16fe95c start (in dyld) + 2524
Posted
by
Post not yet marked as solved
12 Replies
2.4k Views
Doesn't seem to make much sense. I'm toying around with a SpriteKit project that hasn't gotten very far off the ground I noticed this in the error log: EXEC_BAD_ACCESS Any ideas?.. Apple doesn't make it easy to teach yourself dev on this this platform. Let's not even start about the documentation ...
Posted
by
Post not yet marked as solved
3 Replies
855 Views
Hi, I am trying to fix one of the crash coming on the App, I am attaching the Main thread Stack trace, Google search is also not giving any result, if anyone has faced the similar issue, or knew about it, can you help me in understanding the issue. 0 CoreGraphics                  0x179c CGColorSpaceIsUncalibrated + 4 1 QuartzCore                    0x8f410 CARequiresColorMatching + 64 2 QuartzCore                    0xf1614 CA_CGColorGetRGBComponents + 68 3 QuartzCore                    0x20098 -[NSObject(CAAnimatableValue) CA_interpolateValue:byFraction:] + 140 4 QuartzCore                    0x1c608 -[CABasicAnimation applyForTime:presentationObject:modelObject:] + 420 5 QuartzCore                    0x1c35c CA::Layer::presentation_layer(CA::Transaction*) + 428 6 UIKitCore                     0xe944 -[UIViewSpringAnimationState animationForLayer:forKey:forView:] + 136 7 UIKitCore                     0xdbe0 -[UIViewAnimationState actionForLayer:forKey:forView:] + 104 8 UIKitCore                     0xda64 +[UIView(Animation) _defaultUIViewActionForLayer:forKey:] + 92 9 UIKitCore                     0xd128 -[UIView(UIKitManual) actionForLayer:forKey:] + 308 10 QuartzCore                    0xad44 -[CALayer actionForKey:] + 148 11 QuartzCore                    0xabb8 CA::Layer::begin_change(CA::Transaction*, unsigned int, objc_object*, objc_object*&) + 212 12 QuartzCore                    0x130bc CA::Layer::setter(unsigned int, _CAValueType, void const*) + 812 13 QuartzCore                    0xd9c4 -[CALayer setBackgroundColor:] + 56 14 UIKitCore                     0x6b64c -[UIView _setBackgroundCGColor:withSystemColorName:] + 1036 15 UIKitCore                     0x6addc -[UIView _effectiveThemeTraitCollectionDidChangeInternal:] + 472 16 UIKitCore                     0x5f1a4 -[UIView _tintColorDidChange] + 208 17 UIKitCore                     0x5f00c -[_UITintColorVisitor _visitView:] + 312 18 UIKitCore                     0x5ed80 _UIViewVisitorRecursivelyEntertainDescendingVisitors + 220 19 UIKitCore                     0x5ee28 _UIViewVisitorRecursivelyEntertainDescendingVisitors + 388 20 UIKitCore                     0x5ee28 _UIViewVisitorRecursivelyEntertainDescendingVisitors + 388 21 UIKitCore                     0x5ee28 _UIViewVisitorRecursivelyEntertainDescendingVisitors + 388 22 UIKitCore                     0x5ee28 _UIViewVisitorRecursivelyEntertainDescendingVisitors + 388 23 UIKitCore                     0x5ee28 _UIViewVisitorRecursivelyEntertainDescendingVisitors + 388 24 UIKitCore                     0x5ee28 _UIViewVisitorRecursivelyEntertainDescendingVisitors + 388 25 UIKitCore                     0x5ee28 _UIViewVisitorRecursivelyEntertainDescendingVisitors + 388 26 UIKitCore                     0x5ee28 _UIViewVisitorRecursivelyEntertainDescendingVisitors + 388 27 UIKitCore                     0xee410 +[_UIViewVisitor _startTraversalOfVisitor:withView:] + 196 28 UIKitCore                     0x13ff94 -[UIView _dispatchTintColorVisitorWithReasons:] + 124 29 UIKitCore                     0x34aba8 -[UIView _beginOcclusion:] + 164 30 UIKitCore                     0x34a9fc -[UIPresentationController _enableOcclusion:] + 188 31 UIKitCore                     0x34a8b4 -[_UIViewControllerTransitionCoordinator _applyBlocks:releaseBlocks:] + 240 32 UIKitCore                     0x34a78c -[_UIViewControllerTransitionContext __runAlongsideAnimations] + 272 33 UIKitCore                     0x34a660 __63+[UIView(Animation) _setAlongsideAnimations:toRunByEndOfBlock:]_block_invoke + 36 34 UIKitCore                     0xd25a4 -[UIViewAnimationState _runAlongsideAnimations] + 40 35 UIKitCore                     0xd12e8 -[UIViewAnimationState pop] + 40 36 UIKitCore                     0xd0d14 +[UIViewAnimationState popAnimationState] + 56 37 UIKitCore                     0xd0b40 +[UIView _setupAnimationWithDuration:delay:view:options:factory:animations:start:animationStateGenerator:completion:] + 592 38 UIKitCore                     0x48e370 +[UIView(UIViewAnimationWithBlocks) animateWithDuration:delay:usingSpringWithDamping:initialSpringVelocity:options:animations:completion:] + 124 39 UIKitCore                     0x3e9098 -[UIAlertControllerVisualStyleAlert animateAlertControllerView:ofAlertController:forPresentation:inContainerView:descendantOfContainerView:duration:completionBlock:] + 580 40 UIKitCore                     0x3e8be8 -[_UIAlertControllerAnimatedTransitioning _animateTransition:completionBlock:] + 456 41 UIKitCore                     0x570a6c -[_UIAlertControllerAnimatedTransitioning animateTransition:] + 412 42 UIKitCore                     0x7f765c ___UIViewControllerTransitioningRunCustomTransition_block_invoke_3 + 48 43 UIKitCore                     0x206614 +[UIKeyboardSceneDelegate _pinInputViewsForKeyboardSceneDelegate:onBehalfOfResponder:duringBlock:] + 96 44 UIKitCore                     0x2b6db0 ___UIViewControllerTransitioningRunCustomTransition_block_invoke_2 + 196 45 UIKitCore                     0x1f7e4c +[UIView(Animation) _setAlongsideAnimations:toRunByEndOfBlock:] + 180 46 UIKitCore                     0x1f7d08 _UIViewControllerTransitioningRunCustomTransition + 484 47 UIKitCore                     0x762078 __56-[UIPresentationController runTransitionForCurrentState]_block_invoke_3 + 1532 48 UIKitCore                     0x1a4958 -[_UIAfterCACommitBlock run] + 72 49 UIKitCore                     0x1a488c -[_UIAfterCACommitQueue flush] + 176 50 UIKitCore                     0x1a4798 _runAfterCACommitDeferredBlocks + 496 51 UIKitCore                     0x3f6c0 _cleanUpAfterCAFlushAndRunDeferredBlocks + 108 52 UIKitCore                     0x504fc4 _UIApplicationFlushCATransaction + 72 53 UIKitCore                     0x651678 _UIUpdateSequenceRun + 84 54 UIKitCore                     0xc90904 schedulerStepScheduledMainSection + 172 55 UIKitCore                     0xc8fad0 runloopSourceCallback + 92 56 CoreFoundation                0xd622c CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 28 57 CoreFoundation                0xe2614 __CFRunLoopDoSource0 + 176 58 CoreFoundation                0x6651c __CFRunLoopDoSources0 + 244 59 CoreFoundation                0x7beb8 __CFRunLoopRun + 836 60 CoreFoundation                0x811e4 CFRunLoopRunSpecific + 612 61 GraphicsServices              0x1368 GSEventRunModal + 164 62 UIKitCore                     0x3a2d88 -[UIApplication _run] + 888 63 UIKitCore                     0x3a29ec UIApplicationMain + 340 64 PS Express                    0x28490 main + 34 (main.m:34) 65 ???                           0x1c6bc5948 (Missing)
Posted
by
Post not yet marked as solved
1 Replies
1.3k Views
Would someone please be able to explain to me what companion link is and how it may have become enabled on my device ? Would be greatly appreciated Terminusd-395.60.3 pid 1307 built on Dec 17 2022 04:33:51, iphoneOS 20D47 "🙈", packet logging disabled Companion link is currently enabled on this device 20:39:52.3305 : time of this status dump --------- NRD Local Device Database Status (0 devices) --------- --------- Director status --------- Name: Link Director Enabled: YES Fixed Interface mode: NO SOCKS port: 62742 SOCKS server: (null) FD Usage: { NETPOLICY = 2; Total = 6; VNODE = 4; } Unlocked data protection: ClassA --------- Manager status --------- Name: Policy Session Manager Policy Session: { priority = control1 policies = {} } Installed policies: { "NRLinkDirector-Drop" = ( 1 ); } Name: Link Manager - Bluetooth LinkManager type: Bluetooth State: Ready [] Links: {( )} Pipes: {( )} Peripherals: (null) CentralMgr: (null) PeripheralMgr: (null) currentAdvertisementState: Idle currentAdvertisementRate: Default Name: Link Manager - WiFi LinkManager type: WiFi State: Ready Links: {( )} WiFi Interface: en0 (index 16) AWDL Interface: (null) (index 0) WiFi Available: YES WiFi WoW Enabled: NO WiFi Client Type: 0 Local WiFi Endpoint: 192.168.1.124:0 Local WiFi Signature: (null) Remote WiFi Endpoints: { } Remote WiFi Signature: (null) Remote AWDL EndpointDict: { } Available IPv4 addresses: ( "192.168.1.124" ) Available IPv6 addresses: ( ) Available AWDL addresses: ( ) Prefer WiFi asserts: 0 Cleared Prefer WiFi asserts: 0 Orphaned Device Monitor Connections: {( )} Orphaned Device Preferences Connections: {( )} Ephemeral Device Connections: {( )}
Posted
by
Post not yet marked as solved
2 Replies
2.8k Views
Hi there, Currently having some issues debugging on a physical device. I am running a flutter app, and have a provisioning profile provided by our client company that is not expired and has worked up until recently just fine with physical devices. Running the app on a simulator works okay as well. However, all of the sudden the app will not run on a physical device. The build succeeds fine, but then I receive the error "Unable to install runner: A valid provisioning profile for this executable was not found". I have opened devices and simulators and tried to install the provisioning profile on the device, but get the error "Failed to install one or more provisioning profiles on the device: Please ensure the provisioning profile is configured for this device. If not, please try to generate a new profile." I don't know why this error appears, because I have used this exact profile on this device many times before. I'm hesitant to contact the client to receive a new provisioning profile because it is not easy to do, and again this one has worked fine until now. Does anyone have any ideas? Thanks!
Posted
by
Post not yet marked as solved
3 Replies
1.3k Views
I received the attached crash report. The problem is that the crash report does not contain the abort reason - it appears to be thrown in the GCD library with no additional information. Is it a possible deadlock? 2023-02-15_02-40-23.0077_+0100-94015bd052c4005658221a5e6279f28a75b9e92c.crash Any ideas?
Posted
by
Post not yet marked as solved
1 Replies
1.2k Views
I'm experiencing a weird issue on iOS16. There is no code change, it works fine on lower OS versions. The stack traces are: The first case: Crashed: com.apple.main-thread EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x00000000e5bde410 0 libobjc.A.dylib objc_release_x21 + 16 1 CoreData -[_PFManagedObjectReferenceQueue _processReferenceQueue:] + 1020 2 CoreData -[NSManagedObjectContext _processRecentChanges:] + 112 3 CoreData _performRunLoopAction + 412 4 CoreFoundation __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36 5 CoreFoundation __CFRunLoopDoObservers + 532 6 CoreFoundation __CFRunLoopRun + 1048 7 CoreFoundation CFRunLoopRunSpecific + 612 8 GraphicsServices GSEventRunModal + 164 9 UIKitCore -[UIApplication _run] + 888 10 UIKitCore UIApplicationMain + 340 The second case, I believe this stack trace has the same root cause as the previous one (same trend, same UI page, only happens on iOS 16). Crashed: com.apple.main-thread EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0033003200390070 0 libobjc.A.dylib objc_msgSend + 32 1 CoreFoundation -[__NSArrayM dealloc] + 188 2 MyApplication MyClass.m - Line 361 -[MyClass loadMessages:] + 361 3 MyApplication MyClass.m - Line 125 __74-[MyClass requestRecentMessagesAndDiscardExistingMessagesCompletion:]_block_invoke + 125 4 libdispatch.dylib _dispatch_call_block_and_release + 32 5 libdispatch.dylib _dispatch_client_callout + 20 6 libdispatch.dylib _dispatch_main_queue_drain + 928 7 libdispatch.dylib _dispatch_main_queue_callback_4CF + 44 8 CoreFoundation __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16 9 CoreFoundation __CFRunLoopRun + 2036 10 CoreFoundation CFRunLoopRunSpecific + 612 11 GraphicsServices GSEventRunModal + 164 12 UIKitCore -[UIApplication _run] + 888 13 UIKitCore UIApplicationMain + 340 MyClass.m is an Objective-C class, it has a property: @property (nonatomic, strong) NSArray<Message *> *messages; // Message is NSManagedObject In the second stacktrace, frame -[OurClass loadMessages:] + 361, the messages array is deallocated: self.messages = [[NSArray alloc] init...]; So my guess is, somehow the messages are over-released. If the messages are released in MyClass before, then the crash happens as the first stack trace, otherwise, it happens as the second stack trace. I've turned on -com.apple.CoreData.ConcurrencyDebug 1 to try to find out the concurrency issues and fixed them, but no luck. Any help would be much appreciated. Thanks in advance!
Posted
by
Post not yet marked as solved
1 Replies
597 Views
I'm not able to inspect WeatherKit objects like HourWeather and CurrentWeather using the Xcode debugger and breakpoints. When I pause on a breakpoint and try something like po hours where hours is a [HourWeather] I get a debugger error like Couldn't lookup symbols: type metadata accessor for WeatherKit.HourWeather. Is there something about WeatherKit that prevents the debugger from printing out its objects?
Posted
by