You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
XS2A is not using an iOS naming standard (swiftlang/swift#43510) since the module and the main public class have the same name. So to solve the problem of this dependency, we propose that you distribute it to us embedded within your framework, thus guaranteeing compatibility and avoiding problems like Shadowed Name and the crashes when a xcframework try to use it.
It would be great, if you could deliver a version 2.0.0 of your XS2AiOS, in which the class XS2AiOS and all it usages (other code-references, documentatoin, etc.) was renamed to e.g. XS2A
The text was updated successfully, but these errors were encountered:
XS2A is not using an iOS naming standard (swiftlang/swift#43510) since the module and the main public class have the same name. So to solve the problem of this dependency, we propose that you distribute it to us embedded within your framework, thus guaranteeing compatibility and avoiding problems like Shadowed Name and the crashes when a xcframework try to use it.
It would be great, if you could deliver a version 2.0.0 of your XS2AiOS, in which the class XS2AiOS and all it usages (other code-references, documentatoin, etc.) was renamed to e.g. XS2A
The text was updated successfully, but these errors were encountered: