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
I am following your tutorial and I am having the issue that the MyLibraryResource.bundle file does not get created in the right folder so it gets recognized by Xcode. The Products/MyLibraryResource.bundle file shows up in red in Xcode.
any suggestions?
Thanks for your work and the detailed tutorials.
Regards.
The text was updated successfully, but these errors were encountered:
I ran into this problem when I was trying to build for simulator instead of device for the first time. Following the tutorial, when the bundle is dragged to the Copy Resources phase of the iPhone app, the absolute path to the product is used. This leads to problems when building for the simulator, as the product path is for device.
I was able to fix this by finding the bundle in the iPhone app (it gets added to the iPhone app project when you drag it to the Copy Resources phase). Click on it it open the File Inspector (cmd-opt-1). Change the location dropdown to "Relative to Build Products".
The item stays red jf you're just building for simulator, but, behind the scenes the Copy Resources phase picks up the right location and copies things as expected.
As told by pburleson,
I was trying to drag the resource bundle and drop it on copy resource phase but it was giving error that file not found.
But once i could manage to add it in a project where am using my static library as subproject.
But after updating my static library neither i could add resource bundle nor create it.
I am following your tutorial and I am having the issue that the MyLibraryResource.bundle file does not get created in the right folder so it gets recognized by Xcode. The Products/MyLibraryResource.bundle file shows up in red in Xcode.
any suggestions?
Thanks for your work and the detailed tutorials.
Regards.
The text was updated successfully, but these errors were encountered: