Search Issue Tracker

Fixed in 1.1.0

Votes

0

Found in [Package]

0.2.7

Issue ID

1201365

Regression

No

[Android Logcat] Logcat windows 'Failed to Load' when switching to a build target that isn't Android

Package: Android Logcat

-

When you have the Capture Screen or Internal Log window open from the Android Logcat and switch to a build target that isn't Android, the windows will fail to load.

1. Ensure you have the Android modules installed in Unity. (Unity Hub -> Installs -> [Editor Version] -> Add Modules)
2. Create a new unity project.
3. Install Android Logcat through Package Manager. (Window -> Package Manager)
4. Switch the build target to Android in Build Settings.
5. Open the Android Logcat window. (Window -> Analysis -> Android Logcat)
6. Open the 'Capture Screen' and 'Internal Log' window.
- Note that the 'Capture Screen' window only opens if you have a connected Android device.
7. Switch the build target to something that isn't Android.

Expected Outcome: Windows display appropriate message that the target should be Android, or close.
Actual Outcome: 'Capture Screen' and 'Internal Log' windows fail to load.

Notes:
- Tested on Mac and Windows.
- Previous case of this issue for the Stacktrace Utility window. See Case 1180263.
- The title of these windows do not return after switching back to Android.

Reproducible in package version 1.0.3, 1.0.0, 0.2.7.
Could not find a unity version where 0.1.5 would work.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.