You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
Have use Printlife for a long time. Tried to launch today and got 'Unexpectedly Quit'. That said: EXC_CRASH (Code Signature Invalid).
How do I go about fixing this? I have deleted the app and associated files and downloaded a new copy. Still getting the same 'Unexpectedly Quit'. All other apps are working fine except Printlife.
Thanks in advance,
Mac mini (Late 2012), macOS Sierra (10.12.6)
macOS Sierra: If an app freezes or quits unexpectedly
If the behavior persists or you run into any trouble, please reach out again.Try setting up another admin user account to see if the same problem continues. If Back-to-My Mac is selected in System Preferences, the Guest account will not work. The intent is to see if it is specific to one account or a system wide problem. This account can be deleted later. Please post if this worked or not.
Isolating an issue by using another user account
If the problem is still there, try booting into the Safe Mode using your normal account. Disconnect all peripherals except those needed for the test. Shut down the computer and then power it back up after waiting 10 seconds. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. When you reboot normally, the initial reboot may be slower than normal. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart by using the application un-installer or by using the developer’s uninstall instructions. For each disable/delete, you will need to restart if you don't do them all at once. Please post if this worked or not.
Safe Mode - About El Capitan
also Sierra
Safe Mode Startup – El Capitan. also Sierra
If it works in the Safe Mode, try running this program when booted normally and then copy and paste the output in a reply. The program was created by Etresoft, a frequent contributor. Please use copy and paste as screen shots can be hard to read. Click “Share Report” button in the toolbar, select “Copy to Clipboard” and then paste into a reply. This will show what is running on your computer. No personal information is shown. You can run the report for free at least once, but if you run it several times, at some point it will ask you to pay a license fee.
Etrecheck – System Information
Hello Douglas,
You can't blame Apple for this problem. The developer needs to re-issue the executable. It is using an expired provisioning profile. I downloaded Printlife and it crash on me just like it does for you. I checked the app's signature using RB App Checker Lite on the Mac App Store. Mostly everything was fine, except for this section:
An embedded provisioning profile is present: “XC OSX: com.chronos.PrintLife”.
UUID: “aaf14419-7098-46b1-be64-ad29f2da0f16”.
Created on Oct 13, 2016.
Expired on Mar 12, 2018!
The profile specifies the application “PrintLife” (GTQ9M5W984).
The profile specifies the team “Chronos LLC” (GTQ9M5W984).
➤ The profile does NOT match the application's Team ID (GTQ9M5W984)!
There are no provisioned devices.
The profile was signed by 3 certificates.
The profile may be used by one developer:
Developer Certificate “Developer ID Application: Chronos LLC”.
This certificate was used to sign the bundle.
I'm certain this is the cause of the error.
Have already tried everything in your link and none of that works.
Below is the Unexpectedly Quit data:
Process: PrintLife [2281]
Path: /Applications/PrintLife.app/Contents/MacOS/PrintLife
Identifier: com.chronos.PrintLife
Version: ???
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: PrintLife [2281]
User ID: 503
Date/Time: 2018-03-19 08:16:11.881 -0700
OS Version: Mac OS X 10.12.6 (16G1212)
Report Version: 12
Anonymous UUID: 74C13EAF-4F27-2D61-B8C2-2C493797506C
Sleep/Wake UUID: DD94E418-EE7F-4633-BF68-B47BBF3304AB
Time Awake Since Boot: 20000 seconds
Time Since Wake: 1300 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (Code Signature Invalid)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace CODESIGNING, Code 0x1
kernel messages:
VM Regions Near 0 (cr2):
-->
__TEXT 00000001098f6000-0000000109aad000 [ 1756K] r-x/rwx SM=COW @j [(null)]
Thread 0 Crashed:
0 d\ 0x000000010cc1d000 _dyld_start + 0
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007fff56309c20
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x000000010cc1d000 rfl: 0x0000000000000200 cr2: 0x0000000000000000
Logical CPU: 0
Error Code: 0x00000000
Trap Number: 0
Binary Images:
0x1098f6000 - 0x109aacff7 +d\ (0) <D7ABE602-3F2A-37C4-8197-86C01D5CF88A> d\
0x10cc1c000 - 0x10cc59dc7 +d\ (433.5) <93EA668C-4BB2-3646-96E9-B406B81308D6> d\
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: 9836
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=2172K resident=0K(0%) swapped_out_or_unallocated=2172K(100%)
Writable regions: Total=8400K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8400K(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
STACK GUARD 56.0M 2
Stack 8192K 2
__DATA 540K 4
__LINKEDIT 168K 3
__TEXT 2004K 3
shared memory 8K 3
=========== ======= =======
TOTAL 66.7M 11
Model: Macmini6,2, BootROM MM61.010B.B00, 4 processors, Intel Core i7, 2.3 GHz, 8 GB, SMC 2.8f1
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x859B, 0x435435313236344246313630422E43313646
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x859B, 0x435435313236344246313630422E43313646
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x10E), Broadcom BCM43xx 1.0 (7.21.171.133.1a2)
Bluetooth: Version 5.0.5f1, 3 services, 27 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: APPLE HDD HTS541010A9E662, 1 TB
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Hub
USB Device: IR Receiver
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Keyboard Hub
USB Device: Apple Keyboard
USB Device: USB 3.0 Bus
USB Device: Apple USB SuperDrive
USB Device: MX880 series
Thunderbolt Bus: Mac mini, Apple Inc., 23.4
Tried a test account last night, no change. Just tried booting into Safe Mode, no change still unexpectedly quits.
The error message says Code Signature Invalid. There is an updated version of PrintLife in the AppStore. If I purchase that version would Apple still sell it if the Code Signature is invalid?
Douglas wrote:
I'm wondering why the AppStore would be selling software that will not launch due to 'expired provisioning profile'.
The App Store isn't selling the software. This is a question regarding the software being distributed from the company's own web site. Any software sold through Apple's App Store would have to pass a number of automated checks, at least one of which ensures the validity of the embedded provisioning profile.
Although a download from the App Store would be guaranteed to work after downloading, there is still no guarantee that the app would continue to work in the future. Again, it is up to the developer to keep their certificates up-to-date. The only difference about the App Store is that the app will no longer be available from the App Store once its internal certificates expire.
If PrintLife is checking with Apple to see if the certificate is current every time I launch, what happens if my computer is not connected to the internet? I don't recall seeing any warnings that in order for the product to work you had to be connected to the internet.
PrintLife is not checking with Apple. The provisioning profile is embedded inside the executable and it has expired. It doesn't need to connect to the internet to see that it has expired.
Also, this is not a certificate. It is a provisioning profile. A provisioning profile allows an app to use Apple's services at runtime, so there is an internet component to that. In this case, PrintLife wants to use Apple Maps.
Also, I didn't look very closely at the output from the certificate check I ran earlier. I just copied the text in red. I should have known better than that. Here is another section from the certificate check.
The signature contains 3 certificates.
Certificate “Apple Root CA”:
Your keychain contains this trusted root certificate.
Will expire on Feb 9, 2035.
Certificate “Developer ID Certification Authority”:
Will expire on Feb 1, 2027.
Certificate “Developer ID Application: Chronos LLC”:
Expired on Mar 12, 2018.
SHA1 fingerprint: “679AFE383027FC6BDBED8D6ECCC69E327B8F97A4”.
Team ID or Organizational Unit: “GTQ9M5W984”.
This matches the Team ID contained in the signature.
I added the emphasis above. The Application's Developer ID certificate has also expired.
Everything here is working as it should. When certificates expire, the app stops working. Perhaps it has been abandoned.
Are you saying that if I purchase PrintLife from the AppStore I am guaranteed that it will open and operate normally? According to something I read on the website, the AppStore & website downloads are the same. Is the AppStore allowed to go into an application and change the requisite expiration dates? If the AppStore can't do that then the version they are selling is the same version as the website which does not work.
I can't guarantee anything.
While the underlying code may be the same between the Mac App Store and website versions, they cannot be considered the same apps. There are enormous differences between those two environments. In no case does the Mac App Store make any changes to an app. It is always the developer's responsibility to keep the apps up-to-date and renew required certificates and provisioning profiles. These same kind of certificate problems can happen with Mac App Store apps too. There are more automated checks with the Mac App Store and sometimes human checks. Because a Mac App Store developer membership must be renewed each year, there is less of a chance of this kind of certificate problem.
Have you ever contacted the developer about this problem?
The developer does not respond to support requests which is the only way to contact them. There are support requests outstanding for over a year with no response. I have one for over 2 years with no response. The developer, contrary to what the website says, offers zero support.
I'm not trying to beat a dead horse here. However, Printlife from the Chronos website does not launch because their certificates are expired. If the AppStore does not change anything, change the certificates expiration dates, then the app I get from the AppStore will not launch either.
Apps that a developer uploads to the App Store must have a different set of certificates. They will not be the same as the download from the web site. I cannot guarantee that the App Store version will work, but I can guarantee that it will have different certificates.
After a very long google search finding officers and some phone numbers and leaving some messages and texts, today I find that PrintLife version 4 has been fixed and operates normally.
Working on getting them to fix version 3 now.
To the best of my knowledge, they wouldn't, but I'm not familiar with the application.
Code Signature Invalid
