4 ms·

I was actually just referring to the JavaScript, as you have supported JS in RN for some time now. Obviously now that ur doing the native combo u also gotta get

I was actually just referring to the JavaScript, as you have supported JS in RN for some time now. Obviously now that ur doing the native combo u also gotta get native source mapping as well. But I would recommend taking what u started to 100% before getting bogged down by native integration. In short an example using Code Push and Travis would go a long way for you guys and could be done in a weekend. Just use the above Code Push Travis Cli tool. I think a lot of developers would see the path toward RN sentry integration way more clearly if they could see that. Even if they are using other deployment and ci providers. JS on its own is also more important. Tools like Crashyltics are already mature and automated for native stack traces. People don't mind mixing two solutions if they know they are using high quality solutions for what they specialize in. I want to use sentry for JS, but i need to know sentry is serious about integration with react native. Up until now it has felt like a shaky afterthought. Now it feels like ur taking it seriously but skipping a step. Make the original JavaScript integration on point and painless.

the_mitsuhiko 10y ago
Native is just one part. Most of the work is going into managing sourcemap generation through all the various release methods which includes code push. Right now that process is just too manual and some of the sourcemaps that come out of react-native require some extra processing. We were holding off from targeting this for a while because it feels like with every release of react-native some stuff in the processing pipeline changes which breaks sourcemap generation.
- faceyspacey 10y ago
  that makes sense. i guess we're all waiting for things to reach the appropriate point of maturity before investing the time. im excited to use sentry when this all comes together.

the_mitsuhiko 10y ago

Native is just one part. Most of the work is going into managing sourcemap generation through all the various release methods which includes code push. Right now that process is just too manual and some of the sourcemaps that come out of react-native require some extra processing. We were holding off from targeting this for a while because it feels like with every release of react-native some stuff in the processing pipeline changes which breaks sourcemap generation.

faceyspacey 10y ago
that makes sense. i guess we're all waiting for things to reach the appropriate point of maturity before investing the time. im excited to use sentry when this all comes together.