missing package product

Update: As far as I see, the problem lies behind sending input-push-channel in apns body at production environment. Whenever I send this, it migh work once a day or so. Otherwise it never delivers to the client. When I remove it, it just works everytime. Is there a thing I am missing here. It works fine in development environment.

Phew, I already feel bad asking you again 😅 It turns out that MTE and Malloc Stack Logging cannot be enabled at the same time. But I've tried to enabled Malloc Stack Logging, and then get delayed crash somewhere else. Unfortunately, I didn't really understand where/what to look for in Xcode. I tried to hit the 'Memory Graph Debug' but then the crash context seemed to get lost... most likely I am doing it wrong... A little context of our app: An UIPageViewController where you can swipe left/right to see the next/previous image. An UIViewController that has a TileImageView subview TileImageView that shows an image. This view is using CATileLayer. When draw(rect:) is called for a specific tile, we either show a cached tile or send a network request to a local server for the tile data. When the network response is received (callback in draw(rect:) we call the view's draw(rect:) to update with tile. Now if I scroll through the pages the crash may occur. As stated before this code was working fine before

[quote='868298022, bims, /thread/806594?answerId=868298022#868298022, /profile/bims'] Looking at the ips-file I found that it does not show the finding that Xcode show [/quote] Right. Xcode has MTE smarts beyond what the human readable crash report shows. To see the underlying data, open the JSON crash report and search for memoryErrorReport. With some reformatting you get this: memoryErrorReport : { faultAddress:0x0c00000d9de112c0, blamedAllocation: { size:48, allocationTrace:…, deallocationTrace:…, isFreed:true, address:0x0c00000d9de112c0 }, errorType:use-after-free }, The allocationTrace and deallocationTrace backtraces need further massaging. I did a hack-ish job of that and have included the results at the end of this post. I wanted the JSON crash report so that I could run it through some internal tools. I was able to do the first part of that today. I was hoping it might point me at some known bugs. It did, but those were resolved a while bug and thus are unlikely to be the cause of this issue. Unfortu

There is no development yet, the Apple review team has always stated that they will look into it, but no one has made any definitive information or statement yet. I lost a lot of users in my projects that I worked on for years, I am sorry about this situation... I sent an e-mail, created a review request for closed accounts, and opened a topic in the forum. I tried almost all the methods but the team ignored me.

[quote='868376022, DTS Engineer, /thread/809171?answerId=868376022#868376022'] To be clear, you specifically meant: /Applications ...not the standard Applications directory? That's not actually one of our standard directories, which opens the possibility that the system missed the existence of the app, so it wasn't registered with LaunchServices. [/quote] The Launch Services Programming Guide says that A built-in background tool, run whenever the system is booted or a new user logs in, automatically searches the Applications folders in the system, network, local, and user domains and registers any new applications it finds there. The one in the user domain is ~/Applications. Also note that the Finder gives that one the standard Applications icon, whereas if you create an Applications folder in some random location, it gets a generic folder icon. So at least by some measures it is one of your standard directories. I'll see if I can replicate in a VM.

in my ~/Applications folder. To be clear, you specifically meant: /Applications ...not the standard Applications directory? That's not actually one of our standard directories, which opens the possibility that the system missed the existence of the app, so it wasn't registered with LaunchServices. That shouldn't necessarily matter (you did tell the system where the app was...), but that would explain this: Dang, now all of a sudden it's working. If this was caused by a registration, then having this work: P.S., I find that if I instead use the ancient but not deprecated function LSOpenFromURLSpec, then it works. So at least I have a workaround. ...would have also registered the app. That leads to here: Obviously I need to do a lot more testing. As a general warning here, if you're going actively test this sort of thing, my recommendation would be to use VM. The problem here is that the architecture of LaunchServices means that its interactions with it tend to self correct problems. If your goal is to

@DTS Engineer bumping to not lose eyes

Hi Kevin, I have filed the bug report as requested. The Feedback ID is FB21256805. I've included the IORegistry dumps showing the missing keys when using the standard API versus the successful injection using the SetProperties workaround. To answer your specific question: Are you sure you're setting all of the required key set, particularly 'kIOMaximumSegmentByteCountWriteKey'? Yes. We confirmed that kIOMaximumSegmentByteCountWriteKey was correctly set to 65536 (64 KB), and kIOMaximumSegmentCountWriteKey was set to 129. Thanks again for your help in narrowing this down. Best Regards, Charles

Hi @DTS Engineer and thanks :) I hope that your boss will get you a iPhone 17 😅 I'm trying to attach the ips-file again. I added the.txt extension to make it possible to attach it. I hope it will not screw up and make it an inline text-box when I git 'Reply' 😬 Looking at the ips-file I found that it does not show the finding that Xcode show, e.g., Thread X: Use of deallocated memory but it then misses Memory allocated by Thread 1 and Memory deallocated by Thread 1, so I am not sure the ips-file is that useful for MTE :( CrashReport-2025-11-28-141148.ips.txt

This is tricky. My best guess is that translationTask(_:action:) is missing all the magic concurrency decorations required to make this work nicely. To get this to build right now you can mark the closure as sendable, like so: .translationTask(configuration) { @Sendable session in do { try await session.prepareTranslation() } catch { // Handle any errors. } } This compiles in Xcode 26.1 using the Swift 6 language mode and: Approachable Concurrency enabled Default Actor Isolation set to MainActor Note I’m using prepareTranslation() in my examples because it’s simpler, and that makes it easier to focus on the core issue. The drawback to this is that you can no longer access main-actor-isolated state from the closure. You can work around that using MainActor.run(…): try await session.prepareTranslation() … no isolation … await MainActor.run { … main-actor isolated … } Clearly this is less than ideal and I encourage you to file a bug against… actually, I think it’d be best to file a bug against the Trans