John Haupenthal

what is not working?

It would be great to be able to opt-out of having an error thrown if the response contains an error so we could handle the data returned outside of a...

Try renaming your Babel config from `.babelrc` to `babel.config.js`

```javascript interface ClusterProps { clusterColor: string; clusterFontFamily?: string; clusterTextColor: string; geometry: { coordinates: [number, number]; // [lat, lng] type: 'Point'; }; id: number; onPress: () => void; // Default function...

@malikKartik > Also, Don't forget to add import 'react-native-reanimated'; at the top of your application's entry point JS file(index.js). This solved it for me. I knew this was required for...

@arbaz-yousuf-jazsoft @rajeshivn or anyone still trying to implement the solution above: Add this to the top of your functional component: ```javascript const onViewableItemsChanged = ({ viewableItems, }) => { //...

Try restarting your metro bundler with `yarn start --reset-cache`

For anyone still having this issue, I switched to the Accordion from the [React-Native-Collapsible](https://github.com/oblador/react-native-collapsible) library. There was minimal code change from the code I had written with this library and...

As a way to avoid seeing the warning message in the app and in any error tracking services, you can swalllow it this way: ``` export const registerApptentive = async...

In my `app.json`, `expo-build-properties` keeps giving me a warning in VSCode: `Plugin not found: expo-build-properties(PLUGIN_NOT_FOUND)` I've installed it with `npm i` and `expo`, neither helps. App builds fine in sim...