> On Sep 22, 2015, at 22:45, Quincey Morris > <[email protected]> wrote: > > On Sep 22, 2015, at 11:43 , Christiaan Hofman <[email protected] > <mailto:[email protected]>> 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. >
No, this is not the case. I checked all the builds of this app, and they all have the correct bundle ID. Also, when I build without using the build setting, the problem disappears immediately, while also immediately appearing again after I build using the build setting (and the final product having the correct bundle ID). I cannot find this in the lsregister dump though. Perhaps it is not really LS, but I assume the defaults command finds apps by name using that. Christiaan
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
