User Profile

In Apple's crash organizer, I'm seeing a handful of crash reports come in. It doesn't appear to be a widespread issue, but keeps happening now and again.Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Description: DYLD, Library not loaded: @rpath/libswiftCoreGraphics.dylib | Referenced from: /var/containers/Bundle/Application/7208AD66-5D56-4973-88A9-8D22D7E541DB/myapp.app/myapp | Reason: no suitable image found. Did find: | /private/var/containers/Bundle/Application/7208AD66-5D56-4973-88A9-8D22D7E541DB/myapp.app/Frameworks/libswiftCoreGraphics.dylib: code signature invalid for '/private/var/containers/Bundle/Application/7208AD66-5D56-4973-88A9-8D22D7E541DB/myapp.app/Frameworks/libswiftCoreGraphics.dylib' | Triggered by Thread: 0 Thread 0 Crashed: 0 dyld 0x00000001004d5cbc __abort_with_payload + 8 1 dyld 0x00000001004d5668 abort_with_payload_wrapper_internal + 100 (terminate_with_reason.c:71) 2 dyld 0x00000001004d5694 abort_with_payload + 12 (terminate_with_reason.c:93) 3 dyld 0x00000001004b4514 dyld::halt(char const*) + 320 (dyld.cpp:4487) 4 dyld 0x00000001004b69a8 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 4072 (dyld.cpp:6110) 5 dyld 0x00000001004b1044 _dyld_start + 68A couple of versions ago, I saw a similar crash with libswiftCoreMedia.dylib instead of Core Graphics.Any thoughts on what I can do to mitigate this or stamp it out?

I'm trying to experiment with a Catalyst version of my iPad app. I checked the checkbox, I selected the "My Mac" scheme, I ran... and then, code signing errors! In the "Advanced" WW session, it works like magic with Automatic Signing. Unfortunately, I support CarPlay and thus have to manually sign my app. Not as magical.When I checked the checkbox, the Signing & Capabilties tab added a new macOS platform entry, and a bundle identifier: maccatalyst.com.mycompany.myapp. That maccatalyst.com bundle ID isn't dispalyed in my Certifiicates, Identifiers & Profiles section of the Apple developer site. When I try to add it manually, by adding an App ID, choosing Mac and specifying the explicit bundle ID, I get the following error: An App ID with Identifier 'maccatalyst.com.mycompany.myname' is not available. Please enter a different string.How do I proceed?

I'm using Core Data automatic NSManagedObject subclass generation, with a custom Class Definition. I want to update a non-managed property when a managed property value changes. So, I'm trying to use the override accessor enhancements from iOS 10.0 (https://developer.apple.com/library/archive/releasenotes/General/WhatNewCoreData2016/ReleaseNotes.html):- (void)setDepartment:(Department *)value // invoke the dynamic implementation of setDepartment [self managedObjectOriginal_setDepartment:value]; NSLog(@"invoked %@", NSStringFromSelector(_cmd));Problem is that my custom class is in Swift, so I'm at a loss on how to do this override. I've triedmanagedObjectOriginal_setProperty(property)But it gives me a compiler error. Is there any way to use this in Swift?

Seeing some surprising behavior when using the new Simulating Remote Notifications feature in the Xcode 11.4 beta.Looks like my payload in my APNS file is correct - it displays the notification correctly in the Simulator on Springboard, and if I click the Notification my app launches. But if I set the content-availble value to "1", and then simulate the notification, the App Delegate's application(_:performFetchWithCompletionHandler:) method is called, and not application(_:didReceiveRemoteNotification:fetchCompletionHandler:). I'd expect the former to be called only when I'm trying to do a Background App Refresh. This a bug or is there a chance that I'm doing something wrong?

I have an existing app with a number of buttons whose width is determined by their text content. Since I don't know the width until runtime, the button's background is configured with a stretchable image so that the width (or height) can vary. After confuguring the Asset catalog to add a Dark appearance, I've noticed some curious behavior when toggling between light and dark mode and viewing these buttons.When I toggle from light to dark mode and then resume my app, the visual appearance of the buttons does not change. If I print the debug description of the button's trait collection, the UserInterfaceStyle is Dark, as expected. But when I retrieve the background image using the button's backgroundImage(for:) method, it's trait collection's UserInterfaceStyle is still Light.As a workaround - If I go into the Asset Catalog and change Slicing to none, so that the image is no longer stretchable, at runtime the button's visual appearance changes when toggling between Light and Dark Mode as expected. But, if I print the debug descriptions as described above, there still is a descrepancy between the Button and the background image.Is there any additional configuration I need to do to get buttons with stretchable backgrounds to render correctly in both light and dark mode?Feedback Assistant report is FB6626669