I have a project with 5 Targets. All of these have their own .xcassets (Assets) that holds LaunchImages, AppIcons, And two more Image Assets. All of these .xcassets are given appropriate Target Membership (Properly added to Copy Bundle Resources of their own target. All of these .xcassets files have different names).
When deploying these apps on iPhone 5S, the AppIcon does not appear. I searched on google and came across this answer Missing CFBundleIconName in Xcode9 iOS11 app release. I made changes like removing CFBundleIcons and adding CFBundleIconName in my Info.plist file. But nothing seems to work.
I have also assigned AppStore iOS 1024x1024 in AppIcon for all .xcassets file.
I created ipa for AdHoc distribution and verified that appropriate AppIcon gets bundled in the archive (By extracting ipa and browsing through Payload). While distributing ipa with http://www.diawi.com the AppIcon is displayed on the device while the app is being installed (while circular progress is being shown on AppIcon on iPhone). But as the installation finishes, the AppIcon disappears.
I checked the same AdHoc build on iPhone 5 (iOS 10.x.x) and the AppIcon is displayed on it. So, what exactly is creating problem for iOS 11 on iPhone 5S.
Xcode shows AppIcon for each target and their scheme as :
My Xcode version is : Version 9.0 (9A235).Someone please confirm that I have latest stable release (not beta / GM seed).
My iPhone 5S is updated on iOS 11 via official release (I haven't installed beta of iOS 11).
Open your app icons in Preview. Go to Tools -> Assign Profile. Select sRGB IEC61966-2.1 from the dropdown. You will have to do this for all the app icons you are using for your app.
I finally found the problem with cocoapods. The shell-script located at 'Pods -> Target Support Files -> Pods-ProjectName -> Pods-ProjectName-resources.sh' contains a section (probably last) where it combines all asset catalogs into one, thus my exported archive would have assets from all the targets and results in unexpected AppIcon.
All I had to do was to remove the section in the shell script where asset catalogs were combined into one. Refer this answer if you are experiencing same issue.
What worked for me:
Go to 'TARGETS -> Build Settings' and set your icon name in 'Asset Catalog App Icon Set Name'.
I just upgraded from Xcode 3 to 4. Have been playing around a bit first to get used to the new interface and trying to find where everything has moved to... (pfffff). New projects seem to work fine but it's definitely a large transition.
Now I tried opening some older projects but something strange happens...
ALL my projects are iPhone projects, none is for OS X but when opened in Xcode 4 it says in the left most pane: 1 target, missing base SDK. In the right pane I see: Mac OS X Application Target, everything in the Targets Section is related to OS X and NOT to iPhone.
I tried adding a target for iPhone, but still the target is missing. I then deleted the OS X target and see in the left pane: 1 target, IOS SDK 4.3 but the "Run" option in Project menu is still disabled.
I also tried this with sample files from tutorials I used in the past (eg Beginning iPhone 3 Development en More iPhone 3 development) but I have the same problem!
1) Shouldn't Xcode open those Xcode 3 projects just fine ?
2) What can I do to have the "Run" option working again ?
You need to set two Build Settings:
For Base SDK - set this to Latest iOS
For Deployment Target - set this to iOS 4.3 (or whatever the minimum SDK is that you want your app to work on.
Related to point 1 - if you hard code the SDK version here, then whenever it's upgraded, you'll likely get error messages about missing SDKs if the old one is removed
Yo have to try this
You have to select your project then in middle pane you have to select "Targets" and then go to "Build Settings" tab and in base SDK select "IOS 4.3".
Your project -->Targets(your Project Name) -->Build Settings -->Base SDK --> IOS 4.3
You need to set Base SDK and IOS Deployment Target. My Xcode 3 projects works fine after that.
If you select your project, in the editor window you get the PROJECT and TARGETS to work with.
You can set proper values their.
You may need to do more things. In Xcode4 configurations are managed using Scheme. So, Go to
Menu -> Product -> Manage Scheme,
Select your scheme, and Edit your scheme.
You may relieved off some issues there.
You need to follow both answer, set the base SDK and manage the SCHEME.some times you may not see the iphone simulator option in the dropdown list then go to Manage scheme change debug to release then you may see the iphone simulator in dropdown and change it back to debug mode.
i configured the Openers successfully with the help of this link. http://www.politepix.com/openears/configuring.
however they are documented "Configuring Your App For OpenEars" only in Xcode 4.
i am using xcode 3.2.6 cant able to use Openears library in my application using this document .may i knoe any other document links to explain "Configuring Your App For OpenEars" only in Xcode 3.2.6.can any one help me please.i stuck in here in the document.cant able to do this process in xcode 3.2.6.this following steps i can do with xcode 3.2.6...please help me
steps that i cant do in xcode 3.2.6
Step 2: From Xcode, select your blue project icon for your app (not the OpenEarsLibrary project) in the Project Navigator and select its target under the TARGETS header in the left-hand column in the editor. Navigate to the tab Build Phases. Click “Target Dependencies”.
Click the plus button for Target Dependencies. Then select the gray OpenEarsLibrary icon in that dialog and click “Add”.
Step 3: In the same view, with the app target still selected underneath the header TARGETS in the left-hand pane of the editor window, navigate to the Build Phases pane and select “Link Binary With Libraries”
Tapping the plus button, add the OpenEars framework libOpenEarsLibrary.a found in a folder at the top called workspace
please help by converting the above step according to the xcode 3.2.6
Go to this page: http://www.politepix.com/openears/gettingstarted and find the phrase "It is still possible to download the previous version of OpenEars and its distribution contains instructions for Xcode 3 which should be very helpful for figuring out how to install current versions of OpenEars in Xcode 3". Download the previous version of OpenEars that is linked in the phrase "download the previous version of OpenEars".
Inside this download are the entire instructions for installing that older version of OpenEars in Xcode 3, saved as PDFs. The steps in the PDFs are not all the same as the instructions for the current version, but the part about linking the library (the specific part you are asking about) is still exactly the same. This explanation is in the PDF called "Configuring Your App For OpenEars.pdf" starting on page 4.
Wondering why you are still using Xcode 3 but what you need to do from memory is look for the root level targets expander icon in the tree. It looks like a red/white archery target and was usually after the resources folder. Expand it and right click what will probably be the sole target for your project. From there you will be offered the similar opportunity to add build phases.
If that doesnt exist in the contextual menu have a dig around in the Properties section for the target. It might be one of the tabs to add link dependancies.
I have created a new version of iPhone app. I wanted to change the icon, so:
I added the icons in different sized to the Resources folder of my Project in XCode:
I specified the icon files in the info.plist file:
in iTunes Connect I added new version of my app and replace the old icon with the new one. The new icon is now visible when I log in to iTunes Connect.
The effects:
I can see the new icon when I run my app on simulator.
I can see the new icon when I visit AppStore with iTunes on my Mac.
I can see the OLD icon when I visit AppStore on my iPhone.
I can see the OLD icon on my iPhone after upgrading my app to the new version.
Any ideas why the old icon is still visible in some of the places?
kind regards,
Jakub
Use "Build > Clean all Targets" and then build and run. Xcode doesn't always see that images have been updated, and leaves them out of incremental builds. Cleaning before building makes Xcode build the app file from scratch, and will pick up any images it's failing to get.
Why it's inconsistent is that different build types (simulator vs device) are different build targets, and got built with different versions of your images. Not unusual.
The one thing that this WON'T address is the old icon on the iPhone's app store app. You might need to update your app store submission with fresh images.
Whenever I submit my app to itunesconnect, after about 10 minutes, the status changes to "Invalid Binary" with absolutely no explanation why.
I have searched all over for answers there is non. I even re-installed XCode and App loader.
Note that App Loader doesn't give any errors whatsoever.
I build with XCode 3.2.3 iPhone 4 GM Seed iPhone 4 based SDK iPhone/iPad as a target family
I had the same INVALID BINARY error from iTunes Connect even if Application Loader accepted my binary. The solution was very simple...
Open your info.plist, right-click and check Show Raw Key/Values:
CFBundleIconFile = Icon.png (my iPhone 57x57 PNG icon)
CFBundleIconFile~ipad = Icon-72.png (my ipad 72x72 PNG icon)
CFBundleIconFiles = array
Item 0 = Icon.png
Item 1 = Icon#2x.png (my iPhone 4 114x114 PNG icon)
Item 2 = Icon-72.png
Save, clean all targets, build and analyze, compress in Finder and resubmit!
The error was caused because I typed the key "Icon Files". In Raw view, this has mapped to "Icon Files" instead of CFBundleIconFiles. I have Xcode 3.2.3, I guess Xcode 3.2.4 better maps this key identifier.
Good Luck everybody!
Source: Technical Q&A QA1686: App Icons on iPad and iPhone
The "invalid Binary" did cost me 4 days to figure out. and because I stumbled over this helpful page, I want to help saving you the valuable time. In my case, in the provisioning portal, a colleague revoked the distribution cetrificate, built a new one and did not let me know. You can use the new certificate for making new prov files, and in the build process, xcode "thinks" everything is all right. which of course is not. Only after uploading to the itunes connect you see the "Invalid Binary" note without further explanantions. The solution was to revoke the certifikate (again) with the whole certificate request procedure and make a new one. Use this as the certificate, and you will be fine - no more uncommented "Invalid Binary" - and if you share tzh eteam agent access to the portal with others, make sure, you let them know and hand over your new .p12 key file.
The topic is old but i had the same problem today and maybe my explanation will help somebody in future.
While submitting app by Xcode 4 organizer you have to choose distribution profile. Make sure this is exactly the same profile which you set in build settings (project and target). For almost all my projects i didn't have to change build settings from development to distribution and it was fairly enough to choose distribution only in organizer while submitting. But in one case this resulted "Invalid Binary" error in iTunes Connect.
Apple has improved the error reporting on this recently and now you will get an email that highlights the problem accordingly. Just be patient it may take a few minutes to come in. I received the following email which highlighted the problem:
Dear Developer,
We have discovered one or more issues with your recent binary submission for "XXX.APP". Before your app can be reviewed, the following issues must be corrected:
Invalid Icon Path - No icon found at the path referenced under key "CFBundleIcons": xxxIcon.png
Once these issues have been corrected, go to the Version Details page and click Ready to Upload Binary. Continue through the submission process until the app status is Waiting for Upload and then use Application Loader to upload the corrected binary.
Regards,
The iTunes Store Team
I had this same problem and here is how I resolved it:
The CFBundleIconFile is not listed instead Icon File and Icon Files. Change the Icon File to the Icon Files selection. Now click the left arrow next to the Icon Files label to expand the list. You will see Item 0, select Item 0 and then click the plus button to the right to add another item. You should then see Item 1. Enter your 56x56 icon file name in Item 0 and your 72x72 icon file name in Item 1. Save the info list
Since I want this app to be both Iphone/Ipad I choose:
Architecture as Standard (you will get a warning but if you change to only armv7 for a no warning build, the binary will be rejected by itunesconnect)
Base sdk as 3.2
Target Device family as Iphone/iPad
iOS Deployment Target as 3.2
Now build for app store distribution, compress and upload to itunes connect.
I had the same problem. App stucks in "Upload Received" status for more than 5 days. After contacting the Itunes Connect Support with the topics "Manage Your Applications" and "Upload received" and answering unnecessary questions, the App Status changed back to "Invalid Binary". After searching for solutions which recommended to check the icons files I found another tip to check the certificate.
That was my solution: I recreated a distribution certificate with Mac's KeyChaining tool and now used a RSA private key instead of DSA. That helped. I re-uploaded the App and the status changed to "Waiting for Review" few minutes later.
I came here for the same issue, tried the App Launcher update, et cetera. I tried rebooting and resubmitting a dozen times, manually editing the info.plist again and again. For me the solution was noticing that there is now an "Icon files" AND and "Icon files (iOS5)" entry. Check both of these for a bad reference to moved icons.
Did you zip the binary? Might want to try that.
From the iTunesConnect Developer Guide:
Application Binary and Small App Icons
Keep the file size as small as
possible, both for ease of upload
through iTunes Connect, and for the
end-user’s purchase experience. The
binary must be a zipped file, and pass
a code sign check upon upload in
iTunes Connect.
iPhone and iPod touch:
If you are uploading an app to run on
iPhone and iPod touch, the binary must
include an icon that is 57x57 pixels,
which will be displayed on the home
screen and the App Store when viewed
from the iPod touch and iPhone. You
can also optionally include a hi-res
icon that is 114x1144 pixels to take
advantage of the Retina display on
iPhone 4.
iPad: If you are uploading
an app to run on iPad, the binary must
include two icons: one that is 50x50
pixels and one that is 72x72 pixels,
which will be displayed on the iPad
home screen and the App Store when
viewed on the iPad.
If all else fails, reboot, reboot, reboot. I ended up rebooting and resubmitting five times (making no other changes, honestly) before my app was accepted.
A couple of other things to try.
if you have an old xcode 3.2 Entitlements.plist file hanging around.
Delete it and recreate > New File > Code Signing > Entitlements.
Check the configuration for Archiving
Product > Edit Scheme > Archive > Build Configuration
Make sure the correct one is selected. (for me Release was selected but I needed Distribution profile - yours may vary)
your Binary final rejected because of some basic reasons.
like,
1)Check For 'icon files' option in info tab of project.
if your app is Universal icon files should be 4 or <4 *must not more then.
if your app is for one device only the icon file should be 2 or <2. *must not more then.
Icon files should be as per itunes Guide. itune guide Link
2)Must check that for splash screen if your app does not have any splash then also give blank splash screen.in universal set for both device.
3) if you are updating app then check for binary version of previous uploaded app and your app.your app must have grater version then uploaded.
4) check for Bundle name and version also.