Problema ao Atualizar para o MACOS Sequoia

[klausperes]

Prezados, após atualizar o MACOS para a versão Sequoia, não consigo mais me conectar em nenhum appserver, fica conectando mas não completa. Observei o LOG na seção TOTVS LS do VsCode e foi descrito o seguinte:

[Info - 09:08:46] Initializing Language Server.
Version: totvsls 2.0 (Rev.: Last Changed Rev: 42514)
[Info - 09:08:47] Language Server initialized.
[Info - 09:08:47] Developer Support Subsystem initialized.

Loguru caught a signal: SIGSEGV
Stack trace:
12 0x7ff8170f6bef thread_start + 15
11 0x7ff8170fb253 _pthread_start + 99
10 0x1007a50cf void* std::__thread_proxy<std::tuple<std::unique_ptr<std::__thread_struct, std::default_deletestd::__thread_struct>, WorkThread::_StartThread(std::string const&, std::function<void ()>)::$_0>>(void*) + 63
9 0x100777e67 std::__function::__func<QueueManager::LaunchLsThread(bool)::$_0, void ()>::operator()() + 759
8 0x10065c46e BaseMessageHandler<(anonymous namespace)::In_TextDocumentDidOpen>::Run(std::shared_ptr) + 366
7 0x10065cafb (anonymous namespace)::Handler_TextDocumentDidOpen::Run((anonymous namespace)::In_TextDocumentDidOpen*) + 1163
6 0x1007dcef6 WorkspaceFile::doProcess(DBCodeAction, std::function<void (std::vector)>) + 3238
5 0x10079de7d TotvsLinter::callAdvplC(CallAdvplCParams const) + 2477
4 0x1007b2e31 tAdvplc::run() + 7601
3 0x10158288f executeAppreDll(int, char*, tString&, tString&, tString&, tString&, char*, std::function<void (tAbstractParserInterface*)>) + 655
2 0x101578124 Preprocessor(int, char**, tString&, tString&, tString&, bool, tString*, char*, std::function<void (tAbstractParserInterface*)>) + 1012
1 0x101576bd8 ParseCommandLine(int, char**, tAutoArray&, tString&, tAutoArray&, tString&, unsigned char&, unsigned char&, tString&, tString&, unsigned char&, unsigned char&, unsigned char&, tString&) + 2184
0 0x0 4 ??? 0x0000000000000000 0x0 + 0
( 0.792s) [languageServer ] :0 | Signal: SIGSEGV
/Users/klausperes/.vscode/extensions/totvs.tds-vscode-2.0.9/node_modules/@totvs/tds-ls/bin/mac/advpls: line 17: 8296 Segmentation fault: 11 "$tmp/$prog" ${1+"$@"}
[Info - 09:08:47] Connection to server got closed. Server will restart.
true
[Info - 09:08:53] Initializing Language Server.
[Info - 09:08:54] Language Server initialized.
[Info - 09:08:54] Developer Support Subsystem initialized.

Loguru caught a signal: SIGSEGV
Stack trace:
12 0x7ff8170f6bef thread_start + 15
11 0x7ff8170fb253 _pthread_start + 99
10 0x10242c0cf void* std::__thread_proxy<std::tuple<std::unique_ptr<std::__thread_struct, std::default_deletestd::__thread_struct>, WorkThread::_StartThread(std::string const&, std::function<void ()>)::$_0>>(void*) + 63
9 0x1023fee67 std::__function::__func<QueueManager::LaunchLsThread(bool)::$_0, void ()>::operator()() + 759
8 0x1022e346e BaseMessageHandler<(anonymous namespace)::In_TextDocumentDidOpen>::Run(std::shared_ptr) + 366
7 0x1022e3afb (anonymous namespace)::Handler_TextDocumentDidOpen::Run((anonymous namespace)::In_TextDocumentDidOpen*) + 1163
6 0x102463ef6 WorkspaceFile::doProcess(DBCodeAction, std::function<void (std::vector)>) + 3238
5 0x102424e7d TotvsLinter::callAdvplC(CallAdvplCParams const) + 2477
4 0x102439e31 tAdvplc::run() + 7601
3 0x10320988f executeAppreDll(int, char*, tString&, tString&, tString&, tString&, char*, std::function<void (tAbstractParserInterface*)>) + 655
2 0x1031ff124 Preprocessor(int, char**, tString&, tString&, tString&, bool, tString*, char*, std::function<void (tAbstractParserInterface*)>) + 1012
1 0x1031fdbd8 ParseCommandLine(int, char**, tAutoArray&, tString&, tAutoArray&, tString&, unsigned char&, unsigned char&, tString&, tString&, unsigned char&, unsigned char&, unsigned char&, tString&) + 2184
0 0x0 4 ??? 0x0000000000000000 0x0 + 0
( 0.790s) [languageServer ] :0 | Signal: SIGSEGV

[klausperes]

Prezados, consegui conectar nos servidores instalando uma Extensão bem mais antiga, a 2.0.3 de 8 meses atrás.
Tem alguma previsão de uma nova versão da Extensão?

[heltonsystem]

@klausperes, muito obrigado! Estava com o mesmo problema aqui. resolveu, mas espero que saia logo um update para esse problema.