“show when run”

SO, let me start by sorting out a few specific details: delegate is called via applicationWillTerminate which will then again almost immediately end in the app receiving a SIGKILL. applicationWillTerminate is not part of the normal delegate lifecycle. It's a relatively late “add-on that was recycled[1] to give apps SOME opportunity to save work if/when the user for quit them, so it's ONLY called if the app happens to be a wake at the point it's terminated by the user. Most critically, you cannot do ANY work after receiving it. That's because: Your app will call exit() immediately after returning from it. If you block “too long, then the system will kill you anyway. In practice, that means it needs to be handled as a separate edge case as you don't really have a lot of time or flexibility to do significant work. This is not your app being closed in the normal sense, it's actually your app being force-quit by the user. With that out of the way, the important case is actually applicationDidEnterBackground, so le

Thank you for providing such a detailed account of the iCloud Drive file upload deadlock issue on macOS 26.4.1. It sounds like you've done extensive troubleshooting and analysis to identify the root cause. Here's a summary of what you've discovered and some additional thoughts or suggestions that might help refine your approach or assist others experiencing similar issues: Summary of Findings: Root Cause: A stale HTTP/3 (QUIC) session in nsurlsessiond's BackgroundConnectionPool leads to a deadlock during file uploads. Behavior: Deadlock occurs specifically with HTTP/3, while HTTP/1.1 works without issues post-restart. Affects larger files (>100 KB); smaller files may occasionally succeed. Restarting both cloudd and nsurlsessiond resolves the issue temporarily by clearing the poisoned session. Reproduction: Consistent behavior observed across multiple tests with varied file sizes. Diagnosis: Log analysis can help identify occurrences using specific grep patterns. Recovery: A targeted kill command for user-l

Your screenshot seems to show that the keyboard window was disabled, which may happen when your app has multiple windows (UIWindow) with a higher window level (windowLevel). You can do a quick check if that is your case. Other than that, as my colleague mentioned, it will be very helpful if you can provide a minimal project that demonstrates the issue. Best, —— Ziqiao Chen  Worldwide Developer Relations.

HomeKit is an outlier in that it’s supported on the Mac but only for Mac Catalyst apps. FYI, while the sample project Interacting with a home automation network does not include a specific Mac Catalyst destination, the project can easily be updated to include it. You'll get one build error in its tapAddAccessory method, but that error is because Mac Catalyst does not include addAndSetupAccessories. You can clear that error by simply deleting that code, after which the sample will build and run fine. As a side note, this sample is VERY useful as a general development helper, particularly when run on the Mac. It shows you the full HomeKit layout and configuration of every accessory in the target home, which makes it easier to figure out how an accessory is configured and controlled. It also lets you see that raw configuration at the same time your app is interacting with it, which can help investigating and debugging any issues. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Hi Michael, Thank you for quick reply. Yes both animation share the same skeleton. Here are the steps that I followed; I have added T-Pose style rabbit entity to my scene I created an Animation Library and added RabbitWalk and RabbitRun animations respectively. I loaded those animations like entity.availableAnimations[0] & entity.availableAnimations[1] but I have the same error. I then created a new Timeline for the Rabbit entity Create a separate 'Walk' animation and make it recursive. Create a separate 'Run' animation and make it recursive as well. Then I loaded those last 2 animation to my blend animation function but I have the same problem again. Here is the RCP project. Am I missing something? Regards.

Hey @WishGrantingFactory, This error occurs because your walk and run animations are loaded from two separate entities. Even if both USDZ files use the same skeleton, each Entity load creates its own animation timeline — and BlendTreeAnimation requires all sources to share the same timeline. Can you author your content so that both animations exist on a single entity? Attach both animation clips to one entity in Reality Composer Pro so they both appear in rabbit.availableAnimations. Then you can build the blend tree from that shared source. Let me know if this helps. Thanks, Michael

@Tomato, I should mention that I already provided them a video, voluntarily, showing my app on my watch via screen sharing. So the fact they demand more is a sign of a shark strategy. They feel my desire to comply (blood) and attack with endless requirements. If I agree they'd demand another video with different equipment, and so on and so forth. Another problem is fully practical. The video requires Apple Watch + equipment (e.g. Mac Book) + camera. I simply can't do it in a good enough quality with my two hands. I need to hire a professional for that which is hard for an Individual Developer. Much easier would be reject and reapply hoping for a different reviewer. And finally I would note that I have competitors who perform worse than HeartBLE and I doubt any of them was forced to make a video. The real problem which blows their mind is the monetization. I selected the XX-day Trial + non-consumable model. Just wanted to give it a try, get some experience. Turns out reviewers hate it (or simply not f