Description

Fixed AEPOptimizeError bridging to ensure proper error handling in both Swift and Objective-C applications.

Problem

• Objective-C code could not properly detect AEPOptimizeError instances using [error isKindOfClass:[AEPOptimizeError class]] as it is converted into a NSError.
• SwiftUI error handling failed when casting error as? AEPOptimizeError when error is sent as NSError
• Error details were not accessible in Objective-C completion handlers

Solution

• Implemented CustomNSError protocol for AEPOptimizeError to provide proper NSError bridging
• Added errorDomain, errorCode, and errorUserInfo properties for Objective-C compatibility
• Maintained backward compatibility with existing Error protocol conformance

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.