Search results for

İOS 26 beta battery %1

253,701 results found

Post

Replies

Boosts

Views

Activity

EXC_BAD_ACCESS (code=EXC_I386_GPFLT) when using RegisterEventHotKey + SwiftUI AppDelegate
Hi everyone, I’m working on a macOS SwiftUI app that integrates a global keyboard shortcut using the old Carbon API (RegisterEventHotKey, InstallEventHandler, etc.). Everything works fine initially, but I’m running into a consistent EXC_BAD_ACCESS (code=EXC_I386_GPFLT) crash when the app is reopened, or sometimes even while drawing on my SwiftUI canvas view. Setup Here’s the relevant setup (simplified): private let hotKeySignature: FourCharCode = 0x626c6e6b // 'blnk' private weak var hotKeyDelegate: AppDelegate? private func overlayHotKeyHandler( _ callRef: EventHandlerCallRef?, _ event: EventRef?, _ userData: UnsafeMutableRawPointer? ) -> OSStatus { guard let appDelegate = hotKeyDelegate else { return noErr } return appDelegate.handleHotKey(event: event) } final class AppDelegate: NSObject, NSApplicationDelegate { private var hotKeyRef: EventHotKeyRef? private var eventHandlerRef: EventHandlerRef? override init() { super.init() hotKeyDelegate = self } func applicationDidFinishLaunching(_ notification: Not
Topic: UI Frameworks SubTopic: SwiftUI
1
0
30
1d
Reply to App Extension Network Extension - failed to start, signature check failed
Looking into the sysex vs appex, thanks. We probably want to support both eventually, but at the moment the app is distributed on our own with Developer ID signing + notarizing. Also, somehow the issue in the post was cause by a previously installed (6 months ago or more) iOS version of the very same app (same identifier for the app and NE). TestFlight iOS app was also somewhere in /Applications and probably affected developer build of the mac version. After deleting the iOS TestFlight version of the app we managed to finally run in Debug mode on the failing device.
1d
My game was decompiled and published on the App Store
Hi everyone, I'm the developer of Evil Neighbor games. https://play.google.com/store/apps/developer?id=Tonny+Nevel My game was decompiled and published on the App Store. With super-stupid input controls and a lot of ads. https://apps.apple.com/us/app/evil-father-simulator-game/id1660614304 It's a clone of my game: https://play.google.com/store/apps/details?id=com.juliopepe.evilfather2 I decided to make a port on the iOS App Store, as my users asked me about it. And got rejected for all 3 parts with the reason Spam. On my own game I have sent a report for this account 4 months ago https://apps.apple.com/us/developer/manale-adle/id1671853753 (By the way, all other games are stolen too) App store is ignoring me; they sent a message to me and to him. Asked him to contact me and solve the issue. 4 months I have been waiting for a reply from them. I have sent 10+ emails, but it looks like they just put me on the ignore list. Two days ago, I tried to publish another game that I was developing during the yea
0
0
17
1d
Opening two (or more files) with one dialog box (save panel)
I am slowly converting an Objective C with C program to Swift with C. All of my menus and dialog boxes are now in Swift, but files are still opened and closed in Objective C and C. The following code is Objective C and tries to open two files in the same directory with two related names after getting the base of the name from a Save Panel. The code you see was modified by ChatGPT 5.0, and similar code was modified by Claude. Both LLMs wrote code that failed because neither knows how to navigate Apple’s sandbox. Does anybody understand Apple’s sandbox? I eventually want to open more related files and do not want the user to have to click through multiple file dialog boxes. What is the best solution? Are the LLMs just not up to the task and there is a simple solution to the Objective C code? Is this easier in Swift? Other ideas? Thanks in advance for any help. (BOOL)setupOutputFilesWithBaseName:(NSString*)baseName { NSString *outFileNameStr = baseName; if (outFileNameStr == nil || [outFileNameStr length] == 0)
0
0
101
1d
Reply to FileProviderUI prepare method receives internal fileprovider ID list instead of actual itemIdentifier
I'm looking into rewriting our non-replicated FP as a replicated FP, and I'm running into this as well. I'd like to show some UI that includes information from the database we keep about items, and if I had the NSFileProviderItemIdentifier we give to iOS, I could use that to look up the info. Is there any no way to convert the __fp/fs/docID ID into the original ID?
Topic: App & System Services SubTopic: Core OS Tags:
1d
Build Error
While build now I receive this error help me to resolve it Showing Recent Errors Only Prepare build error: Multiple commands produce '/Users/mayankjain/Library/Developer/Xcode/DerivedData/PCS_EmpApp-chsylqbxjptobeawzzckymqzagvr/Build/Products/Debug-iphonesimulator/PCS_EmpApp.app/Info.plist' note: Target 'PCS_EmpApp' (project 'PCS_EmpApp') has copy command from '/Users/mayankjain/Documents/05-NOV-2025-SWETA_IOS/PCS_EmpApp/PCS_EmpApp/xcode-out/Platforms/iOS/Info.plist' to '/Users/mayankjain/Library/Developer/Xcode/DerivedData/PCS_EmpApp-chsylqbxjptobeawzzckymqzagvr/Build/Products/Debug-iphonesimulator/PCS_EmpApp.app/Info.plist' note: Target 'PCS_EmpApp' (project 'PCS_EmpApp') has process command with output '/Users/mayankjain/Library/Developer/Xcode/DerivedData/PCS_EmpApp-chsylqbxjptobeawzzckymqzagvr/Build/Products/Debug-iphonesimulator/PCS_EmpApp.app/Info.plist' Multiple commands produce '/Users/mayankjain/Library/Developer/Xcode/DerivedData/PCS_EmpApp-chsylqbxjptobeawzzckymqzagvr/Build/Products/Debug
Topic: Design SubTopic: General
0
0
157
1d
Missing notification – APNs success but not delivered to device
We have a customer reporting that they didn’t receive some of their push notifications. On November 3, 2025, four push notifications were sent — the customer received the first three but not the last one. Our logs show a successful response from APNs, with the apns-id c116d650-efc6-4fb1-8a74-382d5bab4692. A very similar case occurred on October 31, where the customer also claimed not to have received the notification, yet our logs again show success from APNs with apns-id 1468ef43-66d6-40d2-b10a-c96889fcb65a. Wondering if there any way to help us to trace these cases. Thanks
3
0
72
1d
Not able to write AAC audio with 96 kHz sample rate using AVAudioRecorder or Extended audio file services
Not able to record audio in AAC format with 96 kHz sample rate using AVAudioRecorder or Extended Audio File services with 96 kHz input audio from input device. The audio recording settings used are let settings: [String: Any] = [ AVFormatIDKey: Int(kAudioFormatMPEG4AAC), AVSampleRateKey: sampleRate AVNumberOfChannelsKey: 1 AVEncoderAudioQualityKey: AVAudioQuality.high.rawValue ] When tried using AVAudioEngine using AVAudioFile, AVAudioFile(forWriting: fileURL, // file extension .m4a settings: fileSettings, commonFormat: AVAudioCommonFormat.pcmFormatFloat32, interleaved: interleaved) else { return } got error CodecConverterFactory.cpp:977 unable to select compatible encoder sample rate AudioConverter.cpp:1017 Failed to create a new in process converter -> from 1 ch, 96000 Hz, Float32 to 1 ch, 96000 Hz, aac (0x00000000) 0 bits/channel, 0 bytes/packet, 0 frames/packet, 0 bytes/frame, with status 1718449215
0
0
32
1d
Reply to How to index file based documents in Core Spotlight
“Allowed” is a tricky word, because it covers both business and technical limitations. I don’t work for App Review and thus can’t offer definitive answers about the former. I recommend that you review their published guidelines. But ignoring that, the technical aspects are also tricky. The basic idea of updating your Core Spotlight index in the background should be feasible. The sticking point is getting access to the documents. The cool thing about Spotlight importers is that they’re tightly sandboxed. So the system is able to find all the user’s documents and present them to the importer. The importer is sandoxed so info can’t leak to the app, and the app never gets access to the user’s entire file system. Neat-o! You lose that if you do this indexing yourself. You will be able to access any documents in your app’s container, and any documents which you were previously granted access to by the system [1], but you won’t necessarily be able to see all documents. Share and Enjoy — Quinn “The Eskimo!”
Topic: App & System Services SubTopic: Core OS Tags:
1d