Comments on: iOS4 and the wildcard http://twoappguys.com/blog/ios4-and-the-wildcard/ Apps for the iPhone, iPad, iPod Touch, Android plus info on creating your own apps Fri, 16 Sep 2011 21:39:15 +0000 hourly 1 http://wordpress.org/?v= By: Nick http://twoappguys.com/blog/ios4-and-the-wildcard/#comment-681 Nick Fri, 16 Sep 2011 21:39:15 +0000 http://twoappguys.com/?p=125#comment-681 Thank you so much for posting your code. This was the final piece I needed to solve way too many hours of fail Thank you so much for posting your code. This was the final piece I needed to solve way too many hours of fail

]]> By: Justin http://twoappguys.com/blog/ios4-and-the-wildcard/#comment-18 Justin Tue, 03 May 2011 17:10:08 +0000 http://twoappguys.com/?p=125#comment-18 Apple finally documented the change in August 2010 (QA1710). https://developer.apple.com/library/ios/#qa/qa1710/_index.html Apple finally documented the change in August 2010 (QA1710).
https://developer.apple.com/library/ios/#qa/qa1710/_index.html

]]> By: Guyal http://twoappguys.com/blog/ios4-and-the-wildcard/#comment-17 Guyal Thu, 16 Sep 2010 16:17:51 +0000 http://twoappguys.com/?p=125#comment-17 Thanks for the post; this fixed my upload problem today! Thanks for the post; this fixed my upload problem today!

]]> By: Vincent http://twoappguys.com/blog/ios4-and-the-wildcard/#comment-16 Vincent Tue, 03 Aug 2010 10:52:56 +0000 http://twoappguys.com/?p=125#comment-16 Thank you so much for this solution! Each time I submit my app to iTunes Connect, I have to spend a full day trying to find solutions on the web to weird errors, that turn out usually to be plainly bugs in Xcode or iTunes Connect. For me, it was Nigel Coward's solution that worked: recreating from scratch the Entitlements.plist file. Note: After recreating that file, I could submit my app successfully, but then the Debug configuration was not working anymore... The new Entitlements.plist file has to be removed from the Debug configuration manually. Thanks Apple for simplifying my life... Thank you so much for this solution!

Each time I submit my app to iTunes Connect, I have to spend a full day trying to find solutions on the web to weird errors, that turn out usually to be plainly bugs in Xcode or iTunes Connect.

For me, it was Nigel Coward’s solution that worked: recreating from scratch the Entitlements.plist file.

Note: After recreating that file, I could submit my app successfully, but then the Debug configuration was not working anymore… The new Entitlements.plist file has to be removed from the Debug configuration manually. Thanks Apple for simplifying my life…

]]> By: LR http://twoappguys.com/blog/ios4-and-the-wildcard/#comment-15 LR Tue, 20 Jul 2010 00:44:56 +0000 http://twoappguys.com/?p=125#comment-15 Indeed !!!!! Nigel Coward post will do the trick. It worked! Indeed !!!!!
Nigel Coward post will do the trick.

It worked!

]]> By: Phewwww http://twoappguys.com/blog/ios4-and-the-wildcard/#comment-14 Phewwww Fri, 09 Jul 2010 18:46:12 +0000 http://twoappguys.com/?p=125#comment-14 Thank you for posting this... For about 30 minutes there, I felt like a complete n00b all over again. Thanks for saving my dignity. Thank you for posting this… For about 30 minutes there, I felt like a complete n00b all over again. Thanks for saving my dignity.

]]> By: Nigel Coward http://twoappguys.com/blog/ios4-and-the-wildcard/#comment-13 Nigel Coward Mon, 28 Jun 2010 10:37:40 +0000 http://twoappguys.com/?p=125#comment-13 I too experienced this after updating to the IOS4 SDK. All of my apps which had previously gone through without issue were now giving me the same emailed "Invalid application-identifier Entitlement" error. I followed your initial instructions without success, then in desparation tried the suggestion by User01 of deleting the entitlements.plist file and recreating it in my projects - this worked! As reference for any other souls out there suffering in this way, my new auto generated entitlements.plist file now looks like this: <!--- Required entitlements (in most cases shouldn't be changed) --> application-identifier $(AppIdentifierPrefix)$(CFBundleIdentifier) keychain-access-groups $(AppIdentifierPrefix)$(CFBundleIdentifier) <!--- Custom entitlements below --> Hope this helps anyone else suffering from this annoying problem! Nige I too experienced this after updating to the IOS4 SDK. All of my apps which had previously gone through without issue were now giving me the same emailed “Invalid application-identifier Entitlement” error.

