Crash information is sent again after every startup #169

vtoupet · 2017-07-26T09:10:33Z

Scenario:
A user has a crash with my application. it is successfully reported by Sentry. The crash is fixed on the next application release. On the first application run after the upgrade, the same crash is reported again (while it did not occur again). And worse, the reported software version is the new one. And this occurs at every software upgrade (on both Android and iOS)

I am using:

react-native 0.44.3
react-native_sentry 0.14.5

HazAT · 2017-07-26T09:36:14Z

So you are saying reports are sent twice?
Because I'm not sure why an upgrade to your app should retrigger sending the same report again.
Are you using CodePush?

HazAT · 2017-07-26T09:49:58Z

@vincejah I just fixed an issue that could be related to this.
Can you upgrade to 0.14.3 and see if it still occurs, you sounded like you can reproduce it easily.

vtoupet · 2017-07-26T10:27:59Z

@HazAT it seems to have fixed the issue, but switching from 0.14.5 to 0.14.13 make native crash reporting not working (captureMessage and captureException are ok though)

HazAT · 2017-07-26T10:55:10Z

@vincejah 0.14.14 should address this.
Sorry for the inconvenience and thx for helping, I am currently looking into adding automated end-to-end tests so this does not happen anymore.

vtoupet · 2017-07-26T11:56:59Z

@HazAT triggering a native crash with 0.14.14 prevents the application from exiting and crash report is still not sent

…ad in js" This reverts commit c25812d.

HazAT · 2017-07-26T12:16:12Z

I've reverted the changes, I am working on it want to get tests running first.
I will keep you posted. 0.14.15 reverted the changes.

HazAT · 2017-08-02T11:48:45Z

I've just released 0.15.1 which has tests for this issue. Please upgrade and report if you are still having trouble with this.

vtoupet · 2017-08-18T09:57:40Z

@HazAT
I have upgraded to v0.17.1 and I still get the issue. What I noticed is that at each application boot, it resends the same event (with different event_id though). Does it mean sentry-buffered-events is not properly cleaned after Raven sends an event?

You will see the codepush is installed but it is not used.

Here is my stacktrace:

