Mac OS Big Sur compatibility issue

I totally agree with jcaustin. This is poor performance from logmein - it's now been about week with absolutely no communication from logmein about progress report on a fix for File Manager on Macs. Will be definitely looking for alternative to logmein

This is a real mess for my employees working from home. Logmein does not care none of there updates have fixed this issue. Support is no help this was a great product.  I am now looking for a change. 

When can we expect this to start working? I am not able to access the file manager, which is a big part of my job. 

Per the email subject: Mac OS BigSur and Logmein Client

Tbh I think LogMeIn knows about this.  It's widespread, not something isolated.

bradhs Credimus bradhs  This community thread specifically references Rescue services.  Are you all experiencing this with the Rescue endpoint, or another LogMeIn service such as Central/Pro ?

**  With regards to Rescue services, remote access / control will fully work, though currently TC is not yet supported on Big Sur.  It should be in the very near future: https://support.logmeinrescue.com/rescue/help/is-rescue-supported-on-macos-big-sur 

Thanks for your patience while we patch this problem up.

I'm getting the same error since the installing Big Sur beta, to moving to production on a MacBook Pro 2018.  AND now on a MacBook Pro M1.  AND so far everyone else that has moved to BigSur as well.

Also, I dare to ask when will native M1 code be available.

This is what it looks like on an M1. 

Process: LogMeIn Client [48478]
Path: /private/var/folders/*/LogMeIn Client.app/Contents/MacOS/LogMeIn Client
Identifier: com.logmein.ignition
Version: 4.1.7585 (4.1.0.7585)
Code Type: X86-64 (Translated)
Parent Process: ??? [1]
Responsible: LogMeIn Client [48478]
User ID: 502

Date/Time: 2020-11-23 07:01:37.461 -0800
OS Version: macOS 11.1 (20C5048k)
Report Version: 12

Time Awake Since Boot: 53000 seconds
Time Since Wake: 1400 seconds

System Integrity Protection: enabled

Notes: Translocated Process

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000007fa3c47dd0f
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [48478]

We see the exact same problem. It's only the File Transfer that's experiencing this. Here is the Error :

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000001fc
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [12132]

Same Here

The destination are Windows computers--lots of them.  The issue is with the LogMeIn Client.

Try installing the Unattended version there, then see if that improves the performance.