what do you expect to see in the debugger? The view is shown, the layer isn't. What is the problem in your code that you are trying to debug?

this should get you started https://developer.apple.com/documentation/coreimage/cifilter/3228262-qrcodegenerator

0xe00002c7 is kIOReturnNotSupported (from IOReturn.h). You're trying to open four objects, none of which support that operation. I have had more success using IOServiceNameMatching, and giving the driver a unique name (call SetName in your dext, before RegisterService). This way you should make only one attempt to open your driver through its user client. Also, make sure you actually implement NewUserClient_Impl in your dext.

this sounds like the user of a custom URL scheme. https://developer.apple.com/documentation/xcode/defining-a-custom-url-scheme-for-your-app or do you have something else in mind?

can you check the request.identifier in your request:didFinishWithResult handler?

the feature is available in macOS Sequoia 15.1.1, accessible from the little menu bar icon which shows whether effects, reactions and so on are turned on. What OS are you running, and where are you looking for the facility?

This is a forum for questions about development of software on Apple platforms. Please don't clutter it. For customer support, visit https://support.apple.com For feedback, visit https://www.apple.com/feedback/

You're using a third-party tool and you're new to iOS development, so your way ahead is likely to be a little rocky. I suggest you start by examining the built app bundle on the Mac, see if its plist, its resources and the error messages from Xcode are self-consistent. The Info.plist you posted here doesn't look like an Info.plist in an iOS app bundle - your file is plain text, Info.plist files are xml. Then, on the Mac, in Xcode, build an iOS app from the template and try to send that to Test Flight. Understand the requirements for icons files and how they are fulfilled. Compare what is built by Xcode, the first-party tool, with what your tool is building.

Feedback Assistant is the place to report bugs.

I don't know. I tried your example, and with and without the HStack (and its accompanying braces, of course), I get the same result, the one you expect. Xcode 16.1, macOS 14.7.1, built for macOS and iOS simulator.

On my (real) M1 Pro MacBook Pro with macOS 14.7.1, it looks like this. What machine are you running your VM on?

this forum is for questions about software development. Your question would be better suited for https://discussions.apple.com/welcome option-W produces upper-case sigma (Σ). There doesn't seem to be a direct keyboard entry for lower-case sigma (σ). Type "language" into search field of System Settings, look for "Language input methods", select it, and turn on "Show input menu in menu bar". If you have only one input method, you'll still have access to the Keyboard Viewer and Character Viewer from there. You could also try enabling the Greek keyboard. On a US keyboard, sigma is on the key labelled 'S'. You can switch between keyboard input languages using the icon in the menu bar, or ctrl-space bar.

I think you can just make a codeless kext with a plist like this one: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>CFBundleDevelopmentRegion</key> <string>English</string> <key>CFBundleIconFile</key> <string></string> <key>CFBundleIdentifier</key> <string>com.apple.driver.AppleUSBHub1009</string> <key>CFBundleInfoDictionaryVersion</key> <string>6.0</string> <key>CFBundleGetInfoString</key> <string>1.0, Copyright © 2011 Apple Inc. All Rights Reserved.</string> <key>CFBundlePackageType</key> <string>KEXT</string> <key>CFBundleShortVersionString</key> <string>1.0.0</string> <key>CFBundleSignature</key> <string>????</string> <key>CFBundleVersion</key> <string>1.0.0</string> <key>IOKitPersonalities</key> <dict> <key>Hub1009</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.driver.AppleUSBHostMergeProperties</string> <key>IOClass</key> <string>AppleUSBHostMergeProperties</string> <key>IOProviderClass</key> <string>IOUSBHostDevice</string> <key>idProduct</key> <real>1544</real> <key>idVendor</key> <integer>1234</integer> <key>IOProviderMergeProperties</key> <dict> <key>kUSBWakePortCurrentLimit</key> <integer>1100</integer> <key>kUSBSleepPortCurrentLimit</key> <integer>1100</integer> <key>kUSBHubPowerSupply</key> <integer>1300</integer> </dict> </dict> </dict> <key>OSBundleLibraries</key> <dict> <key>com.apple.iokit.IOUSBHostFamily</key> <string>1.01</string> <key>com.apple.kpi.iokit</key> <string>10.4.2</string> </dict> <key>OSBundleRequired</key> <string>Root</string> </dict> </plist> I added a tiny amount of code. My driver is a subclass of IOService, and overrides Start(), just so I can see it logging. I think, but have not checked, that the AppleUSBHostMergeProperties driver returns an error from its Start (but first merges the properties). The downside of course is that dexts are not loaded until after boot time, so your dext usually has no effect because the system has already loaded a driver for the hub by the time your dext is available. If you plug the hub in after boot time, the codeless dext will be instantiated. (FB12048885)

maybe (and I haven't tried this, we just put up with the hiccups) xcodebuild -checkFirstLaunchStatus and if you're okay with agreeing without reading: xcodebuild -license which are documented at the end of xcodebuild's man page.

I don't remember it being complicated at all. Using the Mac is no different than using an Intel Mac, but often noticeably faster. Building for Apple Silicon is completely automatic for new projects. For existing ones you may have to change one Build Setting (Architectures). You can build for Apple Silicon on Intel, just as you can build for Intel on Apple Silicon, so really nothing changes here. If you're asking about changes required to software source to support Apple Silicon, they're detailed here: https://developer.apple.com/documentation/apple-silicon/porting-your-macos-apps-to-apple-silicon