Can Swift enums have multiple raw values?

You have a couple options. But neither of them involve raw values. Raw values are just not the right tool for the task.

Option 1 (so-so): Associated Values

I personally highly recommend against there being more than one associated value per enum case. Associated values should be dead obvious (since they don't have arguments/names), and having more than one heavily muddies the water.

That said, it's something the language lets you do. This allows you to have each case defined differently as well, if that was something you needed. Example:

enum ErrorType {
    case teapot(String, Int)
    case skillet(UInt, [CGFloat])
}

Option 2 (better): Tuples! And computed properties!

Tuples are a great feature of Swift because they give you the power of creating ad-hoc types. That means you can define it in-line. Sweet!

If each of your error types are going to have a code and a description, then you could have a computed info property (hopefully with a better name?). See below:

enum ErrorType {
    case teapot
    case skillet

    var info: (code: Int, description: String) {
        switch self {
        case .teapot:
            return (418, "Hear me shout!")
        case .skillet:
            return (326, "I'm big and heavy.")
        }
    }
}

Calling this would be much easier because you could use tasty, tasty dot syntax:

let errorCode = myErrorType.info.code

No, an enum cannot have multiple raw values - it has to be a single value, implementing the Equatable protocol, and be literal-convertible as described in the documentation.

I think the best approach in your case is to use the error code as raw value, and a property backed by a prepopulated static dictionary with the error code as key and the text as value.