Same here. AW Series 4 cellular. Used to end day on watchOS 6 with 30% remaining. Now I can’t get to 4 PM before my watch dies; consistent usage pattern. Something is seriously wrong with watchOS 7. Battery drain makes the hardware unusable for intended purposes.

Follow up. With my S4 cellular, an unpair/pair cycle has worked around the battery drain issue. Battery usage on watchOS 7 is now where it was for me on watchOS 6. The downside is that the unpair/pair has played havoc with my VO2 max estimates in the Health app. My estimate dropped by 7 units overnight across the unpair/pair cycle. To say that this is frustrating after 5 months of solid training for me as a runner is disappointing. I get enough grief from my fellow runners for not wearing a Garmin and this experience has not created a lot of faith for me in Apple’s watchOS software quality. 😕

This occurred for me using Xcode 12.5 on an M1 Mac mini. The solution in my case was to ensure that Xcode was opened without using Rosetta. To check for this, select Xcode in the Finder in your Applications folder, then press Command-I. Under the General section of the Info dialog that appears, ensure there is no checkmark beside the "Open using Rosetta" option. Then close and re-open Xcode, and try building your application and running within the Simulator again. In my case, this resolved the appearance of the errors described by the original poster.

Yes, I'm seeing this issue too. I thought it was a macOS Monterey beta 3 issue, but now I'm seeing Spotlight at high CPU when running the simulator in Xcode 13 on Big Sur 11.4.

@dokun1 I was able to get this working by using this tutorial, which seems to register the fonts via Core Graphics, as you've suggested: Packaging your Custom Fonts in Swift Packages by Jacob Rakidzich https://jacobzivandesign.com/technology/custom-fonts-from-swift-package/