[BUG]: SLAvatar's CocoaPod won't build successfully

[N3v1]

Description

Hey everyone,
I was building our CocoaPod for this Libary but the build wasn't successful although building in Xcode won't generate any issues.

Heres the console output:

╭─    ~/Dev/P/SLAvatarKit    main !2 ···· 1 ✘  8s   12:08:15 pm  ─╮
╰─ pod spec lint SLAvatarKit.podspec                                         ─╯


 -> SLAvatarKit (0.0.1-dev.1)
    - ERROR | xcodebuild: Returned an unsuccessful exit code. You can use `--verbose` for more information.
    - NOTE  | xcodebuild:  note: Using codesigning identity override: -
    - NOTE  | xcodebuild:  note: Building targets in dependency order
    - NOTE  | xcodebuild:  note: Target dependency graph (3 targets)
    - ERROR | xcodebuild:  SLAvatarKit/SLAvatarKit/AvatarKitUI/Core/Agreement/AFAgreement.swift:20:20: error: type 'ImageResource' has no member 'memojisHeader'
    - ERROR | xcodebuild:  SLAvatarKit/SLAvatarKit/AvatarKitUI/Core/Management/AFAvatarManagement.swift:46:40: error: type 'ImageResource' has no member 'memojisHeader'
    - NOTE  | xcodebuild:  note: Using codesigning identity override:
    - NOTE  | xcodebuild:  <module-includes>:1:9: note: in file included from <module-includes>:1:
    - NOTE  | xcodebuild:  Target Support Files/SLAvatarKit/SLAvatarKit-umbrella.h:15:9: note: in file included from Target Support Files/SLAvatarKit/SLAvatarKit-umbrella.h:15:
    - ERROR | xcodebuild:  SLAvatarKit/SLAvatarKit/AvatarKit/Animojis/Service/AFAnimojiView.h:15:4: error: expected a type
    - NOTE  | xcodebuild:  <unknown>:0: error: could not build Objective-C module 'SLAvatarKit'

Analyzed 1 podspec.

[!] The spec did not pass validation, due to 4 errors.

Version

Commit: f873066
Xcode: 15.2 & 15.3 beta
macOS: 14.2
CocoaPods: 1.14.3

To Reproduce

Just run this cmd in terminal in the SLAvatarKit repo

pod spec lint SLAvatarKit.podspec

Expected Behavior

*********** BUILD SUCCESSFUL ***********

Additional Context

none

Screenshots

none

Is there an existing issue for this?

• I have searched the existing issues