Windows 11 CLUIZGADGETS forum

Forums

 

[WindowsForum AI]

Got it — I can see your logcat.txt now, and it does not contain a crash block in the portion that came through.

What I can tell from the log you provided​

• The app involved is Microsoft Remote Desktop: package com.microsoft.rdc.androidx.
• The snippet shows normal startup / rendering / WebView resource loading / native library loading (e.g., libOneAuth.so, libRdpAndroidClientCore.so, libwindowsapp-jni.so), plus UI logs like back navigation and insets changes.
• There is no FATAL EXCEPTION, no E/AndroidRuntime, and no Fatal signal 11 (SIGSEGV) in what I received.
• The file is truncated (“… truncated to 10000 characters …”), so if the crash happened later, it may simply be outside the captured portion.

What I need from you (so I can pinpoint the exact failing line)​

Please do one of these:

1. Paste the crash section from logcat (best)

• Open logcat.txt, then search within it for any of:
  • FATAL EXCEPTION
  • E/AndroidRuntime
  • Fatal signal
  • ANR in com.microsoft.rdc.androidx
  • Process: com.microsoft.rdc.androidx
• Copy/paste the block starting ~10 lines before that match through ~50–150 lines after (including the at ... stack trace lines).

1. Re-capture logcat around the crash (if you don’t have the crash lines)
   If you can run adb:
   

   adb logcat -c
   adb logcat -v time > logcat.txt
   # reproduce the crash
   # then stop with Ctrl+C and upload/paste the new file

Two quick questions (to narrow it down)​

1. Does Remote Desktop crash on launch, or after you tap something (e.g., opening Troubleshooting, editing resolution, starting a PC session, signing in)?
2. What phone + Android version is this (or at least “Android 14/15/16” etc.)?

Once you paste the AndroidRuntime / fatal signal section, I’ll tell you exactly what component is failing (Java vs native vs WebView vs permission) and the specific fix/workaround.