BJ Warshaw

Similarly, can we use `recordCustomExceptionName` to log fatal and/or non-fatal exceptions? It seems to provide an API for passing a custom error name *and* stack, whereas `logException` (for Android only)...

@f111fei perhaps it'd be worth discussing with @jeserodz. They publicly released a fork of the project which is being updated/maintained here: https://www.npmjs.com/package/react-native-unity-view-reinvented https://github.com/f111fei/react-native-unity-view/issues/136#issuecomment-560015301 Maybe they (or someone else) could help...

@a-milburn I do not, that's a question for the owner, @rexraphael.

See https://github.com/f111fei/react-native-unity-view/issues/136 if you're interested in forking this library and making it CocoaPods compatible.

@ziyoshams can confirm this issue. In our case, we had been planning on designing our own custom alert boxes anyway. So we did that and have been avoiding using [Alert](https://facebook.github.io/react-native/docs/0.31/alert)...

Since `0.60` RN has moved to CocoaPods as default for dependency management. It would be best to add a Podspec for this project. @f111fei any plans to do so?

We are successfully using Pods to manage `react-native-unity-view` (we're using a forked version of this library, since it may be unmaintained; see https://github.com/f111fei/react-native-unity-view/issues/141). For anyone interested: 1. Add a Podspec...

One more thing. On our CI, the Podspec wasn't passing validation because the `description` field in `package.json` passed to `summary` attribute in Podspec was an empty string. We fixed by...

@marlon-wiprud can you send your `ios/Podfile`? Your React deps should all be managed there. @ziyoshams is right, that the header search paths of `RNUnityView` will determine whether or not it...

Looking back at this, I think RNUnityView does not explicitly need to have React paths added once it's also managed using CocoaPods along with React Native. So these two lines...