findhumane
findhumane
The simplest use case is network calls. As far as I understand and experienced, only one network call can run on the main async JS thread, so stuff like pre-fetching,...
Proximate cause and workaround described here: https://github.com/react-native-maps/react-native-maps/issues/4573#issuecomment-1369146465 ```diff diff --git a/ios/AirMaps/AIRMapMarker.m b/ios/AirMaps/AIRMapMarker.m index 65098aa..0d66061 100644 --- a/ios/AirMaps/AIRMapMarker.m +++ b/ios/AirMaps/AIRMapMarker.m @@ -267,7 +267,7 @@ NSInteger const AIR_CALLOUT_OPEN_ZINDEX_BASELINE = 999; _calloutIsOpen =...
I noticed that [the `develop` branch is ahead of `master`](https://github.com/novalabio/react-native-maps-super-cluster/compare/novalabio:react-native-maps-super-cluster:master...develop), and I had been forking off of `master` (to [fix some issues integrating with newer versions of Expo](https://github.com/novalabio/react-native-maps-super-cluster/compare/master...findhumane:react-native-maps-super-cluster:master)). I applied...
Proximate cause and workaround described here: https://github.com/react-native-maps/react-native-maps/issues/4573#issuecomment-1369146465 ```diff diff --git a/ios/AirMaps/AIRMapMarker.m b/ios/AirMaps/AIRMapMarker.m index 65098aa..0d66061 100644 --- a/ios/AirMaps/AIRMapMarker.m +++ b/ios/AirMaps/AIRMapMarker.m @@ -267,7 +267,7 @@ NSInteger const AIR_CALLOUT_OPEN_ZINDEX_BASELINE = 999; _calloutIsOpen =...
I had a similar problem after upgrading `react-native-paper` from v4 to v5 and I have no idea how to debug it. ``` Web node_modules/expo/AppEntry.js â–“â–“â–“â–“â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘ 25.0% ( 84/240) expo:metro:withMetroResolvers Custom...
That worked, thanks!