Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xcode bug renders ResourceStatusOverlay & ResourceImageView unusable in storyboards #4

Open
pcantrell opened this issue Sep 2, 2015 · 1 comment

Comments

@pcantrell
Copy link
Member

Swift framework classes with an @objc(Name) annotation are not usable under either the Swift name or the Obj-C name within a storyboard.

The current workaround is to define a dummy subclass in the project using Siesta:

class ResourceStatusOverlay: Siesta.ResourceStatusOverlay { }

The storyboard can now see that class.

pcantrell added a commit that referenced this issue Aug 2, 2016
@pcantrell
Copy link
Member Author

As of Siesta 1.0b8 + Xcode 7.3.1, the simple subclass workaround above no longer works.

It is possible to create a project-local subclass in Objective-C that works. However, Siesta should just drop the BOS prefix for the Obj-C version of ResourceStatusOverlay, which will prevent Siesta from exposing this Apple bug in the first place. Targeting 1.0b9 for this.

@pcantrell pcantrell changed the title XC7 bug renders ResourceStatusOverlay & ResourceImageView unusable in storyboards Xcode bug renders ResourceStatusOverlay & ResourceImageView unusable in storyboards Dec 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant