Fixed
Status Update
Comments
rm...@google.com <rm...@google.com> #2
Thank you for your feedback. Team may reach out for more feedback in reproducing or triaging this issue.
sh...@google.com <sh...@google.com>
sh...@google.com <sh...@google.com> #3
Robert, thanks for reporting the bug. This is an embarrassing bug that we didn't parse the file name correctly. The fix is on the way.
In the meantime, I suggest a workaround to rename the file name to 6P_onCreate.trace (our released product assumed only one dot in the file name).
In the meantime, I suggest a workaround to rename the file name to 6P_onCreate.trace (our released product assumed only one dot in the file name).
Description
Android Studio 3.4 Beta 5
Build #AI-183.5429.30.34.5310756, built on February 14, 2019
JRE: 1.8.0_152-release-1248-b22 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.13.6
Steps to Reproduce:
1. Generate trace file with Debug.startMethodTracing (tried multiple devices)
2. Open Trace file with Android Studio (Drag into Android Studio)
Error Message: Failed to open file: The profiler was unable to open the selected file. Please try opening it again or select a different file.
Same trace file can be opened with Android Device Monitor.
Attached trace file is from example project with Navigation Drawer.