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
{{ message }}
This repository has been archived by the owner on Oct 19, 2024. It is now read-only.
At the bottom of this ticket
I’ve successfully exported any cod able along with 6-7 other frameworks but then hit a snag with this library. Are you aware that this actually works with say Bazel uses x frameworks?
_When using an xcframework that depends on another framework, the X is not a member of type Y will also happen for the Framework it depends on when writing an extensions that wraps, for example, delegate methods
Example: Framework Foo depends on Bar and need to conform to DataDelegate.
class Foo {
...
}
extension Foo : Bar.DataDelegate {
...
}
Everything during compiling will go as planned and the xcframework will be generated. Once you add it to your App along with the dependancy framework Bar and try to build it you will get DataDelegate is not a member of type Bar._
The text was updated successfully, but these errors were encountered:
supabase/supabase-swift#38
At the bottom of this ticket
I’ve successfully exported any cod able along with 6-7 other frameworks but then hit a snag with this library. Are you aware that this actually works with say Bazel uses x frameworks?
UPDATE
https://stackoverflow.com/questions/34159442/x-is-not-a-member-type-of-y
The text was updated successfully, but these errors were encountered: