Hi, I am encountering an issue with my app when installing it via TestFlight. Specifically, the app crashes during installation or launch through TestFlight, but I do not experience this problem when running the app in release or debug mode within Xcode. App Name: Flash Service - Clients UserApp-2024-07-09-124244.txt you can check that as well in image and file which i get from Phone Setting Analytics

JSC::MarkedBlock::aboutToMarkSlow(unsigned int) + 88 check iOS crash reports by xcode. However, it still cannot identify the specific line

We are developing an Xcframework that contains Objc + Cpp code. Cpp code is internal to the framework so we are stripping all the symbols. Framework is using few build options to strip off internal symbols: Build PostProcessing - Yes Strip Style - Non-Global Symbols Other Cpp flags - $(OTHER_CFLAGS) -fvisibility-inlines-hidden -fvisibility=hidden Now when a crash happens due to "abort()" function, the topmost symbol (of the framework) is symbolicated to totally different method. But if crash happens due to some other reason, then symbolication works fine. We have tried atos command as well as Mac symbolicator. Both show same behaviour. To explain the issue in more details, here is a GitHub link. It contains all the details on how to reproduce the issue. Build settings are similar to our project settings. https://github.com/bmahajanZ/apple-build-issue

so im testing my app on testflight and i have this update button that will redirect me to the appstore, so i click that then i'll be redirected to appstore and my app on appstore will show this install icon that will let me install the current app on my appstore so then ill install it then when i open it, it crashes and upon checking my console on my mac these are the errors im getting: Error: Cannot make a deep link into a standalone app with no custom scheme defined, js engine: hermes Unhandled JS Exception: Error: Cannot make a deep link into a standalone app with no custom scheme defined, js engine: hermes I tried to debug it on my npx expo start -c, at first im getting the same error but then ive managed to removed it so im confident that it will work, but then it still crashes

Hello, I have an iOS app for which I've received a number of similar crash reports over the last few months. Despite a lot of effort, I haven't been able to replicate the crash myself and I'm finding it difficult to diagnose. The main view of the app loads a list of items from Core Data using @FetchRequest and looking at the logs it appears to me that this is the most likely source of the crash as the call stack includes SwiftUI 0x19c78c368 FetchRequest.update() + 472 (FetchRequest.swift:406). It also appears as if this happens on launch as the crash times and launch times are always very similar. I've attempted lots of things to try and replicate the crash, such as launching the app a lot of times, creating lots of items so that the fetch request has a lot of data to retrieve, performing any other database related actions in the app immediately after launch to try and drive out any concurrency issues and simulating degraded thermal and network conditions for the device. I've included a sample crash report, I'd be very grateful if anyone has any suggestions for diagnosing the issue. Crash Report

I'm working on a mobile app that keeps crashing on launch since updating to iOS 18 Beta 3 and 4. The splash screen is shown and afterwards the app is crashing. The stack trace is very general and it's very hard to pinpoint where it's going wrong. Does someone experience the same behavior? The app was working on iOS 18 Beta 2. In the stack trace you can see that is goes wrong at OurObject. This is an object that inherits from UIStackView. Background information .NET8.0 iOS MVVMCross Stacktrace 2024-07-24 09:29:05.110 ***.iOS[9804:731403] Unhandled managed exception: Objective-C exception thrown. Name: NSInvalidArgumentException Reason: -[OurObject initWithCoder:]: unrecognized selector sent to instance 0x300bb2ec0 Native stack trace: 0 CoreFoundation 0x000000019f0ba098 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 540824 1 libobjc.A.dylib 0x000000019c3c2698 objc_exception_throw + 76 2 CoreFoundation 0x000000019f1bf810 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 1611792 3 CoreFoundation 0x000000019f057728 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 137000 4 CoreFoundation 0x000000019f057050 _CF_forwarding_prep_0 + 96 5 UIKitCore 0x00000001a1b89308 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 3756808 6 UIFoundation 0x00000001aab3af30 D893DC98-0766-3DA9-BDD8-73614C11B808 + 81712 7 UIFoundation 0x00000001aab3ab84 D893DC98-0766-3DA9-BDD8-73614C11B808 + 80772 8 UIKitCore 0x00000001a1b85ec4 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 3743428 9 UIFoundation 0x00000001aab3af30 D893DC98-0766-3DA9-BDD8-73614C11B808 + 81712 10 UIFoundation 0x00000001aab3b0bc D893DC98-0766-3DA9-BDD8-73614C11B808 + 82108 11 UIFoundation 0x00000001aab3ab84 D893DC98-0766-3DA9-BDD8-73614C11B808 + 80772 12 UIKitCore 0x00000001a1b894b4 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 3757236 13 UIKitCore 0x00000001a1c6aa48 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 4680264 14 UIKitCore 0x00000001a19836c4 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 1636036 15 UIKitCore 0x00000001a184c49c D2E47210-1C46-3CA7-BBC2-35021B146A13 + 361628 16 UIKitCore 0x00000001a226c7a8 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 10979240 17 UIKitCore 0x00000001a226cc20 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 10980384 18 UIKitCore 0x00000001a2a5baa0 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 19298976 19 UIKitCore 0x00000001a194b590 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 1406352 20 UIKitCore 0x00000001a1bf2ab4 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 4188852 21 UIKitCore 0x00000001a18047b4 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 67508 22 QuartzCore 0x00000001a0b3a6d8 EC26DDF2-2731-3CF2-A310-543557961180 + 489176 23 QuartzCore 0x00000001a0b3a264 EC26DDF2-2731-3CF2-A310-543557961180 + 488036 24 QuartzCore 0x00000001a0b92edc EC26DDF2-2731-3CF2-A310-543557961180 + 851676 25 QuartzCore 0x00000001a0b10560 EC26DDF2-2731-3CF2-A310-543557961180 + 316768 26 UIKitCore 0x00000001a19a95f0 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 1791472 27 CoreFoundation 0x000000019f09c218 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 418328 28 CoreFoundation 0x000000019f08a4c0 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 345280 29 CoreFoundation 0x000000019f089b84 7AD2298D-5B8F-3AF4-9EED-B09B8E0A9653 + 342916 30 CoreFoundation 0x000000019f089368 CFRunLoopRunSpecific + 572 31 GraphicsServices 0x00000001eb27c1c4 GSEventRunModal + 164 32 UIKitCore 0x00000001a1bd69b0 D2E47210-1C46-3CA7-BBC2-35021B146A13 + 4073904 33 UIKitCore 0x00000001a1c84d54 UIApplicationMain + 340 34 ***.iOS 0x0000000102fdc5f4 xamarin_UIApplicationMain + 60 35 ***.iOS 0x000000010332f340 do_icall + 316 36 ***.iOS 0x000000010332dc40 do_icall_wrapper + 348 37 ***.iOS 0x000000010332264c mono_interp_exec_method + 2784 38 ***.iOS 0x0000000103320218 interp_runtime_invoke + 236 39 ***.iOS 0x00000001032eee9c mono_jit_runtime_invoke + 1116 40 ***.iOS 0x0000000103296600 mono_runtime_invoke_checked + 148 41 ***.iOS 0x000000010329c8fc mono_runtime_exec_main_checked + 116 42 ***.iOS 0x00000001032f449c mono_jit_exec + 356 43 ***.iOS 0x0000000103008ffc xamarin_main + 2336 44 ***.iOS 0x00000001033e7874 main + 64 45 dyld 0x00000001c52c4734 94AF19E0-4F2A-332F-A08C-04B9B7CB6FAC + 210740 (ObjCRuntime.ObjCException) at ObjCRuntime.Runtime.ThrowException(IntPtr gchandle) in /Users/builder/azdo/_work/1/s/xamarin-macios/src/ObjCRuntime/Runtime.cs:line 2594 at UIKit.UIApplication.UIApplicationMain(Int32 argc, String[] argv, IntPtr principalClassName, IntPtr delegateClassName) in /Users/builder/azdo/_work/1/s/xamarin-macios/src/UIKit/UIApplication.cs:line 60 at UIKit.UIApplication.Main(String[] args, Type principalClass, Type delegateClass) in /Users/builder/azdo/_work/1/s/xamarin-macios/src/UIKit/UIApplication.cs:line 94 at ***.iOS.Application.Main(String[] args) in /Users/***/***/***/sources/iOS/Main.cs:line 7 Question for the administrators: Can you remove my previous post from July 16?

I have had a suspicious crash in my app for a long time. I'm 95% using SwiftUI and have to use only one UIKit view that I embed into SwiftUI in my app. I don't understand why my app crashes when the CALayer position is set to Nan because I don't reference layers at all, including that UIKit view. Any ideas why it may happen and how can I reproduce it? Fatal Exception: CALayerInvalidGeometry CALayer position contains NaN: [nan nan]. Layer: <CAShapeLayer:0x303cd9600; position = CGPoint (0 0); bounds = CGRect (0 0; 0 0); delegate = _NoAnimationDelegate; allowsGroupOpacity = YES; anchorPoint = CGPoint (0 0); > Fatal Exception: CALayerInvalidGeometry 0 CoreFoundation 0x83f20 __exceptionPreprocess 1 libobjc.A.dylib 0x16018 objc_exception_throw 2 CoreFoundation 0x1826dc -[NSException initWithCoder:] 3 QuartzCore 0x7b28 CA::Layer::set_position(CA::Vec2<double> const&, bool) 4 QuartzCore 0x7a58 -[CALayer setPosition:] 5 SwiftUI 0x1a131d4 objectdestroy.10Tm 6 SwiftUI 0x1a12ab4 objectdestroy.10Tm 7 SwiftUI 0x281590 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 8 SwiftUI 0x280c0c -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 9 SwiftUI 0x28083c -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 10 SwiftUI 0x27eaf8 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 11 SwiftUI 0x27e2c0 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 12 SwiftUI 0x27c6b0 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 13 SwiftUI 0x27bba8 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 14 SwiftUI 0x27c480 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 15 SwiftUI 0x27bba8 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 16 SwiftUI 0x27c480 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 17 SwiftUI 0x27bba8 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 18 SwiftUI 0x27c480 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 19 SwiftUI 0x27bba8 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 20 SwiftUI 0x27e408 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 21 SwiftUI 0x27c6b0 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 22 SwiftUI 0x27bba8 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 23 SwiftUI 0x27c480 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 24 SwiftUI 0x27bba8 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 25 SwiftUI 0x1a34a8 get_witness_table 7SwiftUI4ViewRzAA7GestureRd__r__lAA15ModifiedContentVyxAA03AddD8ModifierVyqd__GGAaBHPxAaBHD1__AhA0cH0HPyHCHCTm 26 SwiftUI 0x1a323c get_witness_table 7SwiftUI4ViewRzAA7GestureRd__r__lAA15ModifiedContentVyxAA03AddD8ModifierVyqd__GGAaBHPxAaBHD1__AhA0cH0HPyHCHCTm 27 SwiftUI 0x1a2c54 get_witness_table 7SwiftUI4ViewRzAA7GestureRd__r__lAA15ModifiedContentVyxAA03AddD8ModifierVyqd__GGAaBHPxAaBHD1__AhA0cH0HPyHCHCTm 28 SwiftUI 0x1a2ba4 get_witness_table 7SwiftUI4ViewRzAA7GestureRd__r__lAA15ModifiedContentVyxAA03AddD8ModifierVyqd__GGAaBHPxAaBHD1__AhA0cH0HPyHCHCTm 29 SwiftUI 0x1a2ab0 get_witness_table 7SwiftUI4ViewRzAA7GestureRd__r__lAA15ModifiedContentVyxAA03AddD8ModifierVyqd__GGAaBHPxAaBHD1__AhA0cH0HPyHCHCTm 30 SwiftUI 0x1a2a78 get_witness_table 7SwiftUI4ViewRzAA7GestureRd__r__lAA15ModifiedContentVyxAA03AddD8ModifierVyqd__GGAaBHPxAaBHD1__AhA0cH0HPyHCHCTm 31 SwiftUI 0x1a2a40 get_witness_table 7SwiftUI4ViewRzAA7GestureRd__r__lAA15ModifiedContentVyxAA03AddD8ModifierVyqd__GGAaBHPxAaBHD1__AhA0cH0HPyHCHCTm 32 SwiftUI 0x1a2930 get_witness_table 7SwiftUI4ViewRzAA7GestureRd__r__lAA15ModifiedContentVyxAA03AddD8ModifierVyqd__GGAaBHPxAaBHD1__AhA0cH0HPyHCHCTm 33 UIKitCore 0x95540 +[UIView(Animation) performWithoutAnimation:] 34 SwiftUI 0x2686ec -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 35 SwiftUI 0x2656d8 -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 36 SwiftUI 0x263d7c -[UIScrollView(SwiftUI) _swiftui_adjustsContentInsetWhenScrollDisabled] 37 SwiftUI 0x18eedc OUTLINED_FUNCTION_519 38 SwiftUI 0x18e8d8 OUTLINED_FUNCTION_519 39 SwiftUI 0x18e768 OUTLINED_FUNCTION_519 40 QuartzCore 0xd0ecc CA::Display::DisplayLinkItem::dispatch_(CA::SignPost::Interval<(CA::SignPost::CAEventCode)835322056>&) 41 QuartzCore 0xcf230 CA::Display::DisplayLink::dispatch_items(unsigned long long, unsigned long long, unsigned long long) 42 QuartzCore 0xcedd0 CA::Display::DisplayLink::dispatch_deferred_display_links(unsigned int) 43 UIKitCore 0xb776c _UIUpdateSequenceRun 44 UIKitCore 0xb73b0 schedulerStepScheduledMainSection 45 UIKitCore 0xb8254 runloopSourceCallback 46 CoreFoundation 0x56834 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ 47 CoreFoundation 0x567c8 __CFRunLoopDoSource0 48 CoreFoundation 0x54298 __CFRunLoopDoSources0 49 CoreFoundation 0x53484 __CFRunLoopRun 50 CoreFoundation 0x52cd8 CFRunLoopRunSpecific 51 GraphicsServices 0x11a8 GSEventRunModal 52 UIKitCore 0x40a90c -[UIApplication _run] 53 UIKitCore 0x4be9d0 UIApplicationMain 54 SwiftUI 0x3f4148 OUTLINED_FUNCTION_283 55 SwiftUI 0x3a0714 OUTLINED_FUNCTION_283 56 SwiftUI 0x3ac4d0 OUTLINED_FUNCTION_283 57 VerkadaPass 0xd1b4 main (MyApp.swift) 58 ??? 0x1ca1dde4c (Missing)

Hi Everyone, Our app crashes in real device with the following error but works in simulator. Please suggest. We are using iOS 17 in device and xcode 15.4 Date/Time: 2024-06-21 11:41:41.4618 -0500 Launch Time: 2024-06-21 11:41:41.1161 -0500 Release Type: User Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: DYLD 4 Symbol missing Symbol not found: _$s8SAPFiori27FUISegmentedControlFormCellC15reuseIdentifierSSvgZTj Referenced from: <05282F21-2C2D-3AE6-B45B-251164285297> /Volumes/VOLUME//AssetManagerVDP.app/Frameworks/MapFramework.framework/MapFramework Expected in: /Volumes/VOLUME//AssetManagerVDP.app/Frameworks/SAPFiori.framework/SAPFiori (terminated at launch; ignore backtrace) Triggered by Thread: 0 Thread 0 Crashed: 0 dyld 0x1b8275e90 __abort_with_payload + 8 1 dyld 0x1b827e0e4 abort_with_payload_wrapper_internal + 104 2 dyld 0x1b827e118 abort_with_payload + 16 3 dyld 0x1b823c70c dyld4::halt(char const*, dyld4::StructuredError const*) + 304 4 dyld 0x1b820

getting a Crash in crashlytics. However, the user's app on the device does NOT actually crash. Everything works as expected. Heres is the stack trace: Crashed: com.apple.main-thread 0 DigiDeals 0x33404 specialized Universal.displayMessages() + 4302730244 (:4302730244) 1 DigiDeals 0x32840 specialized Universal.displayMessages() + 453 (Universal.swift:453) 2 libswift_Concurrency.dylib 0x4d764 swift::runJobInEstablishedExecutorContext(swift::Job*) + 436 3 libswift_Concurrency.dylib 0x4e9c8 swift_job_runImpl(swift::Job*, swift::ExecutorRef) + 72 4 libdispatch.dylib 0x124b4 _dispatch_main_queue_drain + 748 5 libdispatch.dylib 0x121b8 _dispatch_main_queue_callback_4CF + 44 6 CoreFoundation 0x56710 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 16 7 CoreFoundation 0x53914 __CFRunLoopRun + 1996 8 CoreFoundation 0x52cd8 CFRunLoopRunSpecific + 608 9 GraphicsServices 0x11a8 GSEventRunModal + 164 10 UIKitCore 0x40a90c -[UIApplication _run] + 888 11 UIKitCore 0x4be9d0 UIApplicationMain + 340 12 UIKitCore 0x638384 keypath_get_selector_hoverStyle + 11024 13 DigiDeals 0x4aaf8 main + 4302826232 (AppDelegate.swift:4302826232) 14 ??? 0x1c2bd5e4c (Missing)

We have a crash regarding to Core Data access that was not reproducible in our side but the crash count keeps increasing with the last stack trace is assertionFailure from Apple internal SDK. The last stack trace before the assertionFailure by system is our code initializing CoreData in DataContainer.init(name:bundle:inMemory:) where we will try to access CoreData and the error message we found from our 3rd party crash reporter is something like this DataStore/DataContainer.swift:30: Fatal error: Unresolved error Error Domain=NSCocoaErrorDomain Code=256 "The file “Content.sqlite” couldn’t be opened. UserInfo={NSFilePath=/var/mobile/Containers/Data/Application/9DBF262C-851A-486B-90CC-4397A8896525/Library/Application Support/Content.sqlite, NSSQLiteErrorDomain=13}, ["NSSQLiteErrorDomain": 13, "NSFilePath": /var/mobile/Containers/Data/Application/9DBF262C-851A-486B-90CC-4397A8896525/Library/Application Support/Content.sqlite] That sqlite file is supposed to be file used by Core Data (since we have no other code that access it) and we are quite confused on why sometimes the CoreData cannot be accessed with that kind of error message. So far, we still have no idea to reproduce it and what do to resolve it. I have submitted the report with bug number: FB14433998 I attached an example of the crash report here too. Please gave us insight on why it happened and how we can prevent it from happening again. crash log 1.crash

i'm trying to get firefox running in 10.7 but the kernel is crashing. i have it working/running/looking great on 10.8 and higher. something is happening in 10.7 that is causing the panic. i need the right kit. someone asked a similar question for 10.11: https://forums.developer.apple.com/forums/thread/108732 but feedback assistant doesn't seem like the right answer. i need this kit to move forward. right now using either the 10.7.0 or 10.7.4 kernel debug kit causes a panic on reboot; something to do with AVX and the fpu. i am hoping APPUL had enough foresight to see this would be an issue (even one year later) for people on newer architectures debugging for older, supported (until 2014) targets: this use-case definitely falls within the parameters.

