Dan Williams

This is a complete blocker for us and the above mentioned fixes don't work. Issue is identical to original poster. We're using `django-imagekit==4.0.2` and `django-storages[boto3]==1.7.1`

I agree with you - the only counter point would be to keep consistency with `react-native-google-analytics-bridge`?

@ttmarek not a problem! I agree with you.

See https://github.com/chramos/react-native-skeleton-placeholder/issues/65#issuecomment-1311809097 for a potential workaround

`expo-linear-gradient` and `react-native-linear-gradient` have very similar (the same?) APIs, so one potential approach at getting this package to work with expo is to apply a patch to `react-native-skeleton-placeholder` as follows:...

Is there a reason this hasn't been merged?

@akshetpandey does https://github.com/chirag04/react-native-in-app-utils/pull/140 contain the requested changes?

+1

Does this do the job? ``` import { PurchasesError } from 'react-native-purchases'; const isRevenueCatPurchaseError = (error: any): error is PurchasesError => { return error.domain === 'RevenueCat.ErrorCode'; }; ```

For example, change the implementation of `env.bool()` to the following removes the error: ``` def bool(self, var, default: bool = NOTSET): """ :rtype: bool """ return self.get_value(var, cast=bool, default=default) ```...