How to Handle Enums in Amplify SDK (Issue with snapshot Casting)?

[Take111]

Description

I am updating from the AppSync SDK and using the Swift files generated by the Amplify CLI. However, I am encountering an issue where the parsing of enums fails.

public var status: HogeStatus {
    get {
        return snapshot["status"]! as! HogeStatus // <- fails
    }
    set {
        snapshot.updateValue(newValue, forKey: "status")
    }
}

Error:

Could not cast value of type ‘__NSCFString’ to ‘HogeStatus’.

It seems that snapshot["status"] is being interpreted as a String. In the AppSync SDK, the value is retrieved as an enum, but in Amplify, it becomes a String.

Is there any way to handle this in Amplify to avoid this issue?

In the AppSync SDK, there was logic to handle enums in GraphQLSelectionSetMapper, but I couldn't find a similar feature in Amplify.

Environments

Amplify CLI 12.13.1
Amplify 2.45.4

[harsh62]

Thank you for raising the feature request with our team. We will take this in our backlog and see if we can prioritize and work on it.

[github-actions]

This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!

[julien-tamade]

Hi I'm also running into this issue and need it to be resolved ASAP because the old libraries don't work with Xcode 16 and we need to upgrade to continue to release the app aupdates

[julien-tamade]

@Take111 did you find a workaround?

[Take111]

@julien-tamade Hi! I created an extension like this as a workaround.

extension GraphQLSelectionSet {
    func getEnum<T: RawRepresentable>(key: String, as type: T.Type) -> T? where T.RawValue == String {
        guard let value = snapshot[key] as? String else {
            return nil
        }
        return T(rawValue: value)
    }
}

[julien-tamade]

I see @Take111 , Thank you. So you manually edit the API.swift file to use getEnum throughout the file wherever it's throwing errors? And if there's a new update to API.swift and its' regenerated you'd have to go through that process over again?

Also curious if you had the s3Object fragment in your schema before.