1
NitinSahu
35d

Hello Guys...
Been stuck in this step for a while now, tried all solutions from StackOverflow.
.....
This community is my only hope now...
.....

Comments
  • 4
    I don't know but the error seems quite general. Maybe saying what you have tried may make someone comment on it.
  • 7
    Have you tried checking your assets file for the mentioned icon sizes. Maybe the icons you provided are not the required size? Just guessing here but your problem is around your app icons
  • 1
    Actually I can see in your iBlueNative build is missing the icon on the left panel. Add icons to your assets folder for the required sizes and you’ll be good to go
  • 3
    Seems pretty self-explanatory, what the problem is?
  • 0
    @PappyHans @molaram I already have the images of all the sizes that are coming in the error logs.
    I think it has something to do with the info.plist as its not having a list(array) of CFBundleIcons
  • 1
    Well Xcode is not picking your icons as evident from the build. It still uses the default icon
  • 4
    have you tried turning it off and on again 😝
  • 1
    @linus-torvald true. This helps sometimes haha. As well as cleaning Derived data and build folders
  • 1
    @linus-torvald 😭😭😭 did this several times
  • 0
    @PappyHans that is not my build folder in the screenshot, its a part of the archive windows and I can see the images in xcode when I click on Images.xcassets and AppIcon
  • 1
    @NitinSahu i know exactly what screen this is, but unfortunately there is not much I can do remotely. Try setting the icons location in your target settings? Xcode is definitely not picking them up as such.
  • 4
    @PappyHans Thanks a lot for your help. I downloaded the icons from a different source this time and gave it a shot, and it worked like a charm...

    Thank you guys 🙏🙏🙏
  • 2
    @NitinSahu if I was you I’d do the following

    Start a new project and use the same icons to see if it works. If it does your setup has changed and you need to fix it, if it doesn’t your icons are the problem
  • 5
    @NitinSahu nice to hear you fixed it
Add Comment