[en] Breadcrumb Types
[en] Breadcrumbs are logs set by developers that help trace the path a user navigates before running into a crash or a non-fatal issue. Studio users can set custom breadcrumbs through a Call API.
[en] See the table below to learn about the types of breadcrumbs that Mobile Troubleshooting Tools captures by default.
[en] LAUNCH | [en] Events related to an app’s initiation, the splash screen display and the rendering of the necessary objects. |
[en] CONFIGURATION | [en] Configuration download process. |
[en] VIEW | [en] Events such as opening a new screen or accessing different components. |
[en] PROCESS | [en] Interaction with a process created in Studio and its steps. |
[en] CALL_API | [en] Events that allow a Call API execution or initialization. |
[en] INFO | [en] Events that do not fit any of the other categories. |
[en] EXCEPTION | [en] Exceptions to any event that might not be relevant but still provide useful information. [en] Since Crashlytics only captures eight non-fatal issues per session, the exception helps capture any extra data that might be left out. |
[en] CUSTOM | [en] Breadcrumbs created by a developer or Studio user, configured in Studio through a Call API. |