I recommend using this setting to ensure you’re opting in to add an app icon set to your built product. The first setting allows us to configure alternate app icon sets specifically. icns is copied over to the app bundle's resources folder.Xcode Build Settings for alternate app icons. xcassets to the Copy Bundle Resources build phase.Īfter rebuilding, this time the correct. xcassets, then reset the App Icon of the target to AppIcon. xcassets generating another empty AppIcon called AppIcon-2 behind my back, so manually deleted it from. Set App Icon property in the target's General settings to use my.Removed and re-added CFBundleIconFIle property to the target's ist.Changed the Bundle Identifier and made sure everything still builds: this involves lots of one-click fixes that Xcode suggests to the project metadata, such as this one: and regenerating.What worked for me was something among a few desperate trials: created and imported icon-set images that are generated from Icon Set Creator The icon-set works for an fresh empty macOS Cocoa project.added Assets.xcassets to the project and tested varies renaming of this bundle: images, Images, Icons, etc.cleaned, deep cleaned project build folder, manually deleted ~/Library/Developer/Xcode/DerivedData before rebuilding.icns files included in the output app bundle resources in fact, there was absolutely no. removed all the references to icon files in the Copy Bundle Resources build phase.The app insisted on using the old icon even after I. It works fine when there is multiple file. I had the same problem but I fixed it following the next steps:ġ) Add this code to Podfile: post_install do |installer|Ĭopy_pods_resources_path = "Pods/Target Support Files/Pods-IconTest/Pods-IconTest-resources.sh" It should be a bug in CocoaPods, as disccussed here I say theoretically addresses because I've tried implementing both of these solutions, and neither of them resolved the issue on the project where I've encountered it. See discussion with possible temporary fix here and a pull request that has been created for Cocoapods that theoretically addresses this issue. The most obvious thought is that app icons with transparency might be rejected, but I do not believe the icon images I was using contained transparency and I tried to eliminate this in my testing above.Ī completely separate cause that has been reported for some users is related to CocoaPods integration. Perhaps there is something within the png specification which is a valid png, but not an acceptable app icon to Xcode 9. Creating a new AppIcon resource, and inserting the Sketch-created images resulted in the app icon still working.Īll of the above suggests that there is something in Xcode 9 which rejects or fails to use previously working app icon images, and that some processes to create app icons that previously were fine produce images that Xcode 9 cannot use.Re-creating all the icon sizes with a different process, via Sketch, and inserting those icon images into the same AppIcon resource resulted in the app icon working.Inserting those re-created icon images still resulted in a blank app icon. Ensured that my source image did not contain transparency. Re-exporting all the icon sizes with my usual pre-processing app Prepo.I therefore tried various steps to resolve this: Creating a new AppIcon resource, and inserting the original app icon images likewise led to a blank app icon.Ĭombined together, the points to this stage suggested perhaps there was something wrong with the image files themselves.Copying the image files from the non-working to the working AppIcon asset resulted in the working one now failing also.An AppIcon resource copied in from another project where the AppIcon worked, resulted in the AppIcon working in this project, suggesting there was something wrong with the specific original AppIcon resource that wasn't working.A range of experimentation found the following: In my project, I found that a previous AppIcon resource that was working fine no longer resulted in an app icon being rendered.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |