Normally, I just do 

defaults delete <bundle identifier> 

on the command line and that takes care of it. Issuing 

defaults domains

will give you a (comma-separated) print out of all the defaults domains on your 
mac.



Best


Phil


> On 20 Jan 2017, at 03:49, Daryle Walker <[email protected]> wrote:
> 
> I posted this on the Xcode list, but one of the respondents suggested adding 
> it here too….
> 
>> On Jan 15, 2017, at 8:11 PM, Daryle Walker <[email protected]> wrote:
>> 
>> I threw away an app I made in Xcode 7, including clearing its Git space and 
>> replacing it with an empty branch. I created a new app with Xcode 8. 
>> However, I used the same bundle ID for the two apps. When I first ran the 
>> new app, I saw preference mismatch errors. I realized that, since I used the 
>> same ID for both apps, the new app was looking at the old app’s data. I 
>> deleted the preference file and the Xcode derived data folder. But even now, 
>> the new app’s open-recent list has a file I opened in the old app.
>> 
>> I’m asking: where are all the locations used by both Xcode and the system 
>> that automatically leave bundle-ID-marked files after compiling and running?
> 
> — 
> Daryle Walker
> Mac, Internet, and Video Game Junkie
> darylew AT mac DOT com 
> 
> 
> _______________________________________________
> 
> Cocoa-dev mailing list ([email protected])
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/sqwarqdev%40icloud.com
> 
> This email sent to [email protected]


_______________________________________________

Cocoa-dev mailing list ([email protected])

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to