Are Mac Catalyst apps subject to the same code signing requirements and associated distribution restrictions as iOS/iPad apps? I wrote a small Catalyst app on my laptop and was not able to run the resulting binary on another Mac, it crashed with a code signing error and I had to recompile it on the target computer. I also assume that binary will stop working after a short period of time and require re-signing. I was hoping Catalyst apps would have the less restrictive Mac app requirements but it doesn’t appear so, and I would need to pay $99 to create a binary that stays usable indefinitely.

I recently updated my HomePod mini to version 16.3, which enables the temperature and humidity sensors. However, in the HomeKit iPad app I've developed, the HomePod mini does not show up in HMHome.accessories. I expected it show up there with a service of type HMServiceTypeTempatureSensor.

Updated version of this post My HomePod mini is now on version 16.4, so the the temperature and humidity sensors are enabled. The data properly shows up in the Home app on my various devices. In my HomeKit iPad app running on Mac Catalyst, however, the data does not show up. I would expect the HomePod mini to show up in HMHome.accessories with a service of type HMServiceTypeTempatureSensor. I see all of my other HomeKit accessories, just not the HomePod mini. I have tried with the latest Xcode (14.3) and highest available iOS Target and Minimum Deployment (16.4), macOS version 13.3. I have not, as of this writing, upgraded my HomeKit architecture, however. Note that I haven't tried the app on an actual iPad (and the iOS simulator doesn't expose my HomeKit environment.)