Ionic & Sentry: Error encountered resolving symbol values statically.

Do you want to request a feature or report a bug? Reporting a bug

(If this is a usage question, please do not post it here—post it on forum.sentry.io instead. If this is not a “feature” or a “bug”, or the phrase “How do I…?” applies, then it’s probably a usage question.)

What is the current behavior? Application will not compile with ngc once Sentry is added.

[16:17:08]  ionic-app-script task: "build" 
[16:17:08]  Error: Error encountered resolving symbol values statically. Reference to a non-exported class 
            RavenExceptionHandler. Consider exporting the class (position 85:1 in the original .ts file), resolving 
            symbol AppModule in /home/devbox/code/app/src/app/app.module.ts

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar.

What is the expected behavior? Application will run and then compile for distribution.

Which versions of Raven.js, 3.15.0 and which browser and OS none are affected by this issue? Did this work in previous versions of Raven.js? did not attempt Are you using the CDN (http://ravenjs.com)? no Are you using hosted Sentry yes or on-premises? no If on-premises, which version (e.g. 8.7.0)? N/A

3.15.0 Browser and OS irrelevant. This is a build in ionic-cli for distribution as a native app. The build is happening in Ubuntu Server 16.04.

  "dependencies": {
    "@agm/core": "^1.0.0-beta.0",
    "@angular/common": "4.0.2",
    "@angular/compiler": "4.0.2",
    "@angular/compiler-cli": "4.0.2",
    "@angular/core": "4.0.2",
    "@angular/forms": "4.0.2",
    "@angular/http": "4.0.2",
    "@angular/platform-browser": "4.0.2",
    "@angular/platform-browser-dynamic": "4.0.2",
    "@ionic-native/app-version": "^3.6.1",
    "@ionic-native/core": "^3.6.1",
    "@ionic-native/geolocation": "^3.6.1",
    "@ionic-native/splash-screen": "^3.6.1",
    "@ionic-native/status-bar": "^3.6.1",
    "@ionic/storage": "^2.0.1",
    "ionic-angular": "^3.1.1",
    "ionicons": "^3.0.0",
    "raven-js": "^3.15.0",
    "rxjs": "5.1.1",
    "sw-toolbox": "^3.6.0",
    "zone.js": "^0.8.10"
  },
  "devDependencies": {
    "@ionic/app-scripts": "^1.3.6",
    "typescript": "^2.2.1"
  },

[benvinegar]

Also I had to use Raven.captureException(err); instead of Raven.captureException(err.originalError);

Thanks. I’ll update the docs.

[b264]

I got it to work with

import * as Raven from 'raven-js';

// ...

Raven
  .config('semi-secret stuff')
  .install();

export class RavenErrorHandler implements IonicErrorHandler {
  handleError(err:any) : void {
    Raven.captureException(err);
  }
}

// ...

@NgModule({

// ...

  providers: [
    {provide: ErrorHandler, useClass: RavenErrorHandler},

in app.module.ts