I had a problem that my app did not work outside Xcode (had to include the metalkit.framework I found a simple trick to get my NSLog outputs and locate the issue: NSURL *downloadsDirectory = [[[NSFileManager defaultManager] URLsForDirectory:NSDownloadsDirectory inDomains:NSUserDomainMask] firstObject]; NSURL *fileURL = [downloadsDirectory URLByAppendingPathComponent:@"Log.txt"]; NSString *filePath = [fileURL path]; // Redirect stderr to the file freopen([filePath fileSystemRepresentation], "a+", stderr); Now you get debug info in your Download folder!

I am using the Xcode visionOS debugging tool to visualize the bounds of all the containers, but it shows my Entity is inside the Volume. Then why does it get clipped? Is there something wrong with the debugger, or am I missing something? import SwiftUI @main struct RealityViewAttachmentApp: App { var body: some Scene { WindowGroup { ContentView() } .windowStyle(.volumetric) .defaultSize(Size3D(width: 1, height: 1, depth: 1), in: .meters) } } import SwiftUI import RealityKit import RealityKitContent struct ContentView: View { var body: some View { RealityView { content, attachments in if let earth = try? await Entity(named: "Scene", in: realityKitContentBundle) { content.add(earth) if let earthAttachment = attachments.entity(for: "earth_label") { earthAttachment.position = [0, -0.15, 0] earth.addChild(earthAttachment) } if let textAttachment = attachments.entity(for: "text_label") { textAttachment.position = [-0.5, 0, 0] earth.addChild(textAttachment) } } } attachments: { Attachment(id: "earth_label") { Text("Earth") } Attachment(id: "text_label") { VStack { Text("This is just an example") .font(.title) .padding(.bottom, 20) Text("This is just some random content") .font(.caption) } .frame(minWidth: 100, maxWidth: 300, minHeight: 100, maxHeight: 300) .glassBackgroundEffect() } } } }

Hello, We have an app built with a hybrid framework called NativeScript, and deployed on iPad devices. Since the update to iOS 17.4, we're experiencing crashes that seem to be caused by an out of memory problem. I was able to retrieve crashes reports in .ips format that seem to confirm the out of memory hypothesis, but by lack of experience and knowledge in iOS environment, I couldn't find the origin of the problem yet. One of the most difficult point is that we haven't been able yet to reproduce the bug at home, even with the concerned tablets. Our app crashes randomly on customer's sites, this is manifested by the app getting frozen, with graphic artifacts in the form of vertical gray stripes onto the whole screen. For now, the remedy is to reboot the tablet remotely. I've tried to launch the app on a problematic tablet in profiling mode with Xcode, with the Leaks tools from Instruments, but even after navigating in the whole app, I can't see any suspicious growth in memory usage. Is there someone here that can help me to read the .ips file to understand and isolate the cause of the problem ? Thanking you by advance. P.S : I formatted ips file in valid JSON format

Hello, My app often crashes when I use simulators. I would like some help with reading the crash report that is generated. Especially with the part below Thread 0 Crashed. Based on other posts I understand that the 0x8BADF00D in the crash report is a WatchDog crash that basically says that WatchDog terminated the app because the main thread was blocked for a significant time. Many processes can block the main thread so it's hard to find out what it is in our specific case. Can someone help me reading through the crash report? Short_crash_report.txt Background information The application is Xamarin Native and I use Rider as an IDE. When I use Visual Studio, the simulators run just fine. No crash occurs while using my app on a device. The crash happens on multiple simulators with different OS versions. I already deleted XCode cache, erased content and settings of several simulators and deleted iOS DeviceSupport files.

Hello, I am building a new iOS app which uses AVSpeechSynthesizer and should be able to mix audio nicely with audio from other apps. AVSpeechSynthesizer seems to handle setting the AVAudioSession to active on it's own, but does not deactivate the audio session. This leads to issues, namely that other audio sources remain "ducked" after AVSpeechSynthesizer is done speaking. I have implemented deactivating the audio session myself, which "works", in that it allows other audio sources to become "un-ducked", but it throws this exception each time even though it appears successful. Error Domain=NSOSStatusErrorDomain Code=560030580 "Session deactivation failed" UserInfo={NSLocalizedDescription=Session deactivation failed} It appears to be a bug with how AVSpeechSynthesizer handles activating/deactivating the audio session. Below is a minimal example which illustrates the problem. It has two buttons, one which manually deactivates the audio sessions, which throws the exception, but otherwise works, and another button which leaves audio session management to the AVSpeechSynthesizer but does not "un-duck" other audio. If you play some audio from another app (ex: Music), you'll see the button which throws/catches an exception successfully ducks/un-ducks the audio, while the one without attempting to deactivate the session ducks but does not un-duck the audio. import AVFoundation struct ContentView: View { let workingSynthesizer = UnduckingSpeechSynthesizer() let brokenSynthesizer = BrokenSpeechSynthesizer() init() { let audioSession = AVAudioSession.sharedInstance() do { try audioSession.setCategory(.playback, mode: .voicePrompt, options: [.duckOthers]) } catch { print("Setup error info: \(error)") } } var body: some View { VStack { Button("Works Correctly"){ workingSynthesizer.speak(text: "Hello planet") } Text("-------") Button("Does not work"){ brokenSynthesizer.speak(text: "Hello planet") } } .padding() } } class UnduckingSpeechSynthesizer: NSObject { var synth = AVSpeechSynthesizer() let audioSession = AVAudioSession.sharedInstance() override init(){ super.init() synth.delegate = self } func speak(text: String) { let utterance = AVSpeechUtterance(string: text) synth.speak(utterance) } } extension UnduckingSpeechSynthesizer: AVSpeechSynthesizerDelegate { func speechSynthesizer(_ synthesizer: AVSpeechSynthesizer, didFinish utterance: AVSpeechUtterance) { do { try audioSession.setActive(false, options: .notifyOthersOnDeactivation) } catch { // always throws an error // Error Domain=NSOSStatusErrorDomain Code=560030580 "Session deactivation failed" UserInfo={NSLocalizedDescription=Session deactivation failed} print("Deactivate error info: \(error)") } } } class BrokenSpeechSynthesizer { var synth = AVSpeechSynthesizer() let audioSession = AVAudioSession.sharedInstance() func speak(text: String) { let utterance = AVSpeechUtterance(string: text) synth.speak(utterance) } } (I have a separate issue where the first speech attempt takes a few seconds but I don't think it's related)

What is the latest IOS beta developer out

I have an Electron app on macOS Sonoma (arm64 arch). It has a native addon (app.node) using node-addon-api. Recently it crashed, with the stack trace (given below). What is the AXSerializeCFType function inside the AXUIElementCopyAttributeValue function, and why did it crash there? AXUIElementRef systemWideElement = AXUIElementCreateSystemWide(); AXUIElementRef focusedApp = NULL; AXError error = AXUIElementCopyAttributeValue(systemWideElement, kAXFocusedApplicationAttribute, (CFTypeRef *)&focusedApp); The crash appears to be occurring in the last line of the code, where I am retrieving the focused app AXUIElementRef using AXUIElementCopyAttributeValue. I have already attempted to manually set systemWideElement to NULL, but AXUIElementCopyAttributeValue is not crashing; it is just returning an error kAXErrorIllegalArgument. OS Version: macOS 14.5 (23F79) Report Version: 104 Crashed Thread: 344454 Application Specific Information: Fatal Error: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS / 0x102674000 Thread 344454 Crashed: 0 HIServices 0x18cb5d970 AXSerializeCFType 1 HIServices 0x18cb7ca24 serializeWrapper 2 HIServices 0x18cb7cd40 _AXXMIGCopyAttributeValue 3 HIServices 0x18cb74884 _AXUIElementCopyAttributeValue 4 HIServices 0x18cb74a04 AXUIElementCopyAttributeValue 5 HIServices 0x18cb747fc _AXUIElementCopyAttributeValue 6 HIServices 0x18cb74a04 AXUIElementCopyAttributeValue 7 app.node 0x1027a56f4 getFocusedApplication

Our Ionic App running on iOS 17.5.1, crashed. Attaching the crash report crash report 1.txt

I'm a complete newbie to building an App, this project is a GUI that interacts with an LLM AI service, it's mostly html, javascript, python. I have something that works in a web browser, and mostly works in Android Studio, but in Xcode there are numerous issues. It's my understanding this is something to do with permissions. I have asked an AI which suggested various things that haven't worked, such as reinstalling Cocoapods, and disabling SIP. Are you smarter than an AI, or at least better informed? If so, suggestions or advice would be appreciated. Sandbox: bash(5261) deny(1) file-read-data ........./ios/App/Pods/Target Support Files/Pods-App/Pods-App-frameworks.sh