check the details mentioned here

Oct 13, 2025 by windailys.com 45 views

Bug Details

The TEST bug was reported on March 10, 2025, at 14:44:32 UTC. The user who reported the bug has an email address of a@a.a and was using the app version 1.1 (1). The device used to report the bug was a Google sdk_gphone64_arm64 with OS level 34.

View Hierarchy

The bug was reported from the com.example.app.apm.network.ui.NetworkLogDetailsFragment screen. To view the interactive view hierarchy of this screen, click on the link provided below.

Check View Hierarchy

Session Profiler

The app was using 60.7% of the available memory (1.17/1.93 GB) and 67.4% of the available storage (3.91/5.8 GB) when the bug was reported. The connectivity was via WiFi, and the battery level was at 100% and unplugged.

To view the changes in the parameters mentioned above during the last 60 seconds before the bug was reported, click on the link provided below.

View Full Session Profiler

User Info

User Attributes

The user attributes are as follows:

key_name -1624818175: key value bla bla bla la

User Steps

The last 10 steps done by the user right before the bug was reported are as follows:

14:41:09 In activity com.example.app.main.MainActivity: fragment com.example.app.apm.network.ui.OkHttpFragment was paused.
14:41:09 In activity com.example.app.main.MainActivity: fragment com.example.app.apm.network.ui.OkHttpFragment was stopped.
14:41:09 In activity com.example.app.main.MainActivity: fragment com.example.app.apm.network.ui.NetworkLogDetailsFragment was attached.
14:41:09 In activity com.example.app.main.MainActivity: fragment com.example.app.apm.network.ui.NetworkLogDetailsFragment was created.
14:41:09 In activity com.example.app.main.MainActivity: fragment com.example.app.apm.network.ui.NetworkLogDetailsFragment was started.
14:41:09 In activity com.example.app.main.MainActivity: fragment com.example.app.apm.network.ui.NetworkLogDetailsFragment was resumed.
14:41:41 Tap in "GET" of type "androidx.appcompat.widget.AppCompatTextView" in "com.example.app.main.MainActivity"
14:41:42 com.example.app.main.MainActivity was paused.
14:41:42 In activity com.example.app.main.MainActivity: fragment com.example.app.apm.network.ui.NetworkLogDetailsFragment was paused.
14:41:43 Tap in "android.widget.LinearLayout" in "com.example.app.main.MainActivity"

To view all the user steps done by the user throughout the session, click on the link provided below.

View All User Steps

Console Log

The last 10 console logs logged right before the bug was reported are as follows:

14:41:59  I/IBG-BR  (11696): Adding  visual user steps attachments to bug
14:41:59  V/IBG-Core(11696): Permission android.permission.DETECT_SCREEN_CAPTURE state is granted
14:41:59  V/IBG-Core(11696): encryptAttachments
14:41:59  D/ACTIVITY_EVENT(11696): com.instabug.bug.view.InstabugThanksActivity started microTime: 3894
14:41:59  D/ACTIVITY_EVENT(11696): com.instabug.bug.view.InstabugThanksActivity resumed microTime: 2506
14:41:59  D/ACTIVITY_EVENT(11696): com.instabug.bug.view.InstabugThanksActivity TotalDuration: 55220
14:41:59  V/studio.transport(11696): Agent handling command (id:48 type:APP_INSPECTION) for pid:11696.
14:41:59  I/ImeTracker(11696): com.example.app:4b009a02: onRequestHide at ORIGIN_CLIENT_HIDE_SOFT_INPUT reason HIDE_SOFT_INPUT_BY_INSETS_API
14:41:59  I/ImeTracker(11696): com.example.app:2fd0f1f9: onHidden
14:41:59  E/OpenGLRenderer(11696): Unable to match the desired swap behavior.

To view all the logged console logs throughout the session, click on the link provided below.

View All Console Log

Images

Looking for More Details?

If you are looking for more details about the bug, here are some suggestions:

Network Log: We are unable to capture your network requests automatically. If you are using HttpUrlConnection or Okhttp requests, check the details mentioned here.
User Events: Start capturing custom User Events to send them along with each report. Find all the details in the docs.
Instabug Log: Start adding Instabug logs to see them right inside each report you receive. Find all the details in the docs.
TEST Bug Report Analysis: Q&A =====================================

