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
There seems to be a problem with the way this library loads images from its resources bundle.
From the looks of it you guys are using [UIImage imageNamed:] in NYTPhotosViewController, which searches the main bundle. On my device, that doesn't work, and the image is not loaded. I'm not very familiar with the way Cocoapods works, but it may have something to do with the fact that I'm using use_frameworks! in my podfile.
I think the easiest way to fix this is to use [UIImage imageNamed:inBundle:compatibleWithTraitCollection:] with the bundle received from [NSBundle bundleForClass:], as that will load the image from the appropriate bundle.
Just as a side note, I see you guys are using resources and not resource_bundles in your podspec, and I think the cocoapods team has deprecated resources in favor of resource_bundles.
Thanks in advance for replies 👍
The text was updated successfully, but these errors were encountered:
There seems to be a problem with the way this library loads images from its resources bundle.
From the looks of it you guys are using
[UIImage imageNamed:]
inNYTPhotosViewController
, which searches the main bundle. On my device, that doesn't work, and the image is not loaded. I'm not very familiar with the way Cocoapods works, but it may have something to do with the fact that I'm usinguse_frameworks!
in my podfile.I think the easiest way to fix this is to use
[UIImage imageNamed:inBundle:compatibleWithTraitCollection:]
with the bundle received from[NSBundle bundleForClass:]
, as that will load the image from the appropriate bundle.Just as a side note, I see you guys are using
resources
and notresource_bundles
in your podspec, and I think the cocoapods team has deprecatedresources
in favor ofresource_bundles
.Thanks in advance for replies 👍
The text was updated successfully, but these errors were encountered: