Skip to main content
Version: 4.3.1

Setting custom Activity Markers

Activity markers are events that occur in an application during runtime.
Activity lifecycle events are automatically captured by Finotes.

Developers can set custom activity markers anywhere in the app using setActivityMarker API. These markers will be shown along with the lifecycle events, when an issue is reported.

Activity markers are displayed in their chronological order.
There is no limit to the number of custom markers that can be set by the developer. Only when an issue is raised, these activity markers are sent to the server.

Anywhere in your project :


[Fn setActivityMarkerAt:self marker:@"clicked on payment_package_two"];

Debug level Activity Markers

You can set debug level custom activity markers in the project using [Fn setActivityMarkerForDebugAt]. These markers will be shown along with the activity trail when an issue is reported in the debug builds of the app.

Anywhere in your project :


[Fn setActivityMarkerForDebugAt:self marker:@"logout tapped"]

How activity trail will look like along with reported issue in Finotes dashboard: 


ExtensionDelegate:app loaded                            11:19:24:469    45.79% FREE MEMORY 
Controller:user loaded                                  11:19:24:708    44.39%
Controller:user authenticated                           11:19:27:012    45.19%
Controller:clicked on payment_package_two               11:20:24:235    55.20%

Debug level Activity Markers​

Developers can set custom activity markers that are active only in debug builds of the app. This can be achieved using setActivityMarkerForDebug API.

These markers are not captured in release or production builds.

Any where in the project: 


[Fn setActivityMarkerForDebugAt:self marker:@"logout tapped"]