Re: Clean command fail cured
Re: Clean command fail cured
- Subject: Re: Clean command fail cured
- From: Jeff Evans <email@hidden>
- Date: Sat, 10 Dec 2011 10:51:20 -0800
Fritz,
That did it. Thanks for a very informative post. As usual, my error turned out to be boneheaded.
I didn't know that the application name is munged into the hex id. The problem was apparently that the bundle name in the plist did not match the one used to build the identifier: the actual bundle name was two words with a space between; the name in the i.d. did not have the space. I changed the bundle name to run the two words together and that was all it took.
Now if I want to have a two-word title again I suppose I'll need to revisit the portal and get a new i.d.
Maybe I'll just leave things as they are for the time being.
Jeff
On Dec 10, 2011, at 9:50 AM, Fritz Anderson wrote:
The build directory is a red herring. Drop that line of inquiry.
You don't mention whether you deleted the previous edition of your app from the iOS Simulator before trying the new one. Do that. If you haven't done so already, that may be your whole problem. But you also have to clean up your app ID.
If you do this in the terminal (substitute the items in braces):
$ find '{your project directory}' -type f -print0 | xargs -0 grep '{old company prefix}'
… you will probably not find any references, meaning your old identifier is not lingering anywhere (except maybe in a source-control repository). Come back here if that isn't the case.
Now examine the actual Info.plist precursor for your target (point a plain-text editor at {your target name}-Info.plist, or just use the less command in Terminal). You should see something like this:
<key>CFBundleIdentifier</key>
<string>{new prefix}.${PRODUCT_NAME:rfc1034identifier}</string>
Does {new prefix} include the hex string from Apple's generated identifier? DELETE IT, preferably using the Info tab of the Target editor (see later for details). Your latest message implies you haven't tried this.
You see that by default the last part of the identifier that Xcode constructs is a munged version of your product name. If that's the case in your file, does your intended bundle identifier match the target's product name?
If not (and maybe you should do this anyway), select the target in the Project editor, and then the Info tab. This contains an editor for the target's Info.plist precursor file. Select the value for the "Bundle identifier" entry, and paste in your intended identifier. (DO NOT include that hex string.)
Try again.
— F
On 10 Dec 2011, at 10:45 AM, Jeff Evans wrote:
> But the wording of your question raises a point: when I created the bundle ID at the portal I also changed the latter part of it: the com.mycompany.productname part. That had previously contained some default text from the initial file created by XCode, and I had fiddled with that a bit. Now I'm thinking that maybe changing that was the critical error. The question is: is there any way to fix it? The bundle ID previously in place would not be suitable.
> I've tried deleting the entire build folder. But there is probably a reference to that old bundle i.d. somewhere in the project that is causing this.
--
If this email is spam, report it to
https://support.onlymyemail.com/view/report_spam/MTAxOTYyOjEzNjMwMTg5Mjc6amV2YW5zQGFycy1ub3ZhLmNvbTpkZWxpdmVyZWQ
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden