TypeScript icon, indicating that this package has built-in type declarations

    2.1.0 • Public • Published

    npm npm GitHub forks GitHub stars


    • tns plugin add @nativescript-community/sentry

    Be sure to run a new build after adding plugins to avoid any issues.


    import * as Sentry from '@nativescript-community/sentry';
            dsn: "__DSN__"

    Reporting NativeScript errors

    The handleUncaughtErrors method ensures all unhandled NativeScript errors will be caught by Sentry in production, using a custom error handler.

    Reporting handled errors

    If you would like to send a handled error to Bugsnag, you can pass any Error object to Sentry notify method:

    import * as Sentry from '@nativescript-community/sentry';
    try {
      // potentially crashy code
    } catch (error) {

    Reporting promise rejections

    To report a promise rejection, use notify() as a part of the catch block:

    import * as Sentry from '@nativescript-community/sentry';
    new Promise(function(resolve, reject) {
      /* potentially failing code */
    .then(function () { /* if the promise is resolved */ })
    .catch(function (error) {

    Sending diagnostic data

    Automatically captured diagnostics

    Bugsnag will automatically capture and attach the following diagnostic data:

    • A full stacktrace
    • Battery state
    • Device model and OS version
    • Thread state for all threads
    • Release stage (production, debug, etc)
    • App running duration in the foreground and/or background
    • A device- and vendor-specific identifier

    Identifying users

    In order to correlate errors with customer reports, or to see a list of users who experienced each error, it is helpful to capture and display user information. Information set on the Bugsnag client is sent with each error report:

    Sentry.setUser({"email": "john.doe@example.com"});

    Logging breadcrumbs

    In order to understand what happened in your application before each crash, it can be helpful to leave short log statements that we call breadcrumbs. The last several breadcrumbs are attached to a crash to help diagnose what events lead to the error.

    Automatically captured breadcrumbs

    By default, Bugsnag captures common events including:

    • Low memory warnings
    • Device rotation (if applicable)
    • Menu presentation
    • Screenshot capture (not the screenshot itself)
    • Undo and redo
    • Table view selection
    • Window visibility changes
    • Non-fatal errors
    • Log messages (off by default, see configuration options)

    Attaching custom breadcrumbs

    To attach additional breadcrumbs, use the leaveBreadcrumb function:

        category: 'ui',
        message: 'load main view',
        level: 'info'


    npm i @nativescript-community/sentry

    DownloadsWeekly Downloads






    Unpacked Size

    159 kB

    Total Files


    Last publish


    • tralves
    • rdlabo
    • bradmartin
    • cvietor
    • farfromrefuge
    • triniwiz
    • eddyverbruggen
    • rigor789
    • nathanaela
    • walkerrunpdx
    • dnr
    • keerl