xcode github

To test the feature, you don't need the permission. You must add the Family Controls capability to your Xcode project before you can test it. You must request the permission for your app and each extension before you can distribute your app.

Did you try removing the transparent effect and see if the systems does it by itself ? Do you upload to AppstoreConnect from Xcode 26ß ?

Amazing! Thanks @superpixel! Adding the secret undocumented --enable-icon-stack-fallback-generation=disabled to the ASSETCATALOG_OTHER_FLAGS build setting does work on Xcode 26 beta 6. What I do is enable this, disable Include all app icon assets and copy a separately compiled AppIcon.incs (with the legacy icons) to the Resources folder while making sure the CFBundleIconFile is in the Info.plist pointing to this file - this results in the correct icon showing up on older macOS versions, while Tahoe uses the Icon Composer variant. This should work on macOS (not sure if works for App Store, but my app is not an App Store app, so it does not matter). An other way is to have Include all app icon assets which generates the proper variants in Assets.car, but it bloats the bundle size somewhat (especially as I have some assets that depend on build configuration and this option makes all those into the bundle) - this might be the proper way though. Hope Apple fixes this properly though or add least adds a pr

FWIW, I'm getting this on Xcode 16.4 with no Swift Package Manager. The error alert will popup in groups of 5 or 6. All the buttons just close the alert and lead to another one.

@DTS Engineer it’s a M2 pro MacBook Pro and I’m not running anything in a VM it’s all running natively. I’ve tried both stable xcode and the beta and get the same error.

[quote='854898022, Steve-Olson-1951, /thread/797142?answerId=854898022#854898022, /profile/Steve-Olson-1951'] I built a very basic test app from Xcode templates [/quote] That’s always a great diagnostic test. In this case it confirms that there’s something specific about your main project that’s causing this issue. I have some further suggestions: From the Home screen, remove your main app from the device. And then restart the device. These steps should remove any state leftover from any previous builds of the app. Do a clean build of the app. Do a Product > Run. Does it still reproduce the problem? Presuming it does, run the app from the Home screen and then do a Debug > Attach to Process. Does that work? Also, after the rebuild in step 3, choose Product > Show Build Folder in Finder, then navigate to the Debug-iphoneos folder and, in Terminal, run this command: % codesign -d --entitlements - MyApp.app … [Dict] … [Key] get-task-allow [Value] [Bool] true As this code is Development signed, y

Yeah, this is definitely bugworthy. Dinisan, I’d appreciate you filing a bug about this, and then posting the bug number here, just for the record. Given these: func stepForward(_ input: Int) -> Int { input + 1 } func stepBackward(_ input: Int) -> Int { input - 1 } then these two fail: func chooseStepFunctionNG1(backward: Bool) -> (Int) -> Int { backward ? stepBackward : stepForward } func chooseStepFunctionNG2(backward: Bool) -> (Int) -> Int { backward ? stepBackward(_:) : stepForward(_:) } but these three succeed: func chooseStepFunctionOK1(backward: Bool) -> (Int) -> Int { if backward { stepBackward } else { stepForward } } func chooseStepFunctionOK2(backward: Bool) -> (Int) -> Int { backward ? (stepBackward as (Int) -> Int) : (stepForward as (Int) -> Int) } func chooseStepFunctionOK3(backward: Bool) -> (Int) -> Int { let result = backward ? stepBackward : stepForward return result } The gating factor seems to be type resolution with function types between the func

Hello @DTS Engineer, No, this is definitely not expected Since you answer was specifically quoting iOS 18 and iOS 26 beta 4, what about the older iOS versions? If the behavior expected on those versions? I am curious how you confirmed the behavior though. I have confirmed this behavior by returning a custom NSTextLayoutFragment subclass in NSTextLayoutManager's delegate method textLayoutManager(_:textLayoutFragmentFor:in:). The layout fragment subclass then executes a print statement in its draw(at:in:) method override. Do you have a test project that unveils the issue to share? I just created a demo project for you. I've attached it to my feedback report, but I've also uploaded it to GitHub: https://github.com/galijot/NSTextLayoutFragment-PerformanceIssues I've faced slightly different results today on iOS 17 in this demo project, where just the 2nd paragraph's draw(at:in:) would be called on every scroll step, and other paragraphs would be rendered once per its appearance in the viewport. iOS 18 st

I tried using isSimulatedBySoftware and tested with tools like iMyFone/iTools to simulate the location, but the property still returned false. So I’m not sure if I did something wrong. From what I’ve read https://developer.apple.com/documentation/corelocation/cllocationsourceinformation/issimulatedbysoftware , it seems that isSimulatedBySoftware only works when running and debugging with Xcode.

I tried using isSimulatedBySoftware and tested with tools like iMyFone/iTools to simulate the location, but the property still returned false. So I’m not sure if I did something wrong. From what I’ve read https://developer.apple.com/documentation/corelocation/cllocationsourceinformation/issimulatedbysoftware , it seems that isSimulatedBySoftware only works when running and debugging with Xcode.