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

IB Designables: Failed to render and update auto layout status #254

Closed
alexanderkhitev opened this issue Apr 10, 2018 · 11 comments
Closed

Comments

@alexanderkhitev
Copy link

Hello! I use ActiveLabel in IB and I get this error

 IB Designables: Failed to render and update auto layout status for RegisterMainViewController (Ovd-Ud-K0B): dlopen(ActiveLabel.framework, 1): no suitable image found.  Did find:
	ActiveLabel.framework: required code signature missing for 'ActiveLabel.framework'
@yunnnyunnn
Copy link

+1. Different message tho.
Xcode 9.3 (9E145)
Never happened before Xcode update.

IB Designables: Failed to render and update auto layout status for View: Symbol not found: __T0SS13CharacterViewVN
  Referenced from: ActiveLabel.framework
  Expected in: /../usr/lib/swift/iphonesimulator/libswiftCore.dylib
 in ActiveLabel.framework

@alexanderkhitev
Copy link
Author

I solved this problem as follows, I made a class that inherits from ActiveLabel and used this new class in Storyboard. Of course, it's better to solve this problem on the framework level.

@pradeeprajkumar
Copy link

I'm facing the same issue.
ActiveLabel.framework: required code signature missing for 'ActiveLabel.framework'

screen shot 2018-04-17 at 1 28 50 pm

ActiveLabel Version: 0.8.1
Xcode version: 9.3

Thanks @alexanderkhitev I have temporarily resolved this issue by creating a subclass of ActiveLabel and used it in our Storyboard.

Would be great if its resolved in the framework.

@maziyarpanahi
Copy link
Collaborator

maziyarpanahi commented Apr 24, 2018

Hi,

This is an issue with new Xcode, new CocoaPods 1.5 and it's been covered here:
CocoaPods/CocoaPods#7606

Either downgrade your CocoaPods to 1.4 or use the workaround that is mentioned here: (I used this workaround for myself and it worked)
CocoaPods/CocoaPods#7606 (comment)

Although this issue is not related to this library, I leave it open for the time being as it will hit most of the users.

@s2339956
Copy link

I'm facing the same issue.

@maziyarpanahi
Copy link
Collaborator

I already posted the solution and it's not related to this library.

@akashhipl
Copy link

I'm facing the same issue.

@maziyarpanahi
Copy link
Collaborator

Please follow the instructions: CocoaPods/CocoaPods#7606 (comment)

@muqbilk
Copy link

muqbilk commented Aug 10, 2018

I would suggest trying this first
pod deintegrate

then re-install , you can choose whatever version you are comfortable with :
pod _1.5.3_ install

Then rebuild and see, It worked for me !

@sanket-jayani
Copy link

Thanks @alexanderkhitev, it's working fine

@CodeKunal
Copy link

Restating Xcode worked for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants