New version for CocoaPods to use bundleForClass:

[choefele]

Thanks for this library.

In my project, I'd like to use FontAwesomeKit as a dynamic framework. In a framework, all resources have to be loaded with bundleForClass: instead of mainBundle. This has been fixed in fefd9e57aa77ce70dbb84b3be215b35b583f2cac.

Could you please release a new version for CocoaPods that includes this commit (and the latest updates).

Thanks again.

[PrideChung]

The reason I haven't release it yet is because I can't make the font registration work properly on WatchKit app. It can load the font without throwing any error, but all icons are rendered as question mark, unless I manually register those icon fonts in the Info.plist file. Any idea?

[choefele]

To use a custom font in a WatchKit App, you need to include the font in both WatchKit Extension and WatchKit App targets, see Using Fonts.

You can use the automatic registration process in the WatchKit Extension target. For the WatchKit App target, however, you need to include the font manually and set the UIAppFonts property in the plist.

[choefele]

Did the description on how to use fonts in a WatchKit App help?

[PrideChung]

@choefele Thanks for the tip, I'm still finding a way to make the automatic font registration work. In the meanwhile, you can use pod 'FontAwesomeKit', :head to use the lastest version of FontAwesomeKit.