@mfikes I don't think this works out of the box

well changing it in the Chrome Devtools may not, but isn't it better to change the code anyway?

I'm trying Sentry right now - it seems like a bit of a pain to set up @austinbirch

You’re talking about Sentry’s new method for RN integration, right?

well I tried raven-js first, because that seemed simpler

but that doesn't seem to work on RN/iOS anymore?

now I'm using the new rn integration, but messages seem to go through only sporadically

Hmm, that’s not great. I’m using raven-js at the moment (and their iOS-native client too, to catch native exceptions).

I don’t think I’ve done anything too weird to keep it working.

I’ll have a quick look to confirm that.

do you get this as well? Unable to symbolicate stack trace: The stack is null

No, I don’t think I’m seeing that. Pretty unhelpful!

I’ve just checked, and I don’t have anything too weird going on (except for the whole source mapping thing we were talking about the other day). Roughly speaking, all I have is this (cleaned up to remove some app-specific stuff that shouldn’t make a difference):

(def Raven (js/require "raven-js"))
(def RavenRNPlugin (js/require "raven-js/plugins/react-native"))

;; kind of weird Raven plugin setup
(RavenRNPlugin Raven)

(.install (.config Raven sentry-public-dsn #js {:release release-version}))

I’m probably on quite an old version as well (not upgraded in ages), which might explain.

"raven-js": "^3.16.0"

I might not be helping you at all here, sorry!

Raven plugin setup - interesting!

> Unable to symbolicate stack trace: The stack is null I’ve just managed to get this.

heh 🙂

I don’t install the raven setup when I’m developing, I only enable it for release builds.

ah maybe it only fails in figwheel

Perhaps there’s something with the RN dev error handling that doesn’t work well with it?

I should say that it still reported the issue to Sentry though.

yeah it does, it's just a warning

the full blown RN integration seems pretty complicated, with symbol files etc

I'm worried it'll break something in the long run

I'm mostly interested in JS stacktraces

Yeah, that’s pretty reasonable.

I can’t imagine I’ll be upgrading to the newer integration unless I absolutely have to.

yeah don't touch it unless it breaks

Yep!

As I mentioned the other day for release builds I’m using :advanced optimisations, which means I need those hacks around metro-bundler/RN-packager to build working source maps. Once I’ve got that source map though I just upload it to Sentry to the correct release (automated in fastlane), and then it works. The only one remaining thing is that my source maps don’t include the original JS source for some of the RN/node_modules stuff. That’s less important to me, but I imagine fixable. I’d be interested to hear how you get on with the rest of this.

at this point I'd be happy just get any kind of stack traces

release builds just crash on JS errors

Yeah, not fun.

and afaik no easy way to get at the device logs for release builds

Yep.

Oh, I also use this by the way:

https://bugfender.com/

ah ha!

Kind of like centralised logging for native apps.

Much better than no visibility, but it is just string logs (not structured or anything).

that's all I need

is it easy to set up??

Yeah

I might go with that one instead

I don't care about structured logs for now

Cool. I find it covers everything I need logging-wise.

oh no... Cocoapods

> is it easy to set up?? I should have said: as easy as any RN native module is to setup. Every time I add a native module somehow header paths go crazy and I spend ages in Xcode.

yeah

do Bugfender publish a react-native module?

I’m not sure.

react-native link works best in my experience

Yeah, I agree.

ok I'm trying this out right now

I think I was already using some other stuff via cocoapods at the time I included Bugfender.

Well, I’ve got a bunch of stuff included via Cocoapods, and a bunch of stuff included via react-native link/npm.

I'm mortally afraid of Ruby dependencies

burnt too many times

Ha.

Yeah, not fun.

I make an exception for fastlane, which is :heavy_heart_exclamation_mark_ornament:

I think I’d have given up without fastlane.

I try to spend as little time as possible dealing with Xcode (well, for anything but writing native-side code for the app).

you and me both

has anyone upgraded to react native 0.47?

Has anyone successfully used react-native-tableview with cljs? Got it installed an up and working, but can’t get reorder controls to show on my table cells.

Yak-shaved my way into trying to run their example project in JS, but XCode is barfing trying to build it at all, so not sure if I’m in a dead end.

@joshmiller what's the problem you get?

@mengu I can render a tableview just fine — I can give it rows, fill it with data, and swipe left to show the Delete action and everything — but I cannot reorder rows at all. I’ve got canMove set to true, and if I js/alert a row, it says that’s the case, but it never shows the reorder handle on the right side of the row.

did you do a react-native link? maybe it has some icons and stuff that you need to add to your project

Hm, possible. Let me give that a shot.

That did have stuff to link apparently, but still not seeing the reorder handle; let me check and make sure I have everything still set correctly from screwing around with it.

does anybody know where does this fighwheel-bridge.js coming from?

which template?

@mengu Re-natal’s version of it has a link to the original: https://github.com/drapanjanas/re-natal/blob/master/resources/figwheel-bridge.js

thanks @joshmiller

it looks like they also replaced React.createClass with createReactClass

here is how i upgraded an existing project: https://github.com/drapanjanas/re-natal/issues/129 -- for future reference

@austinbirch thanks for the recommendation... bugfender works great

What’s the reason I can’t do (.setItem js/AsyncStorage app-key (str db))?

says AsyncStorage is not an object

I guess AsyncStorage just isn’t in the js namespace.

I copied code from glittershark and got getItem returning a promise… but how do I await promises in cljs?

@chalcidfly the simplest way is just thread as a promise, call (.then promise (fn [v] ...))

What is the result? a string or some kind of object?

https://pastebin.com/K1PJi9qX is giving me some weird results

@chalcidfly what i do is using -> macro

@joshmiller fixed that handle problem?