Search results for

DTiPhoneSimulatorErrorDomain Code 2

159,888 results found

Post

Replies

Boosts

Views

Activity

Reply to First time SSC contestant here. Need some advice.
[quote='877433022, mlgiPhone7plus, /thread/812911?answerId=877433022#877433022, /profile/mlgiPhone7plus'] Could it be okay to leave a note in the Other comments section of the form for the judges to run apps on a live iPhone or iPad? [/quote] Leaving a note is OK, obviously, but I can’t promise that it’ll have any effect. There are two ways to submit your app. One of them guarantees that your submission will be run on device, but it has a significant limitation. I just posted a summary of the current state of affairs here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
36m
Async AVAudioPlayerNode.scheduleBuffer stutters
My code that streams buffers into AVAudioPlayerNode is stuttering when the buffer is finished and before the next one is played. while engine.isRunning { let framesToCopy = min(buffer.frameLength - framePosition, Self.BufferSize) let srcRaw = UnsafeRawPointer(srcPtr) let playbackBuffer = AVAudioPCMBuffer(pcmFormat: buffer.format, frameCapacity: Self.BufferSize)! let playbackPtr = playbackBuffer.floatChannelData![0] let destRaw = UnsafeMutableRawPointer(mutating: playbackPtr) memcpy(destRaw, srcRaw, Int(framesToCopy) * MemoryLayout.stride) srcPtr = srcPtr.advanced(by: Int(framesToCopy)) playbackBuffer.frameLength = framesToCopy await player.scheduleBuffer(playbackBuffer, at: nil, options: [], completionCallbackType: .dataRendered) } I've tried to schedule multiple buffers at once using a combination of both the synchronous and async versions of scheduleBuffer because I thought the delay might be but it still stutters and the data copied into the playbackBuffer matches the source buffer. I've tried all
0
0
12
55m
Reply to Can my submission be ran on iPhone?
Right. The submission form has two options: Swift Playground 4.6 or later Xcode 26 or later (with a note saying “Xcode app playgrounds are run in Simulator.”) In the first case, your submission must necessarily be run on an iPad. In the second, your submission will be run on the simulator, not a real device. There are some caveats here: In the first case, the Swift Playground app doesn’t yet include support for the iOS 26 SDK )-: See this thread. In the second case, the form doesn’t currently say whether it’ll be an iPhone on iPad simulator. See this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
2h
Reply to My EndpointSecurity Client process is kicked by OS on Mac sleep/wake cycle
Thank you so much for the elaborate and helpful reply. I will try to address each point, to try and see how to close in on my problem. I will also attach a sample crash-report. My rule engine is very fast, based on NSPredicates over ObjC custom classes (No core-data etc.). Rule evaluation is completely internal to my daemon, no API calls and no external calls. There IS , however a stage prior to rule evaluation, where I Parse ES messages into my custom ObjC class, and in that stage there are few API calls one of which has given me grief in the past. I need to decide whether a file-system object (from the ES message) is a Document, in my own semantics. A document is any normal file, or -- package directories. If the file-system object exists and is a directory, and it has a file-name extension, I use something like: _isDocument = [[NSWorkspace sharedWorkspace] isFilePackageAtPath:_filePath ]; If it is non-existing (to be created etc.) Then I use this heuristics and API: { // non-existing directory object about
Topic: App & System Services SubTopic: Core OS Tags:
4h
AudioQueueNewOutput blocks indefinitely on iOS 18.3 (hangs during creation)
Hi everyone, We’re encountering an issue where AudioQueueNewOutput blocks indefinitely and never returns, and we’re hoping to get some insight or confirmation if this is a known behavior/regression on newer iOS versions. Issue Description When triggering audio playback, we create an output AudioQueue using AudioQueueNewOutput. On some devices, the call hangs inside AudioQueueNewOutput and never returns, with no OSStatus error and no subsequent logs. This behavior is reproducible mainly on iOS 18.3. Earlier iOS versions do not show this issue under the same code path. if (audioDes) { mAudioDes.mSampleRate = audioDes->mSampleRate; mAudioDes.mBitsPerChannel = audioDes->mBitsPerChannel; mAudioDes.mChannelsPerFrame = audioDes->mChannelsPerFrame; mAudioDes.mFormatID = audioDes->mFormatID; mAudioDes.mFormatFlags = audioDes->mFormatFlags; mAudioDes.mFramesPerPacket = audioDes->mFramesPerPacket; mAudioDes.mBytesPerFrame = audioDes->mBytesPerFrame; mAudioDes.mBytesPerPacket = audioDes->
0
0
12
5h
Device-Specific Instant Crash on Post-Login in Production iOS App (App Store Distribution)
Hi all, I’m facing a device-specific issue in a live production iOS app distributed privately via the App Store . The app crashes immediately after login on one client’s iPhone, while the same account works fine on other devices. There’s no crash log generated in Analytics, and the app just pops to the home screen. Environment: App: Production app on App Store iOS version: 26.3 Devices: Only one device exhibits the crash; other iPhones work fine Login flow: App calls an API and writes the response to a local SQLite database immediately after login Distribution: App Store (Privately). The user is install via the redemption codes. Observations: All users on the problematic device crash immediately after login. The crash does not occur on any other devices, including the same iOS version. The client had already uninstalled and reinstalled the app via App Store cloud download, but the crash persisted. No crash log appears in Analytics or Xcode (process just terminates). Device restart had not been attemp
0
0
26
8h
Reply to UITabBarController crashes when editing the items
Until 26.4 is generally available, I have found an ugly, but usable, workaround: First perform method swizzling to replace addSubiew:, then in the replacement implementation do nothing when a view is being added to it self This will avoid the crash, but results in a graphic glitch where the selection overlay is opaque over some tabs. Very ugly. To solve this problem: Implement the tab-bar-controller delegate method to detect when customization has ended. When it has ended, set the tab-bar-controller's view-controllers to just the first view-controller, without animation. Then immediately restore the original set of view-controllers, again without animation. This will force the tab-bar to refresh and resolve the graphic glitch from (1) Finally, set the more-view-controller as the selected-view-controller again, since the re-setting of view-controllers in (2) will reset the selected tab. With the above, I do not experience crashes, and there is about 1/2 a second of visual glitching, but thing
Topic: UI Frameworks SubTopic: UIKit
9h
Reply to Apple App Store
Es tut mir leid zu hören, dass Sie Probleme mit der App Store-Leistung auf Ihrer Beta 2 iOS 26.4-Version haben. Hier sind ein paar Schritte, die Sie ausprobieren könnten, um die Situation zu verbessern: Neustart des Geräts: Manchmal kann ein einfacher Neustart helfen, kleinere Softwareprobleme zu beheben. Prüfen auf Updates: Stellen Sie sicher, dass Sie die neuesten Beta-Updates installiert haben. Manchmal werden in nachfolgenden Beta-Versionen Leistungsverbesserungen vorgenommen. Schließen anderer Apps: Stellen Sie sicher, dass nicht zu viele Apps im Hintergrund laufen, da diese die Leistung beeinträchtigen können. Freier Speicherplatz: Prüfen Sie, ob auf Ihrem Gerät noch ausreichend Speicherplatz vorhanden ist. Ein Mangel an Speicherplatz kann die Leistung beeinträchtigen. Temporäre Dateien löschen: Gehen Sie zu Einstellungen > Allgemein > iPhone-Speicher und löschen Sie temporäre Dateien oder Apps, die Sie nicht mehr benützen. Netzwerkverbindung prüfen: Stellen Sie sicher, dass Sie eine stab
9h
navigationItem.titleView shifted left when leftBarButtonItem is nil in iOS 26
iOS 26 – navigationItem.titleView shifted left when leftBarButtonItem is nil Hi everyone, I’m encountering a layout issue on iOS 26 related to navigationItem.titleView positioning. What I’m Doing I’m hiding the default back button and removing the left bar button item: navigationItem.leftBarButtonItem = nil navigationItem.hidesBackButton = true navigationItem.setLeftBarButtonItems([], animated: true) Then I create a custom titleView with a specific width calculated as: Screen width minus the width of the two bar button items (left and right). let titleView = UIView(frame: CGRect(origin: .zero, size: sizeOfTitleView)) let titleLabel = UILabel(frame: CGRect(origin: .zero, size: sizeOfTitleView)) Expected Behavior On previous iOS versions, the titleView is perfectly centered in the navigation bar. Actual Behavior (iOS 26) On iOS 26, when leftBarButtonItem is nil, the titleView is pushed slightly to the left instead of being centered (see attached image). Question Has there been a change in UINavigationB
Topic: UI Frameworks SubTopic: UIKit Tags:
0
0
30
10h
Reply to Is calling different SBApplication objects from different threads bad?
The test using a fake job did not cause a crash, only a hang of the ProofProcessor - FAKE1 NSOperation. I'll grab a sysdiagnose the next time this happens, which could be tomorrow. There's currently one user's job that is repeatedly causing an exception to be thrown while sending AppleEvents via ScriptingBridge. It's probably related, but is not causing the same 2 jobs sending AEs and causing the crash situation.
10h
Reply to Is calling different SBApplication objects from different threads bad?
First up, on the bug side, what would be most useful now would be to capture a sysdiagnose after the crash, then upload that log to the bug. A few notes on that: The log doesn't need to be collected all that soon after the bug. I try to collect within a few minutes of the crash, but there really isn't any difference triggering within the next 15+ minutes. Eventually, we start purging log data (losing data), but I've gotten useful data out of logs that were taken hours after the event. It IS important that you not reboot the machine first. Lots of data is purged during that process, to the point where I've basically found those logs useless. PLEASE include information about WHEN the problem occurred. Even better, upload the crash log from the same crash you want to use to look at in the sysdiagnose. The log volume is so high that trying to figure out what happened without a time reference can be extremely slow and time-consuming. Similarly, the crash log should be included in the sysdiagnose, but there are cas
11h
Reply to Translation framework use in Swift 6
I have found two possible solutions : either (1) use @preconcurrency import Translation instead of just import Translation, and it works magically ; or (2) mark the translationTask closure as @Sendable, and detach to MainActor when needed : .translationTask(configuration) { @Sendable session in do { let responseText = try await session.translate(sourceText).targetText await MainActor.run { // ... propagate back to UI } } catch {} } I'm not sure which is the best solution: #1 is shorter and cleaner but I don't know how it handles concurrency behind the scenes, #2 is more tedious but the isolation path is more clear.
Topic: Machine Learning & AI SubTopic: General Tags:
12h
MusicKit - ApplicationMusicPlayer fails to play certain Songs
[Note: this issue was happening on a main testing device, and after testing the same code on other devices, this issue is only happening on 1 out of 4 devices] We are successfully getting a MusicCatalogResourceResponse for every song ID where we make the MusicCatalogResourceRequest. We are able to display the song title, artist name, and album artwork for each Song in the response. However - when we go to play the song, there are some songs that play, and several songs that do not play. For the songs that don't play, the console shows “Failed to prepareToPlay error=” let musicPlayer = ApplicationMusicPlayer.shared func playSong(_ song: Song) { musicPlayer.queue = [song] Task { try await musicPlayer.prepareToPlay() try await musicPlayer.play() } Is there anything else we can investigate about what may be causing specific song IDs not to play on this specific device? Even if we remove line 6 musicPlayer.prepareToPlay() we still see the same console error when running playSong with the Songs that don't
0
0
24
12h