08-18 11:16:58.923 23247 23280 D io.sentry.android.AndroidSentryClientFactory: Construction of Android Sentry.
08-18 11:16:58.924 23247 23279 I ReactNativeJS: 'react-native-sentry (setDataCallback):', [Function]
08-18 11:16:58.925 23247 23280 D io.sentry.android.AndroidSentryClientFactory: Sentry init with ctx='com.vtoupet.smartmixin.MainApplication@83e06d6' and dsn='Dsn{uri=https://sentry.io/}'
08-18 11:16:58.930 23247 23279 I ReactNativeJS: Running application "SmartMixin" with appParams: {"initialProps":{},"rootTag":1}. __DEV__ === false, development-level warning are OFF, performance optimizations are ON
08-18 11:16:58.974 23247 23280 D io.sentry.android.AndroidSentryClientFactory: Using buffer dir: /data/user/0/com.vtoupet.smartmixin/cache/sentry-buffered-events
08-18 11:16:58.986 23247 23280 I react-native-sentry: startWithDsnString 'https://secret@sentry.io/164894'
08-18 11:16:58.987 23247 23280 I react-native-sentry: captureEvent '{ NativeMap: {"level":"log","category":"console","message":"react-native-sentry (setDataCallback): function (e) {console.log(e);var t=s.store.getState();return e.extra.app=t.app,e.extra.auth=t.auth,e.extra.user=t.user,e.extra.services=t.services,e;}","timestamp":1503047818.921} }'
08-18 11:16:58.991 23247 23279 I ReactNativeJS: [CodePush] Sync already in progress.
08-18 11:16:58.994 23247 23280 I react-native-sentry: captureEvent '{ NativeMap: {"level":"log","category":"console","message":"Running application \"SmartMixin\" with appParams: {\"initialProps\":{},\"rootTag\":1}. __DEV__ === false, development-level warning are OFF, performance optimizations are ON","timestamp":1503047818.93} }'
08-18 11:16:59.004 23247 23280 W unknown:ViewManagerPropertyUpdater: Could not find generated setter for class com.facebook.react.views.text.ReactVirtualTextShadowNode
08-18 11:16:59.024 23247 23280 I react-native-sentry: captureEvent '{ NativeMap: {"level":"log","category":"console","message":"[CodePush] Sync already in progress.","timestamp":1503047818.991} }'
08-18 11:16:59.085 23247 23279 D ReactNativeJS: 'Raven about to send:', { project: '164894',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:   logger: 'javascript',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:   platform: 'javascript',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:   request: {},
08-18 11:16:59.085 23247 23279 D ReactNativeJS:   exception: 
08-18 11:16:59.085 23247 23279 D ReactNativeJS:    { values: 
08-18 11:16:59.085 23247 23279 D ReactNativeJS:       [ { type: 'TypeError',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:           value: 'undefined is not a function (evaluating \'e.props.unknownProp()\')',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:           stacktrace: 
08-18 11:16:59.085 23247 23279 D ReactNativeJS:            { frames: 
08-18 11:16:59.085 23247 23279 D ReactNativeJS:               [ { filename: '[native code]',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   lineno: null,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   colno: null,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   function: '?',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   in_app: true },
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                 { filename: '/data/user/0/com.vtoupet.smartmixin/files/CodePush/fcee790bbc197889231a96be42defc895946cdec2ddb5ca21d9a97df81073a7e/android/index.android.bundle',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   lineno: 338,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   colno: 925,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   function: 'value',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   in_app: true },
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                 { filename: '/data/user/0/com.vtoupet.smartmixin/files/CodePush/fcee790bbc197889231a96be42defc895946cdec2ddb5ca21d9a97df81073a7e/android/index.android.bundle',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   lineno: 338,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   colno: 2413,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   function: 'value',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   in_app: true },
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                 { filename: '/data/user/0/com.vtoupet.smartmixin/files/CodePush/fcee790bbc197889231a96be42defc895946cdec2ddb5ca21d9a97df81073a7e/android/index.android.bundle',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   lineno: 338,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   colno: 953,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   function: '?',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   in_app: true },
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                 { filename: '/data/user/0/com.vtoupet.smartmixin/files/CodePush/fcee790bbc197889231a96be42defc895946cdec2ddb5ca21d9a97df81073a7e/android/index.android.bundle',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   lineno: 338,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   colno: 3012,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   function: 'value',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   in_app: true },
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                 { filename: '/data/user/0/com.vtoupet.smartmixin/files/CodePush/fcee790bbc197889231a96be42defc895946cdec2ddb5ca21d9a97df81073a7e/android/index.android.bundle',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   lineno: 465,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   colno: 921,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   function: 'receiveTouches',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   in_app: true },
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                 { filename: '/data/user/0/com.vtoupet.smartmixin/files/CodePush/fcee790bbc197889231a96be42defc895946cdec2ddb5ca21d9a97df81073a7e/android/index.android.bundle',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   lineno: 465,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   colno: 547,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   function: '_receiveRootNodeIDEvent',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   in_app: true },
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                 { filename: '/data/user/0/com.vtoupet.smartmixin/files/CodePush/fcee790bbc197889231a96be42defc895946cdec2ddb5ca21d9a97df81073a7e/android/index.android.bundle',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   lineno: 402,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   colno: 150,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   function: 'u',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   in_app: true },
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                 { filename: '/data/user/0/com.vtoupet.smartmixin/files/CodePush/fcee790bbc197889231a96be42defc895946cdec2ddb5ca21d9a97df81073a7e/android/index.android.bundle',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   lineno: 402,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   colno: 90,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   function: 'i',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   in_app: true },
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                 { filename: '/data/user/0/com.vtoupet.smartmixin/files/CodePush/fcee790bbc197889231a96be42defc895946cdec2ddb5ca21d9a97df81073a7e/android/index.android.bundle',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   lineno: 506,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   colno: 358,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   function: 'i',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   in_app: true },
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                 { filename: '/data/user/0/com.vtoupet.smartmixin/files/CodePush/fcee790bbc197889231a96be42defc895946cdec2ddb5ca21d9a97df81073a7e/android/index.android.bundle',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   lineno: 518,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   colno: 465,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   function: 'batchedUpdates',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   in_app: true },
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                 { filename: '/data/user/0/com.vtoupet.smartmixin/files/CodePush/fcee790bbc197889231a96be42defc895946cdec2ddb5ca21d9a97df81073a7e/android/index.android.bundle',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   lineno: 507,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   colno: 597,
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   function: 'perform',
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                   in_app: true },
08-18 11:16:59.085 23247 23279 D ReactNativeJS:                 { filename: '/data/user/0/com.vtoupet.smartmixin/files/CodePush/fcee790bbc197889231a96be42defc895946cdec2ddb5ca21d9a97df81073a7e/android/index.android.
08-18 11:16:59.086 23247 23280 I react-native-sentry: captureEvent '{ NativeMap: {"level":"error","event_id":"6cb4ef5265464a1d920e9b363d229595","message":"TypeError: undefined is not a function (evaluating 'e.props.unknownProp()')","category":"sentry","timestamp":1503047819.085} }'
08-18 11:16:59.139 23247 23280 D io.sentry.android.event.helper.AndroidEventBuilderHelper: Proguard UUIDs file not found.
08-18 11:16:59.240 23247 23280 I react-native-sentry: addExtra '__sentry_version' 'codepush:v7'
08-18 11:16:59.241 23247 23279 I ReactNativeJS: [CodePush] Checking for update.
08-18 11:16:59.243 23247 23280 I react-native-sentry: captureEvent '{ NativeMap: {"level":"log","category":"console","message":"[CodePush] Checking for update.","timestamp":1503047819.24} }'
08-18 11:16:59.285 23247 23280 I react-native-sentry: captureEvent '{ NativeMap: {"category":"fetch","type":"http","data":{"status_code":null,"url":"https://codepush.azurewebsites.net/updateCheck?deploymentKey=RLGAz3loD9CxGf0YaU0qBrFZLHCF8f04da60-90f7-443a-99a6-75aa62d73bad&appVersion=0.10.12&packageHash=fcee790bbc197889231a96be42defc895946cdec2ddb5ca21d9a97df81073a7e&isCompanion=&label=v7&clientUniqueId=87a9a7c0fd465e70","method":"GET"},"timestamp":1503047819.28} }'
08-18 11:16:59.337 23247 23303 I cr_LibraryLoader: Expected native library version number "61.0.3163.51", actual native library version number "61.0.3163.51"
08-18 11:17:00.001  1387  1783 V AlarmManager: Triggering alarm #0: 3 when =1907031705 package=androidoperation =*alarm*:android.intent.action.TIME_TICK
08-18 11:17:00.019  1916  1982 I ClockCtrl:  schedule next: 59981
08-18 11:17:00.019  1916  1982 I KeyguardUpdateMonitor: onTimeChanged
08-18 11:17:00.020  1916  1916 I KeyguardIndication: onTimeChanged
08-18 11:17:00.022  1916  1916 I Clock   : onTimeChanged
08-18 11:17:00.036  1916  1916 I DateView: onTimeChanged
08-18 11:17:00.163 23247 23280 I react-native-sentry: captureEvent '{ NativeMap: {"category":"xhr","type":"http","data":{"status_code":200,"url":"https://codepush.azurewebsites.net/updateCheck?deploymentKey=RLGAz3loD9CxGf0YaU0qBrFZLHCF8f04da60-90f7-443a-99a6-75aa62d73bad&appVersion=0.10.12&packageHash=fcee790bbc197889231a96be42defc895946cdec2ddb5ca21d9a97df81073a7e&isCompanion=&label=v7&clientUniqueId=87a9a7c0fd465e70","method":"GET"},"timestamp":1503047820.16} }'
08-18 11:17:00.186 23247 23279 I ReactNativeJS: [CodePush] App is up to date.
08-18 11:17:00.189 23247 23280 I react-native-sentry: captureEvent '{ NativeMap: {"level":"log","category":"console","message":"[CodePush] App is up to date.","timestamp":1503047820.186} }'code cache capacity to 128KB
08-18 11:17:02.808 23247 23279 I ReactNativeJS: DashboardScreen
08-18 11:17:02.810 23247 23280 I react-native-sentry: captureEvent '{ NativeMap: {"level":"log","category":"console","message":"DashboardScreen","timestamp":1503047822.807} }'
08-18 11:17:02.820 23247 23279 I ReactNativeJS: DashboardOutdoorContainer
08-18 11:17:02.825 23247 23280 I react-native-sentry: captureEvent '{ NativeMap: {"level":"log","category":"console","message":"DashboardOutdoorContainer","timestamp":1503047822.819} }'
08-18 11:17:02.825 23247 23247 V BoostFramework: BoostFramework() : mPerf = com.qualcomm.qti.Performance@e777eed
08-18 11:17:02.826 23247 23247 V BoostFramework: BoostFramework() : mPerf = com.qualcomm.qti.Performance@9db7122
08-18 11:17:02.836 23247 23279 I ReactNativeJS: NaModule1CardContainer
08-18 11:17:02.846 23247 23280 I react-native-sentry: captureEvent '{ NativeMap: {"level":"log","category":"console","message":"NaModule1CardContainer","timestamp":1503047822.835} }'
08-18 11:17:02.885 23247 23279 I ReactNativeJS: DashboardIndoorContainer
08-18 11:17:02.891 23247 23279 I ReactNativeJS: NaMainCardContainer
08-18 11:17:02.907 23247 23280 I react-native-sentry: captureEvent '{ NativeMap: {"level":"log","category":"console","message":"DashboardIndoorContainer","timestamp":1503047822.885} }'
08-18 11:17:02.915 23247 23280 I react-native-sentry: captureEvent '{ NativeMap: {"level":"log","category":"console","message":"NaMainCardContainer","timestamp":1503047822.891} }'
08-18 11:17:02.922 23247 23279 I ReactNativeJS: DashboardDropdownContainer
08-18 11:17:02.953 12716 23241 E ctxmgr  : [ProducerActiveIntervalImpl]closeActiveInterval: Error: ongoing, trying to close
08-18 11:17:02.954 23247 23280 I react-native-sentry: captureEvent '{ NativeMap: {"level":"log","category":"console","message":"DashboardDropdownContainer","timestamp":1503047822.922} }'
08-18 11:17:02.979 23247 23279 I ReactNativeJS: StationDropdownButton
08-18 11:17:02.982 23247 23280 I react-native-sentry: captureEvent '{ NativeMap: {"level":"log","category":"console","message":"StationDropdownButton","timestamp":1503047822.979} }'

HazAT · 2017-08-29T12:02:34Z

@vincejah This should be resolved.
Could it be that your code really has this error and it will always be thrown on startup?

vtoupet · 2017-08-29T12:07:05Z

@HazAT my code cannot have this error at startup as one of them is a generated crash that is triggered when clicking on a button.

I'll test with the latest release.

vtoupet · 2017-10-27T08:44:51Z

@HazAT The problem occurs again when switching from 0.21.2 to 0.29.0.

HazAT · 2017-10-27T09:02:34Z

@vincejah can you upgrade to 0.30.0 please.

vtoupet · 2017-10-27T09:08:52Z

@HazAT 0.30.0 is not proposed by npm (latest available build on npm is 0.29.0)

HazAT · 2017-10-27T09:16:31Z

@vincejah please try again

vtoupet · 2017-10-27T09:46:16Z

@HazAT It still occurs on 0.30.0.

dmhood · 2017-11-10T21:00:35Z

I'm encountering this on our Android app as well--several fixed issues are getting re-reported at startup even across different builds. Would love a fix/workaround for this as it's eating a lot of our events!

almostintuitive · 2017-11-30T09:02:22Z

Hi! It seems like we're also affected by this. Unfortunately it makes it really confusing to check if a bug has been fixed or not. This almost renders Sentry useless for us...

HazAT · 2017-11-30T09:07:29Z

Hey, sorry it was so quiet around this issue.
I will take a look at it again today.

HazAT · 2017-11-30T12:15:04Z

Can you guys send me links to your events that got sent twice please?

almostintuitive · 2017-12-01T06:37:32Z

Sure! https://sentry.io/drops-t0/drops-react-native/issues/408265228/ << this was an exception we have thrown manually. It has been removed from the codebase at least 3 days ago - around version 3.11 - but it's still showing up in 3.15. We have disabled codepush in order to verify that this is not coming from there.

almostintuitive · 2017-12-06T15:14:49Z

@HazAT : I can see there's an open PR for this. any ETA for merging it in? we're going live soon (within 24 hours - although soft launching), and it'd be great to get accurate crash reports, otherwise we don't know where we're standing.

HazAT · 2017-12-06T16:44:12Z

@itchingpixels So I am having a hard time reproducing this.
Are you able to test it easily?
If so you can try it by adding this to your package.json

"react-native-sentry": "https://github.com/getsentry/react-native-sentry#bugfix/android-send-event-twice"

and run yarn install / npm install

would love to get feedback

almostintuitive · 2017-12-06T18:48:04Z

sure, happy to, will roll this out tonight

almostintuitive · 2017-12-07T10:12:42Z

will be releasing this in a few hours. will report back later today if we can still reproduce this issue with the latest build! it'll be actually quite easy to verify, we'll have a result in 24 hours, that I'd be 99% confident in.

almostintuitive · 2017-12-07T12:31:43Z

Hi @HazAT:
A release build fails on the CI & locally (so it's not connected to cached dependencies) with the following error:

FAILURE: Build failed with an exception.

What went wrong:
Could not list contents of '/Users/mark/Dev/drops-react-native/node_modules/react-native-sentry/appium/example'. Couldn't follow symbolic link.
Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

this is when using your branch. Do you have any advice?

HazAT · 2017-12-07T12:44:45Z

@itchingpixels Damn it, ok npm is not considering .npmignore when installing directly from a branch.
I will check if I can make a prerelease or something, give me a few minutes.

HazAT · 2017-12-07T12:55:36Z

@itchingpixels
This is a local npm pack of the branch uploaded to my dropbox.
You can add this or download it and upload it somewhere else ...

"react-native-sentry": "https://www.dropbox.com/s/edmziaethn160w9/react-native-sentry-0.31.0.tgz?dl=1"

Please do not use this for a prod release.

almostintuitive · 2017-12-07T13:07:09Z

You mean we should upload it to somewhere we control it before using it in prod?

HazAT · 2017-12-07T13:23:50Z

First this yes,
and I mean you should try it before releasing it.

almostintuitive · 2017-12-08T10:43:26Z

We've rolled it out to our beta country. will report back later when we have a meaningful amount of data! It'll take longer, since our beta country has a substantially smaller userbase.

almostintuitive · 2017-12-08T19:50:54Z

I'm around 90% certain that this has helped. By Monday, we can say with 99.9%.

HazAT · 2017-12-08T20:45:01Z

Ok, that's good news 👍
Let's wait until monday until I make a release

almostintuitive · 2017-12-11T12:01:34Z

I can confirm with 99% confidence that this works - none of the already fixed crashes appear with the latest version we've published!

HazAT · 2017-12-13T08:51:38Z

I've just released version 0.32.0 which includes the fix.
Please check the migration guide in the release section since we have a breaking change in there.

HazAT self-assigned this Jul 26, 2017

HazAT closed this as completed in c25812d Jul 26, 2017

HazAT added a commit that referenced this issue Jul 26, 2017

Revert "Fixes #169 - Add check for native client to not persist paylo…

8fdfbe4

…ad in js" This reverts commit c25812d.

HazAT reopened this Jul 26, 2017

HazAT added a commit that referenced this issue Jul 31, 2017

Fixes #169 - Add check for native client to not persist payload in js

f38defa

HazAT mentioned this issue Aug 2, 2017

Add Appium Device Farm tests #170

Merged

HazAT closed this as completed in #170 Aug 2, 2017

HazAT reopened this Aug 21, 2017

HazAT closed this as completed Aug 29, 2017

vtoupet changed the title ~~Crash information is sent again after application upgrade~~ Crash information is sent again after every startup Oct 27, 2017

HazAT reopened this Nov 3, 2017

HazAT mentioned this issue Dec 4, 2017

fix: Call store event on android when the event has been sent #310

Merged

HazAT closed this as completed in #310 Dec 13, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Crash information is sent again after every startup #169

Crash information is sent again after every startup #169

vtoupet commented Jul 26, 2017

HazAT commented Jul 26, 2017

HazAT commented Jul 26, 2017

vtoupet commented Jul 26, 2017

HazAT commented Jul 26, 2017

vtoupet commented Jul 26, 2017

HazAT commented Jul 26, 2017

HazAT commented Aug 2, 2017 •

edited

vtoupet commented Aug 18, 2017 •

edited by HazAT

HazAT commented Aug 29, 2017

vtoupet commented Aug 29, 2017

vtoupet commented Oct 27, 2017

HazAT commented Oct 27, 2017

vtoupet commented Oct 27, 2017

HazAT commented Oct 27, 2017

vtoupet commented Oct 27, 2017 •

edited

dmhood commented Nov 10, 2017

almostintuitive commented Nov 30, 2017

HazAT commented Nov 30, 2017

HazAT commented Nov 30, 2017

almostintuitive commented Dec 1, 2017

almostintuitive commented Dec 6, 2017

HazAT commented Dec 6, 2017

almostintuitive commented Dec 6, 2017

almostintuitive commented Dec 7, 2017 •

edited

almostintuitive commented Dec 7, 2017

HazAT commented Dec 7, 2017

HazAT commented Dec 7, 2017

almostintuitive commented Dec 7, 2017

HazAT commented Dec 7, 2017

almostintuitive commented Dec 8, 2017

almostintuitive commented Dec 8, 2017

HazAT commented Dec 8, 2017

almostintuitive commented Dec 11, 2017

HazAT commented Dec 13, 2017

Crash information is sent again after every startup #169

Crash information is sent again after every startup #169

Comments

vtoupet commented Jul 26, 2017

HazAT commented Jul 26, 2017

HazAT commented Jul 26, 2017

vtoupet commented Jul 26, 2017

HazAT commented Jul 26, 2017

vtoupet commented Jul 26, 2017

HazAT commented Jul 26, 2017

HazAT commented Aug 2, 2017 • edited

vtoupet commented Aug 18, 2017 • edited by HazAT

HazAT commented Aug 29, 2017

vtoupet commented Aug 29, 2017

vtoupet commented Oct 27, 2017

HazAT commented Oct 27, 2017

vtoupet commented Oct 27, 2017

HazAT commented Oct 27, 2017

vtoupet commented Oct 27, 2017 • edited

dmhood commented Nov 10, 2017

almostintuitive commented Nov 30, 2017

HazAT commented Nov 30, 2017

HazAT commented Nov 30, 2017

almostintuitive commented Dec 1, 2017

almostintuitive commented Dec 6, 2017

HazAT commented Dec 6, 2017

almostintuitive commented Dec 6, 2017

almostintuitive commented Dec 7, 2017 • edited

almostintuitive commented Dec 7, 2017

HazAT commented Dec 7, 2017

HazAT commented Dec 7, 2017

almostintuitive commented Dec 7, 2017

HazAT commented Dec 7, 2017

almostintuitive commented Dec 8, 2017

almostintuitive commented Dec 8, 2017

HazAT commented Dec 8, 2017

almostintuitive commented Dec 11, 2017

HazAT commented Dec 13, 2017

HazAT commented Aug 2, 2017 •

edited

vtoupet commented Aug 18, 2017 •

edited by HazAT

vtoupet commented Oct 27, 2017 •

edited

almostintuitive commented Dec 7, 2017 •

edited