Q: What is the TEST bug?

A: The TEST bug is a reported issue that occurred on March 10, 2025, at 14:44:32 UTC. The user who reported the bug has an email address of a@a.a and was using the app version 1.1 (1).

Q: What is the view hierarchy of the bug?

A: The bug was reported from the com.example.app.apm.network.ui.NetworkLogDetailsFragment screen. To view the interactive view hierarchy of this screen, click on the link provided below.

Check View Hierarchy

Q: What is the session profiler of the bug?

A: The app was using 60.7% of the available memory (1.17/1.93 GB) and 67.4% of the available storage (3.91/5.8 GB) when the bug was reported. The connectivity was via WiFi, and the battery level was at 100% and unplugged.

To view the changes in the parameters mentioned above during the last 60 seconds before the bug was reported, click on the link provided below.

View Full Session Profiler

Q: What are the user attributes of the bug?

A: The user attributes are as follows:

key_name -1624818175: key value bla bla bla la

Q: What are the user steps of the bug?

A: The last 10 steps done by the user right before the bug was reported are as follows:

14:41:09 In activity com.example.app.main.MainActivity: fragment com.example.app.apm.network.ui.OkHttpFragment was paused.
14:41:09 In activity com.example.app.main.MainActivity: fragment com.example.app.apm.network.ui.OkHttpFragment was stopped.
14:41:09 In activity com.example.app.main.MainActivity: fragment com.example.app.apm.network.ui.NetworkLogDetailsFragment was attached.
14:41:09 In activity com.example.app.main.MainActivity: fragment com.example.app.apm.network.ui.NetworkLogDetailsFragment was created.
14:41:09 In activity com.example.app.main.MainActivity: fragment com.example.app.apm.network.ui.NetworkLogDetailsFragment was started.
14:41:09 In activity com.example.app.main.MainActivity: fragment com.example.app.apm.network.ui.NetworkLogDetailsFragment was resumed.
14:41:41 Tap in "GET" of type "androidx.appcompat.widget.AppCompatTextView" in "com.example.app.main.MainActivity"
14:41:42 com.example.app.main.MainActivity was paused.
14:41:42 In activity com.example.app.main.MainActivity: fragment com.example.app.apm.network.ui.NetworkLogDetailsFragment was paused.
14:41:43 Tap in "android.widget.LinearLayout" in "com.example.app.main.MainActivity"

Q: What are the console logs of the bug?

A: The last 10 console logs logged right before the bug was reported are as follows:

14:41:59  I/IBG-BR  (11696): Adding  visual user steps attachments to bug
14:41:59  V/IBG-Core(11696): Permission android.permission.DETECT_SCREEN_CAPTURE state is granted
14:41:59  V/IBG-Core(11696): encryptAttachments
14:41:59  D/ACTIVITY_EVENT(11696): com.instabug.bug.view.InstabugThanksActivity started microTime: 3894
14:41:59  D/ACTIVITY_EVENT(11696): com.instabug.bug.view.InstabugThanksActivity resumed microTime: 2506
14:41:59  D/ACTIVITY_EVENT(11696): com.instabug.bug.view.InstabugThanksActivity TotalDuration: 55220
14:41:59  V/studio.transport(11696): Agent handling command (id:48 type:APP_INSPECTION) for pid:11696.
14:41:59  I/ImeTracker(11696): com.example.app:4b009a02: onRequestHide at ORIGIN_CLIENT_HIDE_SOFT_INPUT reason HIDE_SOFT_INPUT_BY_INSETS_API
14:41:59  I/ImeTracker(11696): com.example.app:2fd0f1f9: onHidden
14:41:59  E/OpenGLRenderer(11696): Unable to match the desired swap behavior.

Q: How can I capture more details about the bug?

A: If you are looking for more details about the bug, here are some suggestions:

Network Log: We are unable to capture your network requests automatically. If you are using HttpUrlConnection or Okhttp requests, check the details mentioned here.
User Events: Start capturing custom User Events to send them along with each report. Find all the details in the docs.
Instabug Log: Start adding Instabug logs to see them right inside each report you receive. Find all the details in the docs.