Cameron Murphy

@reasonman thank you so much for this fix. The line being referenced is now this line https://github.com/maxs15/react-native-modalbox/blob/v2.0.0/index.js#L567 @maxs15 Any chance this fix could be brought in?

+1 here. This is the best alternative to `react-native-drawer` which has been abandoned. Even just a release that renames `componentWillMount` to `UNSAFE_componentWillMount` and `componentWillReceiveProps` to `UNSAFE_componentWillReceiveProps` would be handy so...

I second this. Fantastic work, especially seeing as they've outright said it'll never likely be a core feature.

Could you please also fix ActionException::getErrorMessage()? `$message = "$opType: $path caused $error";` When $error is an array, the message becomes something like 'update: /customer/customer/26210548 caused Array'

@ruflin https://github.com/ruflin/Elastica/pull/1089

Agreed JSON on the command line is clunky. We're exporting stories split into files by grouping. If we export all 400 odd components into the same asketch.json, Sketch likes to...

I see this but only when launching builds via Expo Client from https://exp.host  Local dev and published builds seem to be fine.

The issue seems to be resolved in 0.28.0 🥳

Experiencing this too

Hit this problem too. Why is this issue closed? The docs don't say to pass `{ projectId: Constants.expoConfig.extra.eas.projectId }` to `Notifications.getExpoPushTokenAsync` but that seems like the only workaround right now?