I am experiencing the same issue. Turning off the auto-generated ObjC header "works" but doesn't seem like the right solution. I think the issue is one the swift package manager side in how it generates its compatibility. The issue for us seems to be Swift-only swift package, imported into Swift framework and used by something exposed to Objective C. This inserts the import in the compatibility header which causes issues.
dkellyNISC
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for