Crash when creating pdf on Mac after installing Ver 21.1.23

macOS Catalina officially runs on all standard configuration Macs that supported Mojave. The only reason not to update would be that Catalina does not support ancient, 32-bit apps. But they are no longer supported by their developers, either.

The reason system requirements for Manager have not been modified is that the developer cannot duplicate the problem with Mojave that an extremely small number of users have reported. If there is an issue, it has only been reported with macOS 10.14.6.

I also note that 10.14.6 had a dozen security updates. Have you installed all of those? It is possible an incompatibility arose in one of the security updates that did not show up in testing.

I am having this problem also. Never tried printing before, so can’t vouch for when it broke. I’m on MacOS 10.13.6 and Manager 21.1.47. Exactly as OP stated. Clicking “print” gives a missing application pop-up, and clicking PDF causes a crash.

Steps to reproduce:

  1. Open Reports.
  2. Open profit and loss.
  3. Open a saved report I made for FY 2020. It opens just fine.
  4. Click “Print”. Receive same error as OP, that it can’t find an application for URL “eto:print”. Close this and application resumes gracefully.
  5. With same report open, click "PDF. " Animation suggests it’s thinking how to do it, but then the whole Manager.io window turns blank and remains open for a few seconds before disappearing and crashing with SIGABRT.

Equally reproducible without clicking “Print” first and just going straight to the PDF.

