Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. [iOS] Appstore trouble with CFBundleIconName and asset catalog - something to do with xcode9 and iOS11 SDK
Forum Updated to NodeBB v4.3 + New Features

[iOS] Appstore trouble with CFBundleIconName and asset catalog - something to do with xcode9 and iOS11 SDK

Scheduled Pinned Locked Moved Solved Mobile and Embedded
6 Posts 4 Posters 3.2k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • timdayT Offline
    timdayT Offline
    timday
    wrote on last edited by timday
    #1

    Having updated to xcode9, I'm attempting to submit an updated version of an app built vs. Qt5.7 (just trying a newer version now but this would be a problematic fix for licensing reasons).

    The appstore is rejecting me with this message:

    We have discovered one or more issues with your recent delivery for "...".
    To process your delivery, the following issues must be corrected:
    
    Missing Info.plist value - A value for the Info.plist key 'CFBundleIconName' is missing in the bundle '...'. 
    Apps built with iOS 11 or later SDK must supply app icons in an asset catalog and must also provide a value for this Info.plist key. 
    For more information see http://help.apple.com/xcode/mac/current/#/dev10510b1f7.
    

    Googling this finds plenty of other people who've hit it, but all the solutions (and there seem to be a diverse range of contradictory ones offered) seem to be aimed a people who are far more familiar with xcode than I am.

    How I've attempted to fix it is:

    • In my build-script, after qmake has created the xcodeproj, do a /usr/libexec/PlistBuddy -c 'Add :CFBundleIconName string "AppIcon"' Info.plist
    • Having opened the qmake-generated xcodeproj in xcode, add an Assets.xcassets to the app at the top level.
    • Initially, within that I create an AppIcon (named AppIcon) and populate the blank placeholders with the needed icon sizes (it's an iPad only app so there aren't as many of these as there would be if it also ran on phones). On subsequent attempts the Assets.xcassets is already populated.
    • Build (it runs just fine on local iOS10 and iOS11 devices) and submit to appstore as usual. It uploads successfully, but a few minutes later that error message arrives by email.

    Not sure what I'm doing wrong here... any pointers greatly appreciated.

    1 Reply Last reply
    0
    • R Offline
      R Offline
      refaQtor
      wrote on last edited by refaQtor
      #2

      I've just hit that, as well. This link seemed most promising, and Qt specific: https://appbus.wordpress.com/2017/10/06/ios-11-and-xcode-9-in-qt-5-9-x-projects/

      it is the fix that I am trying now

      It worked like a champ. much easier than the old way, too.

      timdayT 2 Replies Last reply
      4
      • R refaQtor

        I've just hit that, as well. This link seemed most promising, and Qt specific: https://appbus.wordpress.com/2017/10/06/ios-11-and-xcode-9-in-qt-5-9-x-projects/

        it is the fix that I am trying now

        It worked like a champ. much easier than the old way, too.

        timdayT Offline
        timdayT Offline
        timday
        wrote on last edited by timday
        #3
        This post is deleted!
        1 Reply Last reply
        0
        • R refaQtor

          I've just hit that, as well. This link seemed most promising, and Qt specific: https://appbus.wordpress.com/2017/10/06/ios-11-and-xcode-9-in-qt-5-9-x-projects/

          it is the fix that I am trying now

          It worked like a champ. much easier than the old way, too.

          timdayT Offline
          timdayT Offline
          timday
          wrote on last edited by timday
          #4

          @refaQtor Brilliant... following that worked... app just popped up in testflight.

          Comparing with some other write-ups of the issue... I think removing any cruft related to "the old way of doing things" (before asset catalogs) must be quite important to getting something through (except the appstore's error messages are useless and don't tell you what the problem really is). I'd mark your post as the correct answer if the forum let me... but it only lets me flag my own posts as such... so I'll just mark the thread solved. Thanks!

          ekkescornerE 1 Reply Last reply
          0
          • timdayT timday

            @refaQtor Brilliant... following that worked... app just popped up in testflight.

            Comparing with some other write-ups of the issue... I think removing any cruft related to "the old way of doing things" (before asset catalogs) must be quite important to getting something through (except the appstore's error messages are useless and don't tell you what the problem really is). I'd mark your post as the correct answer if the forum let me... but it only lets me flag my own posts as such... so I'll just mark the thread solved. Thanks!

            ekkescornerE Offline
            ekkescornerE Offline
            ekkescorner
            Qt Champions 2016
            wrote on last edited by
            #5

            @timday great to see that my blog post helped you :)

            ekke ... Qt Champion 2016 | 2024 ... mobile business apps
            5.15 --> 6.9 https://t1p.de/ekkeChecklist
            QMake --> CMake https://t1p.de/ekkeCMakeMobileApps

            B 1 Reply Last reply
            2
            • ekkescornerE ekkescorner

              @timday great to see that my blog post helped you :)

              B Offline
              B Offline
              bogong
              wrote on last edited by bogong
              #6

              @ekkescorner Just done the same issue by following of your blog. Confirming that it is working on iOS 12.1 and Xcode 10.2.1. Just published. Thx a lot.

              Just checked the quality of images that generated automatically by this site. They are not "pixel nice", they are very rough. If there are necessity to improve images quality for the level of "pixel nice" need to exchange them by drawn them in Photoshop and using them like templates.

              1 Reply Last reply
              0

              • Login

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Users
              • Groups
              • Search
              • Get Qt Extensions
              • Unsolved