0.5.2 is broken? (iOS)

[TheRohitSharma]

I had to revert to 0.5.1 to get my build using React Native v0.55.4 to work with this module. I kept getting an error regarding Fabric being undefined when I attempted to use Fabric.Answers. Once I reverted to 0.5.1, it built just fine.

Not a big deal for me, but figured I'd give a heads up.

[sibelius]

can you share your error stacktrace?

does this happen on android as well?

cocoapods or react-native link?

[TheRohitSharma]

2018-10-01 10:44:11.068 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Cannot read property 'Answers' of undefined 2018-10-01 10:44:11.090 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Module AppRegistry is not a registered callable module (calling runApplication)

Haven't had time yet to test on Android. Using exact same code and settings that work without a problem using 0.5.1. Xcode version is 9.4.1.

Using react-native link

[jgcmarins]

react-native link react-native-fabric or just react-native link? it is safer to specify which lib you are trying to link sometimes react-native link can duplicate old links, if you are not passing which lib you want to link

[TheRohitSharma]

May not have unlinked before relinking. :/ Trying again.

[jgcmarins]

take a look at your settings.gradle file

[IndianAg0711]

0.5.2 has an issue in iOS where the header paths specified in the SMXXCrashlytics.xcodeproj is not being set correectly. A fix has been merged into master, but a new version of the package has not been released on NPM yet. reverting back to 0.5.1 or using the master branch of this repo in your package.json file should work.

[sibelius]

in which commit?

[IndianAg0711]

@sibelius I'm looking through your commits and can't find anything recent that touched framework search paths directly - it was consistently setting a recursive search path that I had to change for the project to build correctly each time I installed 0.5.2, and when I attempted to use the master branch the search path was set correctly. Sorry I can't provide more info. Will try to dig deeper when I have time.

[sibelius]

maybe releasing another release can fix this?

[IndianAg0711]

possibly 🤞

[TheRohitSharma]

I haven't had a chance to look either, but i did notice that running react-native link react-native-fabric on v0.5.2 just adds to my podfile instead of actually linking as it does <v0.5.2. This also causes issues because afterwards, pod install ends up installing React as well, at which point I have two copies of React which causes errors.

[gedeagas]

Have the same exact problem with @TheRohitSharma

[bdelville]

I reproduce the problem on Android

[diegorribeiro]

0.5.2 has an issue in iOS where the header paths specified in the SMXXCrashlytics.xcodeproj is not being set correectly. A fix has been merged into master, but a new version of the package has not been released on NPM yet. reverting back to 0.5.1 or using the master branch of this repo in your package.json file should work.

0.5.2 Works fine, but change the import to this : import * as FABRIC from 'react-native-fabric'

AND

FABRIC.Answers.logContentView('Home', 'Simple view', 'page-view');

Works.. 0/

---

import FABRIC from 'react-native-fabric' doesn't works for me in latest version (0.5.2)