从xcassets加载图片到NSImage报错：需传入NSImage.Name类型

Hey there! Let's sort out that frustrating image loading bug in your macOS menu bar app. The error you're seeing happens because NSImage expects an NSImage.Name type rather than a raw String, and there are a few easy fixes to get your logo from xcassets loaded correctly.

Step 1: Use the Correct NSImage Initialization Syntax #

The most straightforward fix is to explicitly convert your string to NSImage.Name using its raw value initializer. Here's how to do it safely with optional binding:

import AppKit // Don't forget this at the top of your file!

guard let logoImage = NSImage(named: NSImage.Name(rawValue: "logo")) else {
    fatalError("Failed to load 'logo' from xcassets — double-check the asset name!")
}
// Use logoImage for your menu bar icon

Alternatively, since NSImage.Name conforms to ExpressibleByStringLiteral, you can often pass the string directly if your Swift version supports it. If that was throwing errors before, double-check you've imported AppKit (it's easy to forget when working on menu bar apps!).

Step 2: Verify Your XCAssets Setup #

Even with correct code, the image won't load if your asset isn't properly configured:

• Double-check the asset name in xcassets matches exactly what you're using in code (capitalization matters here!)
• Ensure the logo asset is marked for macOS (you can set this in the Attributes inspector when selecting the asset)
• Confirm the asset is included in your app target: Go to your target's Build Phases → Copy Bundle Resources and make sure your xcassets file is listed.

Step 3: Handle Framework or External Bundle Scenarios #

If your xcassets are stored in a framework instead of the main app bundle, you'll need to specify the bundle explicitly:

guard let frameworkBundle = Bundle(for: YourFrameworkClass.self),
      let logoImage = NSImage(named: "logo", in: frameworkBundle, compatibleWith: nil) else {
    fatalError("Logo not found in framework bundle")
}

Quick Troubleshooting Tip #

If you're still stuck, try cleaning your build folder (Cmd+Shift+K) and rebuilding your app. Sometimes cached assets can cause unexpected loading issues.

内容的提问来源于stack exchange，提问作者Lars Kakavandi-Nielsen