Search results for

DTiPhoneSimulatorErrorDomain Code 2

158,457 results found

Post

Replies

Boosts

Views

Activity

Reply to JavaScript/Swift Interoperability
[quote='871830022, matthewruzzi, /thread/812360?answerId=871830022#871830022, /profile/matthewruzzi'] Are there any other places that I should post this to get more discussion? [/quote] I can think of least two: JavaScriptCore is open source as part of WebKit project, and they have their own community discussions. Likewise, Swift is open source and has Swift Forums. The best approach kinda depends on who you want to do the work. If you just want Apple to fix something, Feedback Assistant is your best option [1]. But if you want to engage with other developers then things get more nuanced, especially with regards to where the changes land, which is a big factor in what work gets done and who does it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] For more about that process, see Bug Reporting: How and Why?. And if you do file this in Feedback Assistant, please post your bug number, just for the record.
Topic: Programming Languages SubTopic: Swift Tags:
2m
Crash in libicucore via NSDateFormatter dateFromString: on iOS 26.2
Introduction: I’m encountering a consistent crash in production on iOS 26.2 (build 23C55). The crash occurs deep within libicucore when calling [NSDateFormatter dateFromString:]. Crash Summary: Exception Type: SIGSEGV (SEGV_ACCERR) Fault Address: 0xffffffff Thread: Crashed on Main Thread (Thread 0) Library: libicucore.A.dylib Code Snippet: The crash is triggered by the following method. It converts a string to an NSDate using a specific format and locale: // 获取日期date - (NSDate *)getDateWithTime:(NSString *)time formatter:(NSString *)formatterStr { NSDateFormatter *formatter = [[NSDateFormatter alloc] init]; [formatter setDateFormat:formatterStr]; formatter.timeZone = [NSTimeZone timeZoneWithName:@Asia/Shanghai]; formatter.locale = [[NSLocale alloc] initWithLocaleIdentifier:@en_US_POSIX]; return [formatter dateFromString:time]; } Backtrace: Here is the relevant part of the crash report: Incident Identifier: E24485B6-C53E-4115-A6CF-A7E4A952AD50 CrashReporter Key: 21FAC1CF-F56B-409A-98AA-351D3D2EB06C Ha
0
0
43
6h
Reply to Universal Control Copy Paste Issue
I agree with @Etresoft, but I would also point out that these forums aren't the place for your post. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. You are talking to other third-party developers here. While some Apple employees do visit these forums, they are likely to agree with @Etresoft in this instance, and, if they don't agree, they would probably point out that your issue is more suited to the Apple Support Forums. (And yes, I'm aware of your other post regarding being unable to post in the other forums, but that does not negate the fact that this is not the place for your post.)
11h
Reply to Choppy minimized search bar animation
Thanks for the post. Instead of examining the two distinct attributes that will trigger the animation, I should directly copy the code and test it myself. I'm a horrible human compiler and I should let Xcode do the work for me. .searchable(text: $searchQuery) .searchToolbarBehavior(.minimize) Upon using your code and utilizing the most recent released version of Xcode, I have not observed the choppy animation issue on my end. I would be grateful if you could provide the specific version of Xcode and simulator you are experiencing this problem with, as it could potentially be a bug. Let’s get to the bottom of this! Albert Pascual
  Worldwide Developer Relations.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
13h
Memory leak when no draw calls issued to encoder
I noticed that when the render command encoder adds no draw calls an apps memory usage seems to grow unboundedly. Using a super simple MTKView-based drawing with the following delegate (code at end). If I add the simplest of draw calls, e.g., a single vertex, the app's memory usage is normal, around 100-ish MBs. I am attaching a couple screenshot, one from Xcode and one from Instruments. What's going on here? Is this an illegal program? If yes, why does it not crash, such as if the encode or command buffer weren't ended. Or is there some race condition at play here due to the lack of draws? class Renderer: NSObject, MTKViewDelegate { var device: MTLDevice var commandQueue: MTL4CommandQueue var commandBuffer: MTL4CommandBuffer var allocator: MTL4CommandAllocator override init() { guard let d = MTLCreateSystemDefaultDevice(), let queue = d.makeMTL4CommandQueue(), let cmdBuffer = d.makeCommandBuffer(), let alloc = d.makeCommandAllocator() else { fatalError(unable to create metal 4 objects) } self.device
0
0
129
17h
Reply to Multi-machine Code Signing
After playing with builds and code signing over this weekend, I'm now not sure my original idea about this failure is correct. It's rather something about rebooting the machine that makes the magic work. If I work on a source tree, editing files, checking things into and out of source code control, performing builds or parts of builds, etc., code signing the final build often fails. If I reboot the system and make the full build right away, before doing anything else, it works. Some tool that I use must be corrupting it. Unless someone knows ways to interfere with code signing that might align with this, I will take this away and try to gather more information. Thanks for your help so far.
17h
Unable to login to my Apple Developer Account
Hello! I've been trying to login to my account for over a week now. All the time I am getting an error Too many verification codes have been sent. Enter the last code you received or try again later.. I cannot contact developer support because that also requires login. There is zero help whatsoever. I don't know what to do anymore. Anyone experienced same issue? Last verification code I received was December 30. Since then my account is basically locked.
0
0
27
17h
Temporarily disable macOS capture of USB RFID reader(s)
Hello. I am attempting to wrap the C library libnfc as a Swift library. This is not for use on macOS - it's mainly for use on Linux (Raspberry Pi). I have a USB reader and my code appears to work so far, however the code/test/debug cycle is suboptimal if I'm running the code on the Pi. As I use a Mac for day-to-day coding, I'd prefer to use Xcode and my Mac for development. MacOS appears to capture the NFC hardware for its own frameworks and attempting to open a connection to the USB device gives a Unable to claim USB interface (Permission denied) error. ioreg shows that the hardware is claimed by an Apple framework: UsbExclusiveOwner = pid 10946, com.apple.ifdbun Is there a way to temporarily over-ride that system and use the hardware myself? I've tried Googling but most of the replies are out of date and Claude's advice launchctl unload /System/Library/LaunchDaemons/com.apple.ifdreader.plist doesn't appear to work... I'm wary of disabling SIP - is there a simple way to ha
0
0
34
22h
Reply to Choppy minimized search bar animation
Dear @DTS Engineer, Thank you for your reply and suggested way forward. I reduced the code to the minimum for further testing purposes: struct SwiftUIView: View { @State var searchQuery: String = var body: some View { NavigationStack { ScrollView { Text(Test) } .navigationTitle(Test) } .searchable(text: $searchQuery) .searchToolbarBehavior(.minimize) } } #Preview { if #available(iOS 26, *) { TabView { Tab { SwiftUIView() } label: { Label(Test, systemImage: calendar) } } } else { // Fallback on earlier versions } } I did not remove .searchable as per your suggestion since without it the .searchToolbarBehavior(.minimize) does not appear to have any effect (the search button is simply not shown). The code above still leads to the same choppy animation as demonstrated in my initial message. As further testing, I tried to extract the NavigationStack view to a separate view (similarly to here), and to remove ScrollView or replace it with a List, but to no success. Hopefully this is helpful.
Topic: UI Frameworks SubTopic: SwiftUI Tags:
1d
vDSP.DiscreteFourierTransform failed to initialize with 5 * 5 * 2^n count
I am implementing the FFT using vDSP.DiscreteFourierTransform. According to the official documentation, the count parameter has requirements as outlined below: /// The `count` parameter must be: /// * For split-complex real-to-complex: `2ⁿ` or `f * 2ⁿ`, where `f` is `3`, `5`, or `15` and `n >= 4`. /// * For split-complex complex-to-complex: `2ⁿ` or `f * 2ⁿ`, where `f` is `3`, `5`, or `15` and `n >= 3`. /// * For interleaved: `f * 2ⁿ`, where `f` is `2`, `3`, `5`, `3x3`, `3x5`, or `5x5`, and `n>=2`. Despite adhering to these specifications in theory, my attempt to initialize an interleaved DFT with count = 2 * 2 * 5 * 5 (equivalent to 5×5 × 2²) resulted in a failure. Below is the code snippet I used for the initialization: do { let dft = try vDSP.DiscreteFourierTransform( previous: nil, count: 2 * 2 * 5 * 5, direction: .forward, transformType: .complexReal, ofType: DSPComplex.self ) print(dft) } catch { print(DFT init failed:, erro
0
0
129
1d
Received Apple Developer “Pending Termination” (3.2(f) + 5.6.2), I found a mistake and want to fix it, what should I do?
Hi everyone, I’m looking for advice from anyone who has dealt with an Apple Developer account “Pending Termination” notice. What happened Yesterday I received a Pending Termination notice for my Apple Developer account (not just a single app). This is a huge deal for me because it affects all apps under the account. The notice cites 3.2(f) and 5.6.2 (Developer Identity). It includes language like: Evidence of Dishonest or Fraudulent Activity You provided fraudulent and/or false account information, documentation, or otherwise falsely represented yourself or your submitted app to Apple either during the account enrollment process or after the account was created. What I discovered (my mistake) After the notice, I did a deeper self-audit and found something that looks bad and could be contributing: One of my apps has a supporting website built from an AI template that look like tea app, the app itself have original code. The Privacy Policy page on the website was empty, and the footer copyright name wa
0
0
252
1d
AVPlayerView. Internal constraints conflicts
I’m getting Auto Layout constraint conflict warnings related to AVPlayerView in my project. I’ve reproduced the issue on macOS Tahoe 26.2. The conflict appears to originate inside AVPlayerView itself, between its internal subviews, rather than in my own layout code. This issue can be easily reproduced in an empty project by simply adding an AVPlayerView as a subview using the code below. class ViewController: NSViewController { override func viewDidLoad() { super.viewDidLoad() let playerView = AVPlayerView() view.addSubview(playerView) } } After presenting that view controller, the following Auto Layout constraint conflict warnings appear in the console: Conflicting constraints detected: . Will attempt to recover by breaking . Unable to simultaneously satisfy constraints: ( , , , , , , , = AVEventPassthroughView:0xb33cfb480.leading + 6 (active)> ) Will attempt to recover by breaking constraint Set the NSUserDefault NSConstraintBasedLayoutVisualizeMutuallyExclusiveConstraints to YES to ha
0
0
223
1d
Strange behavior for automounted directory.
I. am working on an app that uses automounted files using nfsv4 where the server has zfs filesystems. As a test I've created a very simple example and the directory in question seems to automount correctly, but when I try to access it, I get strange behavior. The directory is mounted on is /System/Volumes/Data/mnt/subdir and I can change to that directory just fine. However I get the following: 63 rrsum@Anywhere:subdata% pwd /System/Volumes/Data/mnt/subdata 64 rrsum@Anywhere:subdata% ls -la total 3 drwxr-xr-x 3 nobody nobody 4 Jan 10 13:03 . dr-xr-xr-x 3 root wheel 2 Jan 8 17:27 .. drwxr-xr-x 2 nobody nobody 3 Jan 9 11:20 dir -rw-r--r-- 1 nobody nobody 12 Jan 10 13:09 file.txt 65 rrsum@Anywhere:subdata% cd dir cd: string not in pwd: ls The directory appears in the 'ls -la' properly, but I cannot cd to it.
0
0
233
1d
Persisting User Settings with SwiftData
I was wondering what the recommended way is to persist user settings with SwiftData? It seems the SwiftData API is focused around querying for multiple objects, but what if you just want one UserSettings object that is persisted across devices say for example to store the user's age or sorting preferences. Do we just create one object and then query for it or is there a better way of doing this? Right now I am just creating: import SwiftData @Model final class UserSettings { var age: Int = 0 var sortAtoZ: Bool = true init(age: Int = 0, sortAtoZ: Bool = true) { self.age = age self.sortAtoZ = sortAtoZ } } In my view I am doing as follows: import SwiftUI import SwiftData struct SettingsView: View { @Environment(.modelContext) var context @Query var settings: [UserSettings] var body: some View { ForEach(settings) { setting in let bSetting = Bindable(setting) Toggle(Sort A-Z, isOn: bSetting.sortAtoZ) TextField(Age, value: bSetting.age, format: .number) } .onAppear { if settings.isEmpty { context.insert(UserSetting
2
0
175
1d