Accidently deleted my App Store's PLIST, now this happens.

[N e e k]

I was trying to edit the plist in the App Store so it wouldn't show a badge alert. It was a success, but I didn't know I needed the copy, so I deleted it the original. Now, it won't work at all. This is what it says when I try to open the App Store.

"Process: App Store [449]
Path: /Applications/App Store.app/Contents/MacOS/App Store
Identifier: com.apple.appstore
Version: ???
Build Info: Commerce-355000000000000~4
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: App Store [449]
User ID: 502

Date/Time: 2014-07-23 10:03:30.296 -0500
OS Version: Mac OS X 10.10 (14A283o)
Report Version: 11
Anonymous UUID: B9817145-7D84-A4FA-F5EF-F4339A51EF58


Time Awake Since Boot: 670 seconds

Crashed Thread: 0

Exception Type: EXC_CRASH (Code Signature Invalid)
Exception Codes: 0x0000000000000000, 0x0000000000000000

kernel messages:

VM Regions Near 0x7fff7537b0a8 (cr2):
__LINKEDIT 00007fff675d4000-00007fff675e8000 [ 80K] r--/rwx SM=COW /usr/lib/dyld
--> Submap 00007fff70000000-00007fff80000000 [256.0M] r--/rwx SM=PRV process-only VM submap
unused shlib __DATA 00007fff736d9000-00007fff75c24000 [ 37.3M] rw-/rw- SM=COW system shared lib __DATA not used by this process

Thread 0 Crashed:
0 dyld 0x00007fff67565000 _dyld_start + 0

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x000000000000000d rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007fff5015ab48
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x00007fff67565000 rfl: 0x0000000000000201 cr2: 0x00007fff7537b0a8

Logical CPU: 0
Error Code: 0x020000f4
Trap Number: 133


Binary Images:
0x7fff67564000 - 0x7fff6759a67f dyld (???) <D8593292-21DF-3B34-97D1-C9CBEA96E193> /usr/lib/dyld

External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 417
thread_create: 0
thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=300K resident=296K(99%) swapped_out_or_unallocated=4K(1%)
Writable regions: Total=8416K written=0K(0%) resident=12K(0%) swapped_out=0K(0%) unallocated=8404K(100%)

REGION TYPE VIRTUAL
=========== =======
STACK GUARD 56.0M
Stack 8192K
VM_ALLOCATE 8K
VM_ALLOCATE (reserved) 4K reserved VM address space (unallocated)
__DATA 228K
__LINKEDIT 80K
__TEXT 220K
mapped file 40K
shared memory 4K
=========== =======
TOTAL 64.6M
TOTAL, minus reserved VM space 64.6M"

Any help is appreciated, I can't update to DP4 because it won't open.

 

[maflynn]

Is it still in the trash?

 

[Bruno09]

Have you tried restarting the Mac ?

 

[N e e k]

It's not in the trash. Restarting my mac does nothing. Why is it now that if you delete a .plist it just stays deleted? I thought it would bring back a fresh one like it always used to.

 

[maflynn]

You copied the plist, edited the copy and deleted the original.

Can you undo your edits to get the plist back to what it was?

 

[N e e k]

You copied the plist, edited the copy and deleted the original.

Can you undo your edits to get the plist back to what it was?

I didn't just recently do it. It was a while ago, and since I don't use the App Store frequently I forgot, but now I need to update and I just remembered it doesn't work.

 

[Takuro]

If you still have one of the Yosemite upgrade dmg files, you can use something like Pacifist to open it up and extract the App store app individually. Within the Yosemite installer app, this is under Contents > SharedSupport > InstallESD.dmg. The App Store app is under OSInstall.mpkg > EssentialSystemSoftware > EssentialSystemSoftwareGroup > Essentials.pkg if you browse the dmg file in Pacifist.

If you don't have this, you're S.O.L. Maybe if you actually said what plist you mistakenly edited, somebody could just post it here if they are still running DP3. Frankly, I have no idea why you posted the crash logs, as if we're going to somehow interpret it...

 

[jadot]

Firstly, the crash report means nothing to nearly everybody.

I don't know what your setup is but have you looked through Time Machine?
Also, are you running the current plist as a copy? Is it called "copy" because it's in the same location as the original?

Why anybody is messing around with this stuff without covering their tracks in a DP is beyond me. It astonishes me how many non developers apparently run an unfinished OS on their main computer. There's a laughable amount of "Please Help" pleas on these forums.

Do yourself a favour - don't mess around with stuff you know nothing about. It always ends badly.

Restore, back up, wait for the public release.

 

[N e e k]

Firstly, the crash report means nothing to nearly everybody.

I don't know what your setup is but have you looked through Time Machine?
Also, are you running the current plist as a copy? Is it called "copy" because it's in the same location as the original?

Why anybody is messing around with this stuff without covering their tracks in a DP is beyond me. It astonishes me how many non developers apparently run an unfinished OS on their main computer. There's a laughable amount of "Please Help" pleas on these forums.

Do yourself a favour - don't mess around with stuff you know nothing about. It always ends badly.

Restore, back up, wait for the public release.

What does this have to do with a pre-release software? If I was running Mavericks the same thing would've happened. I'm not complaining that the app doesn't work BECAUSE of the software... it's something I DID regardless. The software has nothing to do with it.

----------

If you still have one of the Yosemite upgrade dmg files, you can use something like Pacifist to open it up and extract the App store app individually. Within the Yosemite installer app, this is under Contents > SharedSupport > InstallESD.dmg. The App Store app is under OSInstall.mpkg > EssentialSystemSoftware > EssentialSystemSoftwareGroup > Essentials.pkg if you browse the dmg file in Pacifist.

If you don't have this, you're S.O.L. Maybe if you actually said what plist you mistakenly edited, somebody could just post it here if they are still running DP3. Frankly, I have no idea why you posted the crash logs, as if we're going to somehow interpret it...

I don't know. I just posted it because I wanted to give as much info as I could...

 

[iPhil]

What does this have to do with a pre-release software? If I was running Mavericks the same thing would've happened. I'm not complaining that the app doesn't work BECAUSE of the software... it's something I DID regardless. The software has nothing to do with it.

----------



I don't know. I just posted it because I wanted to give as much info as I could...

Re download the OS that MAS is messed up part of then use Pacifist to extract MAS app from the installer re-drag the app back into app folder..

 

[w0lf]

What exactly did you delete?

I'd just delete your modified plist and it should create a new one.

 

[iPhil]

What exactly did you delete?

I'd just delete your modified plist and it should create a new one.

The orignal plist for the MAS that file is what OP deleted

 

[w0lf]

The orignal plist for the MAS that file is what OP deleted

> implying there is only 1 plist that effects the App Store...

 

[Takuro]

The OP still hasn't said what plist file he modified. I they're too proud to admit that they either don't remember or don't understand the question, meaning they should have likely not been modifying a plist file in the first place. We can't help.

You do realize that a "plist" is a type of file commonly used within Mac OS to store arrays of data for programs (usually related to settings), and it's a generic term, right? Most apps have upwards of 10-20 or more plist files within not only the app itself, but their Application Support folders and within the System/Preferences folder. Basically you could not have been more vague in your request for help… You may as just as well have said, "Help, I changed an arbitrary file in my OS and it's broken now."

http://en.wikipedia.org/wiki/Property_list

If you had Time Machine backups, you would not have this issue, so now you're going to have to reinstall the OS. Lesson learned (hopefully.)