While I am not new to programming, I am quite new to the Swift language. I am using the Swift Playground app on macOS 26 on an M1 MacBook Air. I am on the lesson about types. Perhaps it's a silly question, but what is a portal? It is never described or pointed out where to find it in the puzzle world. Similarly, the instructions reference a switch object without ever defining what it is. I cannot write code to call methods or set properties on objects about which I have no useful information. Can anyone advise, please? Thank you kindly.
Search results for
İOS 26 beta battery %1
250,760 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Crashlog-0916-071225.log I have an app that crashes on OSX 26 only. I have a @StateObject which is an observer of the NSColorPanel. When I call let panel = NSColorPanel.shared in init(), SwiftUI will crash - apparently with an update while view is being updated. See crash log. I was able to work around it by adding let _ = NSColorPanel.shared in my AppDelegate before SwiftUI is initialized. The exact code worked fine in all previous OSX versions.
I recently updated to macOS sequoia 15.6 Afterward, I updated to Xcode 26 The project I've been running for the last couple years no longer compiles on existing simulators and doesn't build to a physical device. I'm getting an error I'm not familiar with and have no idea how to directly resolve it: The specific error is 'Command SwiftGeneratePch failed with a nonzero exit code' Looking up this issue via Google, there wasn't really a lot of information on this particular build failure. Most suggestions were to change the location of the Derived Data folder (Xcode -> File -> Project Settings -> update location of derived data from default to relative) This was one of the only actionable solutions I found online but this doesn't fully address the issue for me, it just creates a new issue: Command PhaseScriptExecution failed with a nonzero exit code I feel like with enough digging around I should be able to find a solution to the PhaseScriptExecution issue; there seems to be a decent am
Please see the Configuring Your App to Use Alternate App Icons that uses Icon Composer files and supports iOS 18 or later. Note: The sample only uses Icon Composer files. No old icons.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Thanks for the comments/answers. I assumed that the type of file should be set by the Open as context menu. But, I now understand to use the file inspector to set the type. I still have a bit of an issue that in one of my projects, the editor aggressively suggests text completion with swift entities.
Topic:
Developer Tools & Services
SubTopic:
Xcode
As posted in the other thread Steve4442 linked to: The way to go is the following (as John Siracusa) noted on Mastodon: Name your Tahoe .icon file the same as the name of your existing .appiconset in the Assets catalog. Set the ASSETCATALOG_OTHER_FLAGS build setting to: --enable-icon-stack-fallback-generation=disabled I can confirm that the Asset Catalog Other Flags still works with Xcode 26 RC! I’ve submitted two apps with that flag and both got approved by Apple. The App Store even displays the old icon in the iOS/macOS 18 App Store and the new icon in the iOS/macOS 26 App Store. You can see an example here in one of my apps.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Just want to confirm that the Asset Catalog Other Flags still works with Xcode 26 RC! I’ve submitted two apps with that flag and both got approved by Apple. The App Store even displays the old icon in the iOS/macOS 18 App Store and the new icon in the iOS/macOS 26 App Store. You can see an example here in one of my apps. So, to summarize in John Siracusa’s words again: Name your Tahoe .icon file the same as the name of your existing .appiconset in the Assets catalog. Set the ASSETCATALOG_OTHER_FLAGS build setting to: --enable-icon-stack-fallback-generation=disabled
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
The main problem here is that sometimes the snippet view has black text on a black background and it is unreadable. To see what might be affecting this: I tried checking the colorscheme enviroment value via @Environment(.colorScheme) in my view. This usually returns the correct device light/dark mode, however it returns incorrect after device restarts or app is updated. In order to correct this, user must toggle light/dark mode in device settings. I also tried checking UITraitCollection.current.userInterfaceStyle in the perform() function of my AppIntent. This also usually returns the correct value, but does not after user toggles light/dark mode in device settings. In order to correct this, user must open the app. The idea with checking these variables was that if one always returned the correct mode, I could set the text to the correct color instead of using .primary. Neither value seems to be 100% accurate and they fail in opposite situations. Color.primary seems to align with the colorscheme envi
Topic:
UI Frameworks
SubTopic:
SwiftUI
I've instilled Tahoe and Xcode 26(17A324) and the combination is virtually unusable, particularly the latter I'm no longer able to build projects reliably. My workflow is completely disrupted by a spinning beach ball so just a warning that you might want to delay until taking the plunge as I should have done. Fortunately, I have a back sequoia machine I can use instead.
Topic:
Developer Tools & Services
SubTopic:
Xcode
I'm getting an error writing a ciImage as a heif image: // Create CIImage directly from pixel buffer let ciImage = CIImage(cvPixelBuffer: pixelBuffer, options: [CIImageOption.properties: combinedMetadata]) // Write HEIC synchronously do { try ciContext.writeHEIFRepresentation(of: ciImage, to: url, format: .RGBA8, colorSpace: colorSpace) The error I'm getting is: Error Domain=CINonLocalizedDescriptionKey Code=3 (null) UserInfo={CINonLocalizedDescriptionKey=failed to write HEIC data to file., NSUnderlyingError=0x11b1a1ec0 {Error Domain=CINonLocalizedDescriptionKey Code=10 (null) UserInfo={CINonLocalizedDescriptionKey=failed to add image to the PhotoCompressionSession.}}} Both try ciContext.writeJPEGRepresentation(of: copiedCIImage, to: url, colorSpace: colorSpace, options: options) and try ciContext.writePNGRepresentation(of: copiedCIImage, to: url, format: .RGBA8, colorSpace: colorSpace) work. I also verified that the code works with iOS 18. Is there something new we need to do for Heif images? Thanks
Topic:
Media Technologies
SubTopic:
Photos & Camera
Tags:
Mobile Core Services
Photos and Imaging
Core Image
MKMapPoint doesn’t conform to Codable so you can’t use it directly in your model. One solution is to store the coordinate properties in the model instead.
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags:
I FINALLY got a solution. I've tried everything in all the threads but this is what worked. I went to XCODE, debug, destinations manage destinations. Then I right clicked my physical device. Went to the installed provisional profiles and deleted the existing ones on my phone. Rerun the build and it worked
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
I'd encourage you all to email Apple support. I did. I made two fresh apps, tried to Macs, two iOS device all with the same results.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
stopped working is unfortunately not a problem definition that anyone can give helpful suggestions for. One needs to know: what was happening, and what is now happening in details are there any errors? What are they? have you made any changes to your code? Even if it is a small change that you don't think is relevant? have you rebuilt the app since it was working. Is it a new Xcode version? Have you changed anything with the project settings? In any case, if you have not changed anything, and the same build of the app is not behaving the same on iOS 26, our engineering teams need to investigate this issue, as this might indicate a change with iOS 26. We'd greatly appreciate it if you could open a bug report, include crash logs and sample code or models that reproduce the issue, and post the FB number here once you do. Bug Reporting: How and Why? has tips on creating a successful bug report. Important: For feedback related to a specific framework or API, select Deve
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Hi everyone - I'm seeing an issue specifically on iOS26 where we instantiate a few storyboard items programmatically and pull their restoration identifier. On iOS26, these identifiers are null and cause a crash, but the assignments are on the storyboard and there has been no change to that logic. On iOS 18, for example, there is no crash and the identifiers are pulled properly. Anybody else seeing this?