Well, I'm not Apple, but I think it is unlikely that you'll ever hear a reason for their design decisions. What you'll usually hear is that if you want a feature, use the Feedback Assistant to request that feature - outline your use case, what you can do, what you can't do, why you would like to be able to do it. Often, decisions like these are made to improve the overall user experience of the phone; it is quite easy to drain the battery rapidly if you leave. video recording on inadvertently. You may contend that the user should be made the final arbiter in this decision (it's my phone, and I'll drain the battery if I want to!), and that is so on other platforms, but this is Apple's design and Apple make the rules.

I might be completely wrong here, but it looks like you can do this line differently connection = NWConnection(host: host, port: port, using: .udp) the last parameter doesn't need to be fixed as .udp, the default udp parameters. You can make new NWParameters and alter the value of requiredLocalEndpoint. hth, and Happy New Year

Your code wouldn't compile as-is, but I think you want your GradientLegendView to slide in from the leading edge, and out on the trailing edge of the ContentView, in response to pressing a button. And you don't want to animate the isShowingLegend variable, you'd rather attach the animation to your GradientLegendView. The thing is, what you want to animate (the position of the GradientLegendView) isn't intrinsic to the GradientLegendView. The view position is a property of the GradientLegendView which only makes sense in the ContentView. I took the .transition modifier out of the GradientLegendView, and removed its isShowingLegend. The GradientLegendView is the thing which shows the gradient legend; it doesn't make sense for it to take that bool parameter. The piece of UI which uses the GradientLegendView decides whether to show it or not. I attached a .transition(.slide) to the HStack which builds your GradientLegendView, and provided a .animation controlled by isShowingLegend. The animation is applied to a Group in your overlay. The Group returns an HStack if isShowingLegend is true and an (implied) EmptyView otherwise. It is necessary because the type of the parameter to .overlay should be some View. this is my ContentView     @State private var isShowingLegend = true     var body: some View {         Button("Press Me") {             isShowingLegend.toggle()         }          .frame(maxWidth: .infinity, maxHeight: .infinity)         .edgesIgnoringSafeArea(.all) //        .task { //          setupMenuItems() // won't compile, don't have //        }         .overlay(             Group {                 if isShowingLegend {                     HStack {                         GradientLegendView(                             // doesn't need isShowingLegend                             labels: SampleData.createHeatmapLegendLabelArray(),                             colors: SampleData.createHeatmapLegendColorArray(),                             width: 120,                             height: 200)                         Spacer()                     }                     .transition(.slide)                 }             }             .animation(.easeInOut, value:isShowingLegend)           ,           alignment: .bottom         )     } } I don't know if this is what you are looking for (or were looking for, because it has been two weeks!), but I hope it helps. This is a pretty good article about transitions https://www.objc.io/blog/2022/04/14/transitions/ And I found this tutorial very useful also https://www.hackingwithswift.com/books/ios-swiftui/creating-implicit-animations

at the top of your file, change #include "fmt/core.h" to `#define FMT_HEADER_ONLY #include "fmt/format.h"` that worked for me. I found the magic ju-ju on Stackoverflow, if you search for "How to use fmt library in the header-only mode?" you should see the answer I found. If this forum allows direct links, it is here: https://stackoverflow.com/questions/66944554/how-to-use-fmt-library-in-the-header-only-mode

when you record a video, is the phone using the same field of view as for a still picture?

the code you have posted does not compile - ContentView5 and Tutorial are missing. The PreviewProvider is missing - usually this builds your ContentView, but for some reason you have a ContentView100. It would be easier to read your code if you posted inside a code block (see the little icons at the bottom of the Your Reply pane). Try again and maybe someone can help you out!

In my development version, the delivery app has embedded.provisionprofile. The dext contains embedded.mobileprovision. In my release version, the delivery app has embedded.provisionprofile. The dext has both embedded.mobileprovision and embedded.provisionprofile.

there's a good chance that no-one from Apple will see this or take action on it. You should file a bug using Feedback Assistant, at least those are tracked, while this forum is not.

in Xcode, go to View/Navigators/Reports. (the navigator is the panel on the left, which can be closed. The Report navigator can also be chosen by the rightmost button at the top of this panel). Click the build log. On the right, the log will open. You'll see a Link stage near the end of the log. Select that stage, and a little icon will appear at the end of the line you have just highlighted. You can click that to expose the detailed link log.

In Xcode, select the dext target, then under Signing, you should see a section labelled "DriverKit", with a Provisioning Profile: which you cannot modify, called "Xcode Managed Profile". If you click on the (i) here, does everything seem as you expect? You should see some capabilities, and some entitlements. Do they all have tick marks? Find your app in the Derived Data folder, and drill down to the dext, and look at its .embeddedprofile (QuickLook should open it for you, just use the space bar). Does it look correct? Follow the advice from Quinn here https://developer.apple.com/forums/thread/656490

first question I have is "do you really need a driver"? If your device provides a service which is only useful to one application, a driver may be inappropriate or unnecessary, particularly if the interface is USB. In addition, kexts are being replaced by dexts, so even if you need a driver, that driver may not need to be in the kernel (or at least, not the parts that you write). I would advise you to use os_log(OS_LOG_DEFAULT, ) to begin with. To view the logs, use the Console app and filter on some unique string in your message (I like to use "XXXX"). This is primitive but there are less things to go wrong. You can also filter on "com.apple.driver.IOKitTest" to find all strings logged from your driver or about your driver. You can also use the command-line interface to the ASL (Apple System Log), log. It has a very long man page which refers to an even longer piece of documentation about how to build the predicates used for --predicate. It is so complicated I rarely use it. See https://developer.apple.com/documentation/os/logging/viewing_log_messages?language=objc

this isn't really a developer question, you would have more luck asking this on the support forums. You could get an external keyboard with a media eject key, then you can use the shortcuts listed here https://support.apple.com/en-us/HT201236. Or, hold down the Touch ID/power button until the machine shuts down. Or, just close the lid and let the Mac sleep. Unlike Intel Macs, M1 Macs keep their charge for quite a while in sleep.

I also spent weeks battling signing issues. If you're using Xcode 14, you can simply select "Automatic" in the Signing and Capabilities tab. As it says in that tab, "Xcode will create and update profiles, app IDs and certificates". Choose "Development" for the signing certificate. Delete any app IDs or profiles you may have made manually on the developer portal for your app or its extension, and let Xcode do all the work for you. If you don't, Xcode will try to use the manually generated profiles and you'll get a message like "Xcode 14 and later requires a DriverKit development profile enabled for IOS and macOS. Visit the developer website to create or download a DriverKit profile". Automatic signing will let you develop and test on your own machine, or any other test machine entered on the portal under Devices. You asked "Does the Code Signing Identity/Profile in the Apple Developer section need to match exactly, or can that have more than what is requested? " If you look at the embedded profile that Xcode puts in your app, you'll see what it creates (for development). It looks at the entitlements you request, and puts those same entitlements in the profile. In my case I have a com.apple.developer.driverkit.transport.usb entitlement which specifies my company's USB vendor ID. The development embedded profile specifies "*" as the vendor ID, the distribution profile specifies my company's VID. When you come to distribute your app, Xcode can't create everything for you. The Account Owner has to go into the portal and create profiles for any extensions which require managed capabilities (entitlements which are only provided in response to a specific request to Apple). An Admin can create other types of profiles. If you are not the Account Owner the Generate button will fail to generate a profile, but it won't tell you why. In the distribution workflow, you choose the manually-generated profiles when you come to upload your product for notarization (not at build time). So you can keep the "Signing and Capabilities" setting in Xcode at Automatic.

well, that looks like a fun application! Aren't you just seeing normal lens vignetting here? The image plane of the original film camera was evenly illuminated by the original lens (film cameras can't compensate for lens vignetting). The adapter interposes elements between that image plane and the iPhone's lens, such that light falling on the periphery of the plane follows a much different path than light falling on the center of the plane. You can and should compensate for the difference in image brightness in software.

In Xcode, choose File/New... Project. From the template chooser, select macOS, Application, Command Line Tool. Click Next give it a name (maybe "hello") choose C++ from the language popup click Next choose where to save your project Xcode will open the project and it will have a starter main() routine. Xcode help is here https://developer.apple.com/documentation/xcode This will get you started. After that, this forum, and the Internet in general, is your friend. Most of the differences between Mac and Windows are in the application and system frameworks and APIs. But you'll face an uphill struggle with programming on the Mac if you insist on using C++, because most of the APIs are Objective C or Swift, and some of the new frameworks are Swift-only.