I followed your initial instructions without success, then in desparation tried the suggestion by User01 of deleting the entitlements.plist file and recreating it in my projects – this worked!

As reference for any other souls out there suffering in this way, my new auto generated entitlements.plist file now looks like this:


application-identifier
$(AppIdentifierPrefix)$(CFBundleIdentifier)
keychain-access-groups

$(AppIdentifierPrefix)$(CFBundleIdentifier)

Hope this helps anyone else suffering from this annoying problem!

Nige

]]> By: Jeff Haynie http://twoappguys.com/blog/ios4-and-the-wildcard/#comment-12 Jeff Haynie Sun, 27 Jun 2010 09:53:17 +0000 http://twoappguys.com/?p=125#comment-12 oops. yeah, sorry 'bout that. in the upcoming 1.4, this is fixed along with a few others: 1. If you have an Entitlements.plist in your root project folder, we'll use that one and won't generate one. 2. We automatically generate the appropriate iOS4 Entitlements.plist (thanks to above) ... 3. We should be working now in the various builds - ad hoc vs. distro - etc. If you'd like to test before the final release (coming hopefully on monday), you can pull from master at http://github.com/appcelerator/titanium_mobile. Cheers! Jeff oops. yeah, sorry ’bout that.

in the upcoming 1.4, this is fixed along with a few others:

1. If you have an Entitlements.plist in your root project folder, we’ll use that one and won’t generate one.

2. We automatically generate the appropriate iOS4 Entitlements.plist (thanks to above) …

3. We should be working now in the various builds – ad hoc vs. distro – etc.

If you’d like to test before the final release (coming hopefully on monday), you can pull from master at http://github.com/appcelerator/titanium_mobile.

Cheers!
Jeff

]]> By: John http://twoappguys.com/blog/ios4-and-the-wildcard/#comment-11 John Sat, 26 Jun 2010 14:45:41 +0000 http://twoappguys.com/?p=125#comment-11 User01 you said it, but since Tony and I use appcelerator just deleting the file does not work, but Apple definitely does need to be more clear when displaying error messages. User01 you said it, but since Tony and I use appcelerator just deleting the file does not work, but Apple definitely does need to be more clear when displaying error messages.

]]> By: User01 http://twoappguys.com/blog/ios4-and-the-wildcard/#comment-10 User01 Sat, 26 Jun 2010 08:13:05 +0000 http://twoappguys.com/?p=125#comment-10 Thanks very much for your post, it saved my life. At the end of the day, I think it's just easier to delete your Entitlements.plist and add a new one. When you do this, all the information necessary is already added to Entitlements.plist. It is appalling that Apple doesn't make this clear, and even more appalling that their email when your app is rejected states: "Invalid application-identifier Entitlement - This error can occur if the bundle identifier (that is, the value assigned to the CFBundleIdentifier key in Info.plist) does not match the pattern allowed by the provisioning profile you obtained from the iPhone Developer Portal. " Now that I know the problem, it makes half way sense, but the email should specifically tell you just to regenerate your Entitlements.plist as it's work completely differently now! Thanks very much for your post, it saved my life.

At the end of the day, I think it’s just easier to delete your Entitlements.plist and add a new one. When you do this, all the information necessary is already added to Entitlements.plist. It is appalling that Apple doesn’t make this clear, and even more appalling that their email when your app is rejected states:

“Invalid application-identifier Entitlement – This error can occur if the bundle identifier (that is, the value assigned to the CFBundleIdentifier key in Info.plist) does not match the pattern allowed by the provisioning profile you obtained from the iPhone Developer Portal. ”

Now that I know the problem, it makes half way sense, but the email should specifically tell you just to regenerate your Entitlements.plist as it’s work completely differently now!

]]>