warning: Icon specified in the Info.plist not found under the top level app wrapper: Icon-SMall@2x.png (-19007)Typo in icon filename in info.plist (did you notice this typo? No? Look again!), just correct the name SMall --> Small. Would be nice, if Xcode would warn about these earlier.
warning: This bundle is invalid. The application-identifier entitlement is not formatted correctly; it should contain your 10-character App ID Seed, followed by a dot, followed by your bundle identifier: 54D496P3DK.* (-19054)I started this project over a year ago. Working few hours a few evenings and weekends every now and then does not quarantee a speedy release, I have just learned. Kind of takes the whole "Release Early, Release Often" idea away. Can't even say it's "Fail Early, Fail Often" methodology, since I totally failed to make a release during that time (except TestFlight experiment)!
Anyway, seems like some file formats were changed in Xcode 4. The fix was to Copy & Paste this new Entitlements.plist (from StackOverflow):
<?xml version="1.0" encoding="UTF-8"?>I'm a member in three Apple Developer Program teams and have two of them "installed" in this development machine. Therefore I get the following code signing warning. Didn't do anything to fix it, but the warning disappeared at the end.
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>get-task-allow</key>
<false/>
<key>application-identifier</key>
<string>$(AppIdentifierPrefix)$(CFBundleIdentifier)</string>
<key>keychain-access-groups</key>
<array>
<string>$(AppIdentifierPrefix)$(CFBundleIdentifier)</string>
</array>
</dict>
</plist>
Not sure which is more troublesome: to see a warning in the first place or that it disappears without me doing anything about it.
Code Sign warning: code-signing identity 'iPhone Developer' matches multiple identities : 'iPhone Developer: Jouni Miettunen (code1)', 'iPhone Developer: Jouni Miettunen (code2)' -- 'iPhone Developer: Jouni Miettunen (code1)' will be used.Release has been made, now waiting for next warnings. Exciting times!
No comments:
Post a Comment