Connor Mullins

I had the same issue - thanks @flogy !

Problem seems to persist with "@react-native-firebase/analytics": "^6.7.1". My setUserId call is not being displayed in debug view. I know it's firing because I passed an incorrect parameter and got an...

I've upgraded to "lottie-ios": "^3.1.8", "lottie-react-native": "^3.5.0", "react-native": "0.61.4", and am still getting the same issue @spooksmus reported I re-ran `pod install --repo-update` and restarted metro bundler with `npm start...

Follow up to my comment, I had run `npm update lottie-ios lottie-react-native` and was still getting the above issue. The yellow box warnings were resolved after running `npm i --save...

@emilioicai - I know this is actually an NPM thing, but why would running `npm update lottie-react-native` with version `^3.5.0` specified in package.json not work? Shouldn't this at least be...

This seems to be a real problem. This project uses two functions exposed by @expo/config in version 3, `getExpoSDKVersion`, and `AppJSONConfig`. Neither of those functions exist in major version 6...

@pkreissel I'll cheers to you tonight. This bug has been plaguing our android app for months and it's been tough to trace down and resolve. Your fix immediately worked. Thank...

Hopping into this comment thread to say that v10 seems to have a PrivacyInfo.xcprivacy file starting with 10.16.1: https://github.com/mapbox/mapbox-maps-ios/releases/tag/v10.16.1 I'm updating to this build for our app now to see...

No, actually I must be wrong about the root cause. Looking at our MapboxCommon framework, the PrivacyInfo.xcprivacy file is present. The error message specifically states `ITMS-91056: Invalid privacy manifest -...

Thank you!! 🙇