“eskimo”

[quote='889751022, Madhuri_Ramapure, /thread/826318?answerId=889751022#889751022, /profile/Madhuri_Ramapure'] Kindly, please check attached files, we implemented same thing in native app. [/quote] I’m sorry but the above is not an answer to the questions I posed earlier, and without that it’s hard to make progress on this issue. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

It’s hard to investigate Swift concurrency problems without knowing more about your build environment, so I tried reproducing this here in my office: Using Xcode 26.5, I created a new project from the iOS > App template. I changed it to use the Swift 6 language mode. I changed ContentView.swift to this: import SwiftUI /* @preconcurrency */ import DeclaredAgeRange struct ContentView: View { @Environment(.requestAgeRange) var requestAgeRange var body: some View { VStack { Button(Test) { Task { do { let response = try await requestAgeRange(ageGates: 13, 15, 18) // ^ // Sending value of non-Sendable type 'DeclaredAgeRangeAction' risks // causing data races // // Sending main actor-isolated value of non-Sendable type // 'DeclaredAgeRangeAction' to @concurrent instance method // 'callAsFunction(ageGates:_:_:)' risks causing races in between // main actor-isolated and @concurrent uses print(response) } catch { } } } } .padding() } } #Preview { ContentView() } I think this accurately reflects the error you’re seei

You’ve written this like a bug report. Did you also file it in Feedback Assistant? If not, please do. That’s way to get this in front of the relevant folks. And either way, please post the bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Right. The cases of this that I’ve seen have all been related to that issue, where the system attributes a plug-in using Rosetta to the app itself. If you see this in the 26.6 beta, please let us know. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

My usual response to a post this would be to recommend that you make it official by filing an enhancement request. In this case, however, you might wanna wait a week to see what WWDC26 brings. If there’s new stuff, you can evaluate that before filing your ER. And if there isn’t, you’ve only ‘lost’ a week. If you do file an ER, please post your bug number here, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

My experience is that problems like this, where it’s being seen by a tiny fraction of users, are caused by issues on the device rather than issues with your code. That limits your ability, as an app developer, to investigate the problem. And it also raises the question of exactly how much user-level support that you want to do? There are a variety of steps that a user in this situation might take to try to resolve this issue. These range from the simple (disable and re-enable Face ID) to the extreme (backup, erase the device, restore). You have to decide what you’re comfortable trying to talk them through, and what you want to leave to them, or Apple Support. Regardless, it would be super helpful if you were able to capture a sysdiagnose from the affected device before trying to resolve the issue. You could have the user capture that and send it to you, or have them report a bug in Feedback Assistant directly, which adds the sysdiagnose log, and then just pass you the bug number. [quote='828317021, VaibhavSah

Hi, eskimo, I have posted a bug with sysdiagnose logs and crash log. The bug number is FB22904017. By the way, it's my first time to know how to collect sysdiagnose logs 🤦🏻‍♀️. By the way, I learn a lot from yours articles like An Apple Library Primer, Implementing Your Own Crash Reporter and so on. Does has any way to get all your articles like above?

[quote='889650022, Fushj, /thread/783701?answerId=889650022#889650022, /profile/Fushj'] Here a .ips file from user [/quote] Thanks! Sometimes an JSON (.ips) crash report allows me to find existing bug reports associated with the crash. Sadly, that didn’t pan out in this case. [quote='889650022, Fushj, /thread/783701?answerId=889650022#889650022, /profile/Fushj'] I can reproduce the crash, but it doesn't always happen [/quote] OK, that means you’re doing better (well, worse :-) than anyone else in this thread. And I think that warrants you filing a bug about this. Make sure to: Reproduce the crash. Immediately trigger a sysdiagnose log. Attach that to your crash report. Note For more about sysdiagnose logs, see our Bug Reporting > Profiles and Logs page. Once you’re done, please post your bug number here so that I can add my own (internal) comments to it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='889666022, goekhanbl, /thread/824550?answerId=889666022#889666022, /profile/goekhanbl'] I would appreciate it if Apple engineering [/quote] It’s unlikely that anyone from the relevant engineering team will see your post here on the forums. The best way to ensure that happens is to file a report in Feedback Assistant. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The setup you’re proposing is probably feasible but I’d definitely considering it to be ‘fighting the framework’ (well, fighting the developer tool). Is there a specific reason you need to build the app’s executable separately from the app bundle? Why not build the executable from source? That is, merge steps 2 and 3? That’s how most Xcode projects work and it’s very much the well trodden path. And that means that certain Xcode functionality expects things to work this way. For example, if you tried to do this by creating a generic bundle target and placing your pre-built executable in that bundle, you’ll miss out on a bunch of cool app-specific functionality, most notable the stuff in the Signing & Capabilities editor. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Yeah, that’s a very dark and dusty corner of macOS. I have links to some info in this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='828197021, Macho Man Randy Savage, /thread/828197, /profile/Macho+Man+Randy+Savage'] But also when I set the queue the system yells at me anytime I make a change to NSMetadataQuery that alters the query. [/quote] Can you be more specific about what “yells at me” means? What are the actual symptoms here? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='889533022, ShaddamIV, /thread/828110?answerId=889533022#889533022, /profile/ShaddamIV'] But I will check from the terminal to see if I can get more infos. [/quote] Cool. I look forward to the results. [quote='889533022, ShaddamIV, /thread/828110?answerId=889533022#889533022, /profile/ShaddamIV'] macOS should have a way to uninstall an app for real [/quote] As I mentioned above, this is technically challenging, but if you’d like request this officially I recommend that you file it in Feedback Assistant. Please post your bug number, just for the record. [quote='889533022, ShaddamIV, /thread/828110?answerId=889533022#889533022, /profile/ShaddamIV'] macCatalyst app are sandboxed [/quote] Just to be clear, Mac Catalyst apps don’t have to be sandboxed. Rather, the Mac App Store requires sandboxing. And macOS gives you the option to distribute directly using Developer ID signing. However, I can understand why folks choose to ship their app on the Mac App Store, so your point is well taken in general. Share a

Thanks for the update. I’ve been chatting with various engineering teams about your issue. They believe that you’re hitting a known bug. Originally I was skeptical of that conclusion because you wrote: [quote='828136021, vince-zheng, /thread/828136, /profile/vince-zheng'] The only known way to recover so far is to erase all content and settings [/quote] which isn’t a good match for the bug they’re talking about. However, in your latest message you wrote: [quote='889526022, vince-zheng, /thread/828136?answerId=889526022#889526022, /profile/vince-zheng'] Yesterday, the device appeared to recover temporarily, but the same issue occurred again afterwards. [/quote] which is much like what we’d expect. Anyway, your bug is now marked as a duplicate of an internal bug tracking this problem. The fix for this is not in any shipping or seeded releases of iOS. If and when that changes, our bugs folks should notify you via your bug. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let m

Let’s focus this discussion on your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com