This is a dedicated space for developers to connect, share ideas, collaborate, and ask questions. Introduce yourself, network with other developers, and join us in fostering a supportive community.

All subtopics
Posts under Community topic

Post

Replies

Boosts

Views

Activity

iOS 18.3 (22D5040d) issues with unexpected shut downs and heavy battery drain
iPhone 15 Pro, 96% battery health. It all started last week when i was still on a 18.2 beta version. I figured updating would fix it but it s even worse now. It charges quickly and drains as quickly. Randomly shuts down at i.e. 93% battery percentage. After power off, it powers up with 10%, repeats the cycle and then it just sticks at 10%. I’ll update when I know for how long it stays like this. Meanwhile do you guys have any idea how to temporarily fix it or a workaround for the issue until further update will fix it?
9
1
5k
Jan ’25
Apple Developer Program Account Activation - No Response
I'm experiencing an issue with my Apple Developer Program enrollment process: Submitted initial enrollment application: Sat Jan 11 21:13 (7 days ago) Current status: Stuck at "Purchase your membership" stage (pending) Waited: 6+ days without any response or ability to proceed to payment The system shows "Your purchase may take up to 48 hours to process" message No payment has been processed yet as I cannot proceed to that step I have not received any emails explaining the delay or requesting additional information. I've checked both my primary and spam folders. Is this delay normal at the pre-payment stage? What would be the recommended next steps to resolve this situation? Any guidance would be appreciated.
1
1
336
Jan ’25
Apple Developer Program Subscription Issue
Hello everyone, I’m reaching out for assistance regarding an issue with my Apple Developer Program subscription. I made the $99 USD payment for my subscription on January 10, 2025, but my account is still not active, and I am unable to publish my app. According to the process, activation should take up to 48 hours, but it has now been much longer without any updates. Additionally, when I log into the Apple Developer website, I still see the "PURCHASE" button as if the payment was not processed. Has anyone encountered a similar issue? If so, how was it resolved? Any guidance on what steps I should take next would be greatly appreciated. Thank you in advance for your help!
1
1
255
Jan ’25
Decode errors, even on "Hello, world!" - Mac
This wasn't happening until I updated Xcode to 16.2 (I'm using Sequoia 15.2). When I run any Mac app, I get these errors: Can't find or decode reasons Failed to get or decode unavailable reasons Can't find or decode disabled use cases I even got these errors running "Hello, world" which tells me that either I need to reinstall or there is a bug. Thanks for any help, -Ashley
4
0
1.4k
Jan ’25
Invalid memory pointer crash: cannot figure out cause
Hi there! I'm one year into iOS development, and can usually figure out the cause of a crash. However, I've been bumping my head against this one for a while now. Invalid memory pointer crash According to this article, the crash (EXC_BAD_ACCESS) happens due to an invalid memory pointer. When I use the atos command to symbolicate the crash report, the line where the crash happens in my app (see line 39 in the full stack trace below) is simply the very first line in MyApp that extends App (annotated with @main) -- but there's no code on that line. It seems like the error is happening somewhere with UIKit's UIViewController but I can't seem to figure it out. Could be relevant code I do have the following class in my app, which helps with hiding the tab bar I use when another view is opened. It might be relevant: struct HideTabBar: UIViewControllerRepresentable { var callback: (UITabBar) -> Void private let proxyController = ViewController() func makeUIViewController(context: UIViewControllerRepresentableContext<HideTabBar>) -> UIViewController { proxyController.callback = callback return proxyController } func updateUIViewController(_ uiViewController: UIViewController, context: UIViewControllerRepresentableContext<HideTabBar>) { } typealias UIViewControllerType = UIViewController private class ViewController: UIViewController { var callback: (UITabBar) -> Void = { _ in } override func viewWillAppear(_ animated: Bool) { super.viewWillAppear(animated) if let tabBar = self.tabBarController { self.callback(tabBar.tabBar) } } } } Full stack trace: Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000010 Exception Codes: 0x0000000000000001, 0x0000000000000010 VM Region Info: 0x10 is not in any region. Bytes before following region: 4363845616 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> Termination Reason: SIGNAL 11 Segmentation fault: 11 Terminating Process: exc handler [664] Triggered by Thread: 0 Kernel Triage: VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 libobjc.A.dylib 0x19205fc20 objc_msgSend + 32 1 UIKitCore 0x19c697a68 -[UIViewController dealloc] + 860 2 UIKitCore 0x19c863c80 -[UINavigationController dealloc] + 296 3 UIKitCore 0x19c863b34 -[_UISplitViewControllerColumnContents .cxx_destruct] + 44 4 libobjc.A.dylib 0x192061acc object_cxxDestructFromClass(objc_object*, objc_class*) + 116 5 libobjc.A.dylib 0x192060f00 objc_destructInstance + 80 6 libobjc.A.dylib 0x192060ea4 _objc_rootDealloc + 80 7 CoreFoundation 0x19a0fc730 cow_cleanup + 164 8 CoreFoundation 0x19a0fec80 -[__NSDictionaryM dealloc] + 148 9 libobjc.A.dylib 0x192061acc object_cxxDestructFromClass(objc_object*, objc_class*) + 116 10 libobjc.A.dylib 0x192060f00 objc_destructInstance + 80 11 libobjc.A.dylib 0x192060ea4 _objc_rootDealloc + 80 12 UIKitCore 0x19c8f4a54 -[UISplitViewControllerPanelImpl dealloc] + 100 13 libobjc.A.dylib 0x192061acc object_cxxDestructFromClass(objc_object*, objc_class*) + 116 14 libobjc.A.dylib 0x192060f00 objc_destructInstance + 80 15 libobjc.A.dylib 0x192060ea4 _objc_rootDealloc + 80 16 UIKitCore 0x19c457730 -[UIResponder dealloc] + 124 17 UIKitCore 0x19c697ba0 -[UIViewController dealloc] + 1172 18 libobjc.A.dylib 0x192060df4 AutoreleasePoolPage::releaseUntil(objc_object**) + 212 19 libobjc.A.dylib 0x192060c80 objc_autoreleasePoolPop + 260 20 UIKitCore 0x19c4315ec -[_UIAfterCACommitBlock run] + 92 21 UIKitCore 0x19c43149c -[_UIAfterCACommitQueue flush] + 164 22 UIKitCore 0x19c4313b4 _runAfterCACommitDeferredBlocks + 496 23 UIKitCore 0x19c430fec _cleanUpAfterCAFlushAndRunDeferredBlocks + 80 24 UIKitCore 0x19c430efc _UIApplicationFlushCATransaction + 72 25 UIKitCore 0x19c42e660 _UIUpdateSequenceRun + 84 26 UIKitCore 0x19c42e2a4 schedulerStepScheduledMainSection + 172 27 UIKitCore 0x19c42f148 runloopSourceCallback + 92 28 CoreFoundation 0x19a14b834 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 29 CoreFoundation 0x19a14b7c8 __CFRunLoopDoSource0 + 176 30 CoreFoundation 0x19a149298 __CFRunLoopDoSources0 + 244 31 CoreFoundation 0x19a148484 __CFRunLoopRun + 828 32 CoreFoundation 0x19a147cd8 CFRunLoopRunSpecific + 608 33 GraphicsServices 0x1deb951a8 GSEventRunModal + 164 34 UIKitCore 0x19c781ae8 -[UIApplication _run] + 888 35 UIKitCore 0x19c835d98 UIApplicationMain + 340 36 SwiftUI 0x19e33c294 0x19df48000 + 4145812 37 SwiftUI 0x19e2e8860 0x19df48000 + 3803232 38 SwiftUI 0x19e2f461c 0x19df48000 + 3851804 39 MyApp 0x1041f8690 0x1041b0000 + 296592 40 dyld 0x1bd91f154 start + 2356
0
1
398
Oct ’24
Critical Bug: Photos Turn Completely Black After Editing on macOS Tahoe (25A5295e)
I’ve encountered a critical issue in macOS Tahoe (Beta) that affects the Photos app or any app that leverages Apple’s editing frameworks. After editing certain photos—whether applying filters, cropping, or making basic adjustments—the image suddenly turns completely black upon saving or exiting the edit mode. Details: macOS Version: macOS Tahoe (latest beta) Affected App(s): Photos, Preview, and some third-party editing apps Steps to Reproduce: Open a photo in the Photos app Make any basic edit (e.g., crop, adjust brightness) Click “Done” The edited photo appears entirely black Notes: Happens with both JPEG and HEIC formats Original photo appears fine before editing Exporting the photo also results in a black image Restarting the app/system does not resolve the issue iCloud Photos is enabled This issue seems related to the image rendering pipeline post-editing, possibly tied to Core Image or GPU rendering frameworks. It severely affects photo usability and could result in permanent data loss if backups are not maintained. Please advise if a workaround exists or if this bug has been logged already. Happy to provide system logs or sample images if needed.
1
1
188
Jun ’25
Can I change iOS version in package.swift to use SwiftData?
For the swift student challenge I was hoping to use swift data, I found that since it's a playground app, in package.swift the defaults is set to iOS 16 which means you can't use swift data. I changed it to iOS 17 and everything works but I want to know if that goes against the rules in anyway, changing th bios version in package.swift? This was the code I changed in package.swift. let package = Package( name: "ProStepper", platforms: [ .iOS("17.0") ],
3
1
580
Jan ’25
In iOS 18 beta 5 version, setting the conversion to NSAttributedString using [.documentType: NSAttributedString.DocumentType.html] occasionally causes crashes
In iOS 18 beta 5 version, setting the conversion to NSAttributedString using [.documentType: NSAttributedString.DocumentType.html] occasionally causes crashes The same issue was encountered in previous versions. However, after running the code on the main thread, it no longer crashed. But after upgrading to the iOS 18 beta 5 version, it occasionally crashes even when running on the main thread. How can this issue be resolved?
3
1
1k
Oct ’24
Internet Sharing Wi-Fi starts as open network despite WPA2/WPA3 password configuration
On recent versions of macOS (including current betas), when enabling Internet Sharing from Ethernet to Wi-Fi, the configured WPA2/WPA3 password is ignored and the shared network is broadcast as an open (unsecured) network. Steps to Reproduce: Connect Mac to Ethernet via USB/LAN adapter Go to System Settings > General > Sharing > Internet Sharing Set up Wi-Fi options with a valid WPA2/WPA3 password Enable Internet Sharing Expected Behavior: Devices should see a password-protected Wi-Fi network with a lock icon and require authentication. Actual Behavior: The network appears unsecured (no lock icon) Devices like iPhone connect without entering a password This can be verified immediately from iOS Wi-Fi settings Additional Notes: Reproducible across macOS 15.5 RC and 16.0,26.0 Developer Beta Feedback has been submitted via Feedback Assistant multiple times This is a serious security risk if used in public or shared environments Has anyone else experienced this? Any known workarounds besides terminal-level defaults or Plist edits? Thanks in advance!
0
1
65
Jun ’25
Can't update to macOS 26 beta 2
I've got the initial WWDC beta of macOS 26 (25A5279m) installed inside a virtual machine (UTM), but can't seem to update to the second beta. Nothing is showing up within Software Update. Is this because it's within a VM, or am I doing something wrong? It'd be a real pain to have to install a new VM afresh with the RestoreImage for every update.
0
1
161
Jun ’25
Library not loaded: /usr/lib/swift/libswiftWebKit.dylib,...SquareReaderSDK
hi team To continue testing Xcode 26 beta for our POS project's compatibility with the upcoming iOS 26 release in September, we’ve been running trials on various simulators. While the app works fine on iOS 18 simulators (iPad Pro/Air), it fails to launch on iOS 26-based iPad simulators with the following error: "libswiftWebKit.dylib library is not loaded"...... SquareReaderSDK Reason: tried: '/Users/username/Library/Developer/Xcode/DerivedData/ProjectnamePOS-buqsthxxbyqalydvfpxruhzgmymf/Build/Products/Debug-iphonesimulator/libswiftWebKit.dylib (Detailed logs are shared below.) Is there a known fix for this issue, or is a resolution expected in an upcoming beta release? dyld[34660]: Library not loaded: /usr/lib/swift/libswiftWebKit.dylib Referenced from: <BA066DAA-6AD6-3622-9A40-08C1600B0DC6> /Users/username/Library/Developer/CoreSimulator/Devices/3F807800-D684-4398-89DC-1AEC1747A99A/data/Containers/Bundle/Application/5327A260-4241-48F6-85C2-A7E0E0F152E3/Projectname.app/Frameworks/SquareReaderSDK.framework/SquareReaderSDK Reason: tried: '/Users/username/Library/Developer/Xcode/DerivedData/ProjectnamePOS-buqsthxxbyqalydvfpxruhzgmymf/Build/Products/Debug-iphonesimulator/libswiftWebKit.dylib' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/introspection/libswiftWebKit.dylib' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/swift/libswiftWebKit.dylib' (no such file), '/usr/lib/swift/libswiftWebKit.dylib' (no such file, not in dyld cache), '/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libswiftWebKit.dylib' (no such file) Library not loaded: /usr/lib/swift/libswiftWebKit.dylib Referenced from: <BA066DAA-6AD6-3622-9A40-08C1600B0DC6> /Users/username/Library/Developer/CoreSimulator/Devices/3F807800-D684-4398-89DC-1AEC1747A99A/data/Containers/Bundle/Application/5327A260-4241-48F6-85C2-A7E0E0F152E3/Projectname.app/Frameworks/SquareReaderSDK.framework/SquareReaderSDK Reason: tried: '/Users/username/Library/Developer/Xcode/DerivedData/ProjectnamePOS-buqsthxxbyqalydvfpxruhzgmymf/Build/Products/Debug-iphonesimulator/libswiftWebKit.dylib' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/introspection/libswiftWebKit.dylib' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/swift/libswiftWebKit.dylib' (no such file), '/usr/lib/swift/libswiftWebKit.dylib' (no such dyld config: DYLD_SHARED_CACHE_DIR=/Library/Developer/CoreSimulator/Caches/dyld/24F74/com.apple.CoreSimulator.SimRuntime.iOS-26-0.23A5260l/ DYLD_ROOT_PATH=/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot DYLD_LIBRARY_PATH=/Users/username/Library/Developer/Xcode/DerivedData/ProjectnamePOS-buqsthxxbyqalydvfpxruhzgmymf/Build/Products/Debug-iphonesimulator:/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libLogRedirect.dylib:/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libBacktraceRecording.dylib:/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libMainThreadChecker.dylib:/usr/lib/libRPAC.dylib:/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib/libViewDebuggerSupport.dylib DYLD_FRAMEWORK_PATH=/Users/username/Library/Developer/Xcode/DerivedData/ProjectnamePOS-buqsthxxbyqalydvfpxruhzgmymf/Build/Products/Debug-iphonesimulator DYLD_FALLBACK_FRAMEWORK_PATH=/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks DYLD_FALLBACK_LIBRARY_PATH=/Library/Developer/CoreSimulator/Volumes/iOS_23A5260l/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 26.0.simruntime/Contents/Resources/RuntimeRoot/usr/lib```
0
1
101
Jun ’25
CoreAudio: Audio Output Device Stopped Error since macOS 15
Hello! I used the Apple CA Playthrough example code that pipes audio between devices. It uses AudioUnit callbacks to pipe the input to an output device, and I created a system equalizer with it - however users reported it stopped working in macOS 15. I am getting the error HALPlugIn.cpp:552 HALPlugIn::DeviceGetCurrentTime: got an error from the plug-in routine, Error: 1937010544 (stop) for the output device and no sound coming out of the speakers. The error only occurs when using a virtual device as an input, not using the microphone. First I thought the problem was in the loopback driver, but it also does not work with other loopback drivers like Blackhole. STEPS TO REPRODUCE Install a virtual device, for example "brew install blackhole-2ch" and run the CAPlayThrough example code (you need to add Mic Permission in the info.plist). Then set your system audio output to the virtual device, select the device as input in CAPlayThrough and hit start. You should see the error in console. My question: What did change in macOS 15 that could cause this? Is it something with the new permission handling maybe?
0
1
535
Jan ’25
Beta update 18.3 on IOS
Beta Update Feedback: iOS 18.3 The iOS 18.3 beta update has been a deeply frustrating experience due to numerous critical issues that severely impact the device's functionality. Below is a detailed report of the problems encountered: All major social applications, including WhatsApp, Instagram, and Photos, consistently crash. When launching these apps, the screen often turns dark before reverting to the home screen. This issue persists across other third-party and native apps, making the device unusable for basic tasks. The system frequently hangs, failing to process basic operations effectively. Restarting the device is often the only temporary solution; however, even after multiple restarts, the issues remain unresolved. Significant charging drops are observed, and the device intermittently fails to recognize the charger. Charging efficiency has drastically decreased, creating inconvenience for daily usage. The Photos app is riddled with bugs, making it nearly impossible to use. Basic functions such as viewing, editing, or sharing photos do not work properly. Every aspect of the update feels unstable, with issues cropping up in every corner of the system. The phone’s functionality has deteriorated, so it no longer performs as expected. Device Affected: iPhone 13 Impact Level: Severe This update has caused immense frustration and has made the iPhone 13 difficult.
2
1
2.2k
Jan ’25
tvOS 26 issue: Please bring back passcode-locked apps — disappearing apps and shared restrictions make Apple TV frustrating for families
I recently updated to tvOS 26 on my Apple TV 4K (1st generation) and was disappointed to find that apps I restrict no longer appear at all. In earlier versions, restricted apps would still be visible and simply prompt for a passcode — this was much more convenient for adults in the household. Now, if I restrict apps for my children, they disappear completely. To use them again, I have to go deep into settings, turn restrictions off, and even recreate the passcode each time, which is frustrating and impractical for daily use. I also tried adding a Kids user account, but most restrictions still apply system-wide. Only the Apple TV app behaves differently between users. This makes switching between parent and child accounts nearly pointless for managing access. Please consider one or both of the following: 1. Bring back the passcode-on-launch behavior for restricted apps (instead of hiding them). 2. Give each user their own isolated settings environment, like how profiles work on iOS/iPadOS or even a fresh Apple TV—this way, restrictions, home screen, and app access could be personalized. Families are a huge part of the Apple TV audience, and these recent changes have made it much harder to use the device in a shared household. Thank you!
2
1
181
Jun ’25