These are chat archives for SudoPlz/react-native-bugsnag

8th
Jul 2016
Ioannis Kokkinidis
@SudoPlz
Jul 08 2016 18:02
@kattrali Any news on the source-maps brother? Its the one thing that judges wether people will use bugsnag or not. Everything else is great at the moment! (No pressure of course, just curious)
Delisa Mason
@kattrali
Jul 08 2016 18:13
Hello! I was actually just drafting an update.
Ioannis Kokkinidis
@SudoPlz
Jul 08 2016 18:13
AWEEEESOME!
Delisa Mason
@kattrali
Jul 08 2016 18:14
Haha
Ioannis Kokkinidis
@SudoPlz
Jul 08 2016 18:14
I'm excited!
Delisa Mason
@kattrali
Jul 08 2016 18:14
Might not be that exciting, initially :)
We are currently only processing sourcemaps for projects with an app type of "js"
Ioannis Kokkinidis
@SudoPlz
Jul 08 2016 18:14
aaah I see
Delisa Mason
@kattrali
Jul 08 2016 18:14
so you can change your app type to get sourcemap processing
Ioannis Kokkinidis
@SudoPlz
Jul 08 2016 18:14
so I have to turn the project to JS instead of Other
Delisa Mason
@kattrali
Jul 08 2016 18:14
yep!
Ioannis Kokkinidis
@SudoPlz
Jul 08 2016 18:14
cool
so will there by a react-native or hybrid type in the near future?
Delisa Mason
@kattrali
Jul 08 2016 18:15
though we don't yet support processing multiple types of stacktraces in a single error and/or project type
there will!
I've put a proposal into the roadmap to better support hybrid applications and react native as a first class app type
Ioannis Kokkinidis
@SudoPlz
Jul 08 2016 18:15
awesome
Delisa Mason
@kattrali
Jul 08 2016 18:15
its been really awesome though that you've gotten so far already
Ioannis Kokkinidis
@SudoPlz
Jul 08 2016 18:15
we can use all the existing tools for it to take less time
Delisa Mason
@kattrali
Jul 08 2016 18:16
sweet
Ioannis Kokkinidis
@SudoPlz
Jul 08 2016 18:16
you can arrange for us to use a specific key in the metadata
so that the server knows what to work on
no fancy operations
no more code
for the sdks i mean
only backend processing
if that makes it easier for you guys
Delisa Mason
@kattrali
Jul 08 2016 18:16
well, I think the longer-term fix will be to support multiple stacktraces per error
Ioannis Kokkinidis
@SudoPlz
Jul 08 2016 18:17
ah yeah sure
Delisa Mason
@kattrali
Jul 08 2016 18:17
which leads into my next step, which will be to update the notifier API: https://github.com/bugsnag/bugsnag-notifier-api
Ioannis Kokkinidis
@SudoPlz
Jul 08 2016 18:17
aha yep
Delisa Mason
@kattrali
Jul 08 2016 18:17
replace stacktrace with an object like { type: "js", frames: [(array of stack frames)] }
and name the key stacktraces, for example
so we could have many per error
it may not be the fastest fix, but probably better for everyone so there are less magic keys
I'll be out of town for most of next week, but may have an update after that. Let me know if you have more questions!
Ioannis Kokkinidis
@SudoPlz
Jul 08 2016 19:31
sounds good
@kattrali Ok so I will try to implement sourcemaps as it is right now making my project JS, does this work well at the moment?
Delisa Mason
@kattrali
Jul 08 2016 20:52
It works well for regular JS projects, we're in uncharted territory now but it might help shake out any issues.