Recursive Header List Causes Builds To Fail #17
Comments
|
Seems like a similar issue to this: |
hamzahayat
added a commit
that referenced
this issue
Apr 23, 2021
* Refactored SDK to be more modular * Removed TaplyticsProvider imports * Removed unused and undocumented native methods * Added _newSessionCallback native method and exported it as part of `setTaplyticsNewSessionListener` method * Changed newSyncObject to take in NSDictionary * Added getVariables and registerVaraiblesChangedListener methods and removed lodash and only added lodash.clonedeep * Add library to gitignore and prettierignore * Added extra line on ignore files * Added push method types and cleaned up the push methods * Removed old index files and added push types to index * Added TaplyticsProvider * Removed console.log and exported TaplyticsProvider from index.ts * Updated TaplyticsProvider to fetch properties on App Start for android * Added useFeatureFlag hook * Export TaplyticsProvider * Added useVariable hook * Added explicit return * Fixed typo in comments * TAP-6064: Added useCodeBlock hook (#17) * Added useCodeBlock hook * Added useRunningExperiments (#18)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like on large projects XCode can throw a build error after adding react-native-taplytics. Here's the error I was getting:
It seems that this setting in Build Settings was the culprit. Removed it and everything built fine + works well. Something with the recursive search that causes the build to fail.
The text was updated successfully, but these errors were encountered: