"LogMeIn Client" is not optimized for your Mac.
Does logmein not give a crap about their software of the Mac anymore? I've been getting this message for months now.
Forum Discussion
Hi nikhsub1
We do have plans to release a 64 bit version of our software but, I currently do not have a release date that I can share. While High Sierra shows this message about 32 bit applications, they continue to function normally and Apple has not ended support for them yet. After clicking OK that message should not be displayed again for that application.
But with the announcement of Mac OS10.14 today they are moving rapidly to the day when they will not support 32 bit apps any longer. I would STRONGLY suggest that LogMeIn accelerate their development to ensure that your Mac users are not left behind this fall. At the very least provide us with a time table so we can make appropriate plans if you are unable to support us.
A client wants to know if a date has been set yet for the release of a 64 bit version of LogMeIn for Mac?
He keeps getting the message: not optimize for your Mac and need to be updated, it will not work in future versions of MacOS.
Curious if anyone else is having this issue and if a fix is in the works.
Thanks.
Having same problem, productivity killer. 5 min connection max before OS throws error.
Macbook Pro 9,1; LMI Version 4.1.5877 (PlugIn: 1.0.1048)
Thank you, MRMinSF .
Stalkingcorw If you could share the same information with us, OS X version number, the related Mac TC or applet version number and any error messages?
We have also been experiencing this issue but have waited for Mojave GM to raise.
logmein crashes when the window focus moves from logmein to another window while a session is open.
If logmein client is idle without a session being rendered, the app will run without crashing.
- Version 4.1.6927 (PlugIn: 1.0.1948)
- MacOS Mojave 10.14 (18A391)
- Occurs on multiple machines.
Process: LogMeIn Client [16743] Path: /Applications/LogMeIn Client.app/Contents/MacOS/LogMeIn Client Identifier: com.logmein.ignition Version: 4.1.6927 (4.1.0.6927) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: LogMeIn Client [16743] User ID: 502 Date/Time: 2018-09-27 09:22:07.620 +0100 OS Version: Mac OS X 10.14 (18A391) Report Version: 12 Bridge OS Version: 3.0 (16P375) Anonymous UUID: C6519E8B-13DA-72FF-2A82-2CA4B157AC94 Sleep/Wake UUID: 9EA165ED-1740-4D57-BCD1-EAC0E35E1ABA Time Awake Since Boot: 170000 seconds System Integrity Protection: enabled Crashed Thread: 0 TLMIApplicationMain Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Illegal instruction: 4 Termination Reason: Namespace SIGNAL, Code 0x4 Terminating Process: exc handler [16743] Application Specific Information: *** CFRelease() called with NULL *** Thread 0 Crashed:: TLMIApplicationMain Dispatch queue: com.apple.main-thread 0 com.apple.CoreFoundation 0x00007fff523ac55e CFRelease + 109 1 com.logmein.remctrlplugin 0x0000000116126656 0x11603b000 + 964182 2 com.logmein.remctrlplugin 0x000000011605a769 0x11603b000 + 128873 3 com.logmein.remctrlplugin 0x000000011605a5fd 0x11603b000 + 128509 4 com.logmein.remctrlplugin 0x000000011605cc6b 0x11603b000 + 138347 5 com.logmein.remctrlplugin 0x000000011605e4a5 0x11603b000 + 144549 6 com.logmein.remctrlplugin 0x0000000116124d7c 0x11603b000 + 957820 7 com.logmein.remctrlplugin 0x000000011611d29a 0x11603b000 + 926362 8 com.apple.AppKit 0x00007fff4fa5f205 _NSViewDrawRect + 66 9 com.apple.AppKit 0x00007fff4fa5dabd -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inContext:shouldChangeFontReferenceColor:stopAtLayerBackedViews:] + 1545 10 com.apple.AppKit 0x00007fff4fa5d4a2 __46-[NSView(NSLayerKitGlue) drawLayer:inContext:]_block_invoke + 192 11 com.apple.AppKit 0x00007fff4fa5d201 -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 1769 12 com.apple.QuartzCore 0x00007fff5d371aaf CABackingStoreUpdate_ + 577 13 com.apple.QuartzCore 0x00007fff5d3d3325 invocation function for block in CA::Layer::display_() + 53 14 com.apple.QuartzCore 0x00007fff5d370c90 -[CALayer _display] + 1839 15 com.apple.AppKit 0x00007fff4fa5c75a _NSBackingLayerDisplay + 531 16 com.apple.AppKit 0x00007fff4fa40cc9 -[_NSViewBackingLayer display] + 811 17 com.apple.QuartzCore 0x00007fff5d3701bc CA::Layer::display_if_needed(CA::Transaction*) + 634 18 com.apple.QuartzCore 0x00007fff5d35e447 CA::Context::commit_transaction(CA::Transaction*) + 319 19 com.apple.QuartzCore 0x00007fff5d35dd20 CA::Transaction::commit() + 576 20 com.apple.AppKit 0x00007fff4fa378f5 __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 274 21 com.apple.CoreFoundation 0x00007fff5243b95d __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 22 com.apple.CoreFoundation 0x00007fff5243b892 __CFRunLoopDoObservers + 452 23 com.apple.CoreFoundation 0x00007fff523dd3c5 __CFRunLoopRun + 1166 24 com.apple.CoreFoundation 0x00007fff523dcce4 CFRunLoopRunSpecific + 463 25 com.apple.HIToolbox 0x00007fff51676895 RunCurrentEventLoopInMode + 293 26 com.apple.HIToolbox 0x00007fff516764d4 ReceiveNextEventCommon + 371 27 com.apple.HIToolbox 0x00007fff51676348 _BlockUntilNextEventMatchingListInModeWithFilter + 64 28 com.apple.AppKit 0x00007fff4f93395b _DPSNextEvent + 997 29 com.apple.AppKit 0x00007fff4f9326fa -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1362 30 com.apple.AppKit 0x00007fff4f92c75d -[NSApplication run] + 699 31 com.apple.AppKit 0x00007fff4f91be97 NSApplicationMain + 780 32 LogMeIn Client 0x0000000109462864 0x109456000 + 51300 33 libdyld.dylib 0x00007fff7f472085 start + 1
LMI Central customer here. Upgraded to Mojave. LogMeIn client crashes everytime you switch applications with a session open. Any known fixes for this issue?
Edit: Sorry posted this in wrong thread, can a mod move this.
This issue has been a Support Case with LogMeIn technical support.
Currently, no workaround or options available for users who want to use LogMeIn Pro on a MAC running Mojave. That's the official word I've been told by LogMeIn.
