Re: PRODUCT_BUNDLE_IDNTIFIER messes up LS?
Re: PRODUCT_BUNDLE_IDNTIFIER messes up LS?
- Subject: Re: PRODUCT_BUNDLE_IDNTIFIER messes up LS?
- From: Quincey Morris <email@hidden>
- Date: Tue, 22 Sep 2015 13:45:29 -0700
- Feedback-id: 167118m:167118agrif8a:167118s3XycmWZAC:SMTPCORP
On Sep 22, 2015, at 11:43 , Christiaan Hofman <email@hidden> wrote:
But somehow the registration of the ID in LS seems to be done before that expansion is done, because the defaults command thinks it’s “${PROJECT_BUNDLE_IDENTIFIER}” rather than what it is expanded into.
There’s another possibility, which is that there’s another build of the app that *does* have the unexpanded string as its bundle ID. This could be, for example, because you built the app one time before setting all of the build settings appropriately.
It used to be possible to peer into the LS database using lsregister, but I don’t see that this is around any more. If you can find something to dump the information, you should be able to see the path to the app it thinks has the wrong bundle ID.
|
_______________________________________________
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