Here’s a bit of the stack trace and crash info:
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
System.AggregateException: One or more errors occurred. (Exception of type 'MonoMac.Foundation.NSErrorException' was thrown.)
 ---> MonoMac.Foundation.NSErrorException: Exception of type 'MonoMac.Foundation.NSErrorException' was thrown.
   at Eto.Mac.Forms.Controls.WKWebViewHandler.ExecuteScriptAsync(String script)
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
   at System.Threading.Tasks.Task`1.get_Result()
   at Eto.Mac.Forms.Controls.WKWebViewHandler.SetupContextMenu()
   at Eto.Mac.Forms.Controls.WKWebViewHandler.EtoNavigationDelegate.DidFinishNavigation(WKWebView webView, WKNavigation navigation)
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff71be0b66 __pthread_kill + 10
1   libsystem_pthread.dylib       	0x00007fff71dab080 pthread_kill + 333
2   libsystem_c.dylib             	0x00007fff71b3c1ae abort + 127
3   libcoreclr.dylib              	0x000000010329492e PROCAbort + 30
4   libcoreclr.dylib              	0x0000000102e67897 PROCEndProcess(void*, unsigned int, int) + 215
5   libcoreclr.dylib              	0x000000010329749c UnwindManagedExceptionPass1(PAL_SEHException&, _CONTEXT*) (.cold.4) + 44
6   libcoreclr.dylib              	0x00000001030b6a2e UnwindManagedExceptionPass1(PAL_SEHException&, _CONTEXT*) + 830
7   libcoreclr.dylib              	0x00000001030b6ab6 DispatchManagedException(PAL_SEHException&, bool) + 134
8   libcoreclr.dylib              	0x000000010301a144 IL_Throw(Object*) + 548
9   ???                           	0x0000000111817349 0 + 4588663625
10  ???                           	0x00000001118172b4 0 + 4588663476
11  ???                           	0x0000000115583a17 0 + 4653070871
12  ???                           	0x00000001155838c2 0 + 4653070530
13  com.apple.WebKit              	0x00007fff5878c687 WebKit::NavigationState::NavigationClient::didFinishNavigation(WebKit::WebPageProxy&, API::Navigation*, API::Object*) + 93
14  com.apple.WebKit              	0x00007fff5895355e WebKit::WebPageProxy::didFinishLoadForFrame(unsigned long long, unsigned long long, WebKit::UserData const&) + 316
15  com.apple.WebKit              	0x00007fff5896f337 void IPC::handleMessage<Messages::WebPageProxy::DidFinishLoadForFrame, WebKit::WebPageProxy, void (WebKit::WebPageProxy::*)(unsigned long long, unsigned long long, WebKit::UserData const&)>(IPC::Decoder&, WebKit::WebPageProxy*, void (WebKit::WebPageProxy::*)(unsigned long long, unsigned long long, WebKit::UserData const&)) + 100
16  com.apple.WebKit              	0x00007fff587884a1 IPC::MessageReceiverMap::dispatchMessage(IPC::Connection&, IPC::Decoder&) + 127
17  com.apple.WebKit              	0x00007fff589c4324 WebKit::WebProcessProxy::didReceiveMessage(IPC::Connection&, IPC::Decoder&) + 24
18  com.apple.WebKit              	0x00007fff5875588d IPC::Connection::dispatchMessage(std::__1::unique_ptr<IPC::Decoder, std::__1::default_delete<IPC::Decoder> >) + 119
19  com.apple.WebKit              	0x00007fff587583e4 IPC::Connection::dispatchOneMessage() + 176
20  com.apple.JavaScriptCore      	0x00007fff4d73018f WTF::RunLoop::performWork() + 479
21  com.apple.JavaScriptCore      	0x00007fff4d730332 WTF::RunLoop::performWork(void*) + 34
22  com.apple.CoreFoundation      	0x00007fff49ab5b01 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17

System info:
Model Name: MacBook Pro
Model Identifier: MacBookPro8,2
Processor Name: Intel Core i7
Processor Speed: 2.5 GHz
Number of Processors: 1
Total Number of Cores: 4
Memory: 16 GB

Thanks for your assistance. I hope this helps.

Andrew

No, as it has been reported with macOS 10.13.6 and 10.14.1 also. However, it appears that updating from Manager 21.1.6 to Manager 21.1.7 has triggered all the issues that these numerous users have experienced as noted by @Damien_C observation:

It would appear that users with older mac machines will be locked into Manager 21.1.6 until such time that they upgrade their hardware.

The first such reports came 6 days after I wrote that the problem had only been reported on 10.14.6. And my very next sentence was, “That does not mean there are not more.”

Hi, I appear to be having the same problem with my Mac as well since the same update. Updated to version 21.1.55 today & the same issue occurs. i.e. press pdf button grey screen opens up- pause- manager crashes I also copy in the error report. Im not technical so my understanding of the crash report is limited:

Process: ManagerDesktop [1449]
Path: /Applications/Manager.app/Contents/MacOS/ManagerDesktop
Identifier: io.manager
Version: 21.1.55 (1)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: ManagerDesktop [1449]
User ID: 501

Date/Time: 2021-01-30 12:22:25.431 +0000
OS Version: Mac OS X 10.14.6 (18G6042)
Report Version: 12
Anonymous UUID: 73666D5E-AA82-62D9-CC72-C753A462606F

Sleep/Wake UUID: B1D98266-4F61-420F-95AD-2A50704AD5D7

Time Awake Since Boot: 6400 seconds
Time Since Wake: 3800 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
System.AggregateException: One or more errors occurred. (Exception of type ‘MonoMac.Foundation.NSErrorException’ was thrown.)
—> MonoMac.Foundation.NSErrorException: Exception of type ‘MonoMac.Foundation.NSErrorException’ was thrown.
at Eto.Mac.Forms.Controls.WKWebViewHandler.ExecuteScriptAsync(String script)
— End of inner exception stack trace —
at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at Eto.Mac.Forms.Controls.WKWebViewHandler.SetupContextMenu()
at Eto.Mac.Forms.Controls.WKWebViewHandler.EtoNavigationDelegate.DidFinishNavigation(WKWebView webView, WKNavigation navigation)
abort() called

@Damien_C , @Leo_Visser, @Pagee , @strothei , @MuttakiNl , @rajbhansali , @dram , @stylechild , a problem similar to yours was reported by another user. He found that it disappeared after he completely shut down his Mac and restarted it. (Not just a restart; not put it to sleep and woke it up; but a hard shutdown.)

Could you try that and let us know if your problem resolved?

@Tut blank screen issue is related to Windows so this won’t help.

There are more problems than a blank screen mentioned in this thread. Have you now identified that they are all related?

I’m not quite sure whether this issue will be fixed. Both High Sierra and Mojave no longer receive bug fixes from Apple. I’m awaiting guidance from third-party programmer to see if this is fixable and whether we can continue supporting High Sierra and Mojave or we will have to bump up minimal requirements to Catalina or higher.

@Tut - Thanks for your reply.

I shut down completely. After booting, I opened Manager straight away and into Reports → Profit and Loss → [saved report] → View → PDF. This time the app window went completely blank with not even any words in the title bar. It did this previously, but crashed nearly right away. This time, it’s sat here a couple of minutes totally blank without crashing.

Oh wait…

I’m typing this from a second computer and Manager crashed literally as I finished typing the preceding paragraph to say it wasn’t crashing. That’s hilarious. Must’ve stayed open 2 whole minutes at that blank screen before crashing. At a glance, the stack trace looks roughly the same as before.

After re-opening Manager, I tried printing the report. Same deal as before, with no application found for eto:print. Restart doesn’t seem to help as you’d hoped.

FWIW, I know my 2011 Macbook Pro (pre-retina) is crazy old; I’ve been living on borrowed time with it for a few years. Now that the GPU is incompatible with newer OSes, it’s a dead end. This issue was the final straw in making me decide to upgrade. I inherited a late-2013 MBP for free that’s been sitting on my workbench for a couple of years gathering dust. Today I replaced the battery, installed an SSD, and got a MagSafe 1 to MagSafe 2 adapter so I could charge it with all my old chargers. $210 USD and half-a-day of work and now I’m on Big Sur with a machine that ought to last at least a couple of years.

I hope you are able to find a solution for others, but now that I’m on Big Sur, I’m all set. FYI, it all works fine on the new machine and OS.

Thanks,
strothei

Well, @strothei, that is good news. Ironically, the first reports of freezes, crashes, or blank screens with macOS came from early adopters of Big Sur. Then we started seeing reports on the forum of similar behavior with High Sierra and Mojave. Very perplexing.

Hi Damian, I tried everything en full shutdown; and after desperate attempt just paid for a year"s online cloud version which works fine, it only give errors when I want to send emails via that system. It is costing us more in tine and effort than to just pay the subscription as I am not only the bookkeeper of the office but also man the reception as well as manage the office. Will see in futue if Manager get it right to fix the error in their system, but till then I will have to dig into my pocket to keep the Tax Office off our backs with penalties and interest …lol. But thanks for all your assistance, it is mostly appreciated .

Kind regards
Leo

I have updated the OS to BigSUR and issue is partly solved. Now i am able to generate PDF and print also but Manager crashes after printing the document.

Hello Leo,
Glad I could help and you were able to resolve to your satisfaction. Meanwhile I am still stuck with Ver 21.1.6 on Mojave 10.14.6 which is okay for now. However, I look forward to the possibility of a forthcoming solution that may eventuate from @lubos working with the third-party programmer. It certainly would be most welcome.
Regards,
Damien

1 Like

I am experiencing the same problems. Printing isn’t possible and Backup does not save file anymore.

Running the latest desktop-version 21.2.25 on MacOS 10.13.6 (High Sierra). Tested it on two other High Sierra Mac’s: same problem.

Please help!

Hello @HansL,

See post #57 above, I believe this may also be the only solution for (High Sierra) you are locked into Ver 21.1.6 until @lubos is able to resolve if possible with his third-party programmer.

Regards,
Damien

@HansL, have you tried the shut-down and restart l described in my post #57 above? I tried to replicate these problems on macOS 10.13.6 and could not.

@Tut, complete shutdown and restart as in post #70 above does not resolve problem for me on Mojave 10.14.6.

Thanks, I will go back to version 21.1.6 for the time being.

Thanks Damien, I will go back to version 21.1.6 for the time being.