Styjun

Can a passenger predict that an airline is about to go bankrupt?

Why would an airline put 15 passengers at once on standby?

Smallest PRIME containing the first 11 primes as sub-strings

How do I introduce dark themes?

Calculate the Ultraradical

Why aren't faces sharp in my f/1.8 portraits even though I'm carefully using center-point autofocus?

How to compare integers in TeX?

How to level a picture frame hung on a single nail?

Avoiding dust scattering when you drill

My machine, client installed VPN,

What action is recommended if your accommodation refuses to let you leave without paying additional fees?

Is it possible for a company to grow but its stock price stays the same or decrease?

A word that refers to saying something in an attempt to anger or embarrass someone into doing something that they don’t want to do?

Lost passport and visa, tried to reapply, got rejected twice. What are my next steps?

To what degree did the Supreme Court limit Boris Johnson's ability to prorogue?

Would a horse be sufficient buffer to prevent injury when falling from a great height?

Writing a program that will filter the integer solutions

Is the "spacetime" the same thing as the mathematical 4th dimension?

Beyond Futuristic Technology for an Alien Warship?

Knights and Knaves: What does C say?

How many stack cables would be needed if we want to stack two 3850 switches

Can adverbs modify adjectives?

Duck, duck, gone!

Booting Ubuntu from USB drive on MSI motherboard -- EVERYTHING fails

Exception thrown while executing UI block: Invalid Region

Android (RN): How to set lat/long of MapView before render? Getting region update errorReact Native: Exception thrown while executing UI block: put reactNavSuperviewLink backReact Native Geolocation Not updating in SimulatorReact Native: Exception thrown while executing UI blockReact Native - Acceptable Amount of Memory UsageReact-Native-Maps onRegionChangeComplete Breaks & Returns (0,0) and Obscure Lat/LngDeltasApple maps shows “directions not available” when launched from react-native appCannot get current position without GPS on react-native with navigator.geolocationException thrown while executing UI block: - [ABI27_0_0RCTview updateContentOffsetINeeded]:React Native, current coordinates dont reflect longlat set on Android Studio GPS

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

1

I'm building an app with react-native-maps. In testing, I've got it set up with a button that toggles between two different locations (DC and Concord NH), one of which happens to be my actual current location. I also have a "Find me!" button to go to the current location.

On the Android simulator, when I hit "find me" it jumps to San Fransisco, which I assume is where the simulator location is set. I don't own an actual Android device

On both iOS simulator and on my iPhone, the DC/NH buttons work, and on my iPhone when I've toggled into DC, I see my blue dot. However, on both the iOS simulator and my iPhone, when I hit "find me" I get this error (the coordinates below are when running on the simulator:

Exception thrown while executing UI block:
Invalid Region <center: +37.33233141, -122.03121860, span: +0.04491556, -5.73770224>

The same error happens, sensibly with different coords, on my iPhone.

It appears that Android and iOS are translating the coordinates differently, or something like that. They both read the coords I give for DC and NH the same, and appear to show the same region when I call those locations up.

By the way, I'm using Apple Maps on iOS – not ready to do the whole ejecting code thing to use Google Maps.

Here's the code I use to get the current location and convert it to numbers that React Native can understand correctly:

 calculateRegion(latitude, longitude, accuracy) 
 const oneDegreeOfLongitudeInMeters = 111.32;
 const circumference = 40075 / 360;
 const latitudeDelta = accuracy / oneDegreeOfLongitudeInMeters;
 const longitudeDelta = accuracy * (1 / Math.cos(latitude * circumference));
 const region = latitude, longitude, latitudeDelta, longitudeDelta ;
 this.setState( region );
 

 getLocation = () => 
 navigator.geolocation.getCurrentPosition(position => 
 const lat = position.coords.latitude;
 const long = position.coords.longitude;
 const accuracy = position.coords.accuracy;
 this.calculateRegion(lat, long, accuracy);
 );
 ;

Does anyone have ideas about this?

react-native react-native-maps

share|improve this question

edited Mar 28 at 22:02

Jonathan Tuzman

asked Mar 28 at 19:42

Jonathan TuzmanJonathan Tuzman

1,60011 gold badge1111 silver badges2626 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Instead of doing setState you may set or update region by using "this". Like this.region=region. If the problem continues can you post your code?
  
  – Masuk Helal Anik
  Mar 31 at 10:50
  

  
  
  
  

add a comment
 | 

1

I'm building an app with react-native-maps. In testing, I've got it set up with a button that toggles between two different locations (DC and Concord NH), one of which happens to be my actual current location. I also have a "Find me!" button to go to the current location.

On the Android simulator, when I hit "find me" it jumps to San Fransisco, which I assume is where the simulator location is set. I don't own an actual Android device

On both iOS simulator and on my iPhone, the DC/NH buttons work, and on my iPhone when I've toggled into DC, I see my blue dot. However, on both the iOS simulator and my iPhone, when I hit "find me" I get this error (the coordinates below are when running on the simulator:

Exception thrown while executing UI block:
Invalid Region <center: +37.33233141, -122.03121860, span: +0.04491556, -5.73770224>

The same error happens, sensibly with different coords, on my iPhone.

It appears that Android and iOS are translating the coordinates differently, or something like that. They both read the coords I give for DC and NH the same, and appear to show the same region when I call those locations up.

By the way, I'm using Apple Maps on iOS – not ready to do the whole ejecting code thing to use Google Maps.

Here's the code I use to get the current location and convert it to numbers that React Native can understand correctly:

 calculateRegion(latitude, longitude, accuracy) 
 const oneDegreeOfLongitudeInMeters = 111.32;
 const circumference = 40075 / 360;
 const latitudeDelta = accuracy / oneDegreeOfLongitudeInMeters;
 const longitudeDelta = accuracy * (1 / Math.cos(latitude * circumference));
 const region = latitude, longitude, latitudeDelta, longitudeDelta ;
 this.setState( region );
 

 getLocation = () => 
 navigator.geolocation.getCurrentPosition(position => 
 const lat = position.coords.latitude;
 const long = position.coords.longitude;
 const accuracy = position.coords.accuracy;
 this.calculateRegion(lat, long, accuracy);
 );
 ;

Does anyone have ideas about this?

react-native react-native-maps

share|improve this question

edited Mar 28 at 22:02

Jonathan Tuzman

asked Mar 28 at 19:42

Jonathan TuzmanJonathan Tuzman

1,60011 gold badge1111 silver badges2626 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Instead of doing setState you may set or update region by using "this". Like this.region=region. If the problem continues can you post your code?
  
  – Masuk Helal Anik
  Mar 31 at 10:50
  

  
  
  
  

add a comment
 | 

I'm building an app with react-native-maps. In testing, I've got it set up with a button that toggles between two different locations (DC and Concord NH), one of which happens to be my actual current location. I also have a "Find me!" button to go to the current location.

On the Android simulator, when I hit "find me" it jumps to San Fransisco, which I assume is where the simulator location is set. I don't own an actual Android device

On both iOS simulator and on my iPhone, the DC/NH buttons work, and on my iPhone when I've toggled into DC, I see my blue dot. However, on both the iOS simulator and my iPhone, when I hit "find me" I get this error (the coordinates below are when running on the simulator:

Exception thrown while executing UI block:
Invalid Region <center: +37.33233141, -122.03121860, span: +0.04491556, -5.73770224>

The same error happens, sensibly with different coords, on my iPhone.

It appears that Android and iOS are translating the coordinates differently, or something like that. They both read the coords I give for DC and NH the same, and appear to show the same region when I call those locations up.

By the way, I'm using Apple Maps on iOS – not ready to do the whole ejecting code thing to use Google Maps.

Here's the code I use to get the current location and convert it to numbers that React Native can understand correctly:

 calculateRegion(latitude, longitude, accuracy) 
 const oneDegreeOfLongitudeInMeters = 111.32;
 const circumference = 40075 / 360;
 const latitudeDelta = accuracy / oneDegreeOfLongitudeInMeters;
 const longitudeDelta = accuracy * (1 / Math.cos(latitude * circumference));
 const region = latitude, longitude, latitudeDelta, longitudeDelta ;
 this.setState( region );
 

 getLocation = () => 
 navigator.geolocation.getCurrentPosition(position => 
 const lat = position.coords.latitude;
 const long = position.coords.longitude;
 const accuracy = position.coords.accuracy;
 this.calculateRegion(lat, long, accuracy);
 );
 ;

Does anyone have ideas about this?

react-native react-native-maps

share|improve this question

edited Mar 28 at 22:02

Jonathan Tuzman

asked Mar 28 at 19:42

Jonathan TuzmanJonathan Tuzman

1,60011 gold badge1111 silver badges2626 bronze badges

Exception thrown while executing UI block:
Invalid Region <center: +37.33233141, -122.03121860, span: +0.04491556, -5.73770224>

 calculateRegion(latitude, longitude, accuracy) 
 const oneDegreeOfLongitudeInMeters = 111.32;
 const circumference = 40075 / 360;
 const latitudeDelta = accuracy / oneDegreeOfLongitudeInMeters;
 const longitudeDelta = accuracy * (1 / Math.cos(latitude * circumference));
 const region = latitude, longitude, latitudeDelta, longitudeDelta ;
 this.setState( region );
 

 getLocation = () => 
 navigator.geolocation.getCurrentPosition(position => 
 const lat = position.coords.latitude;
 const long = position.coords.longitude;
 const accuracy = position.coords.accuracy;
 this.calculateRegion(lat, long, accuracy);
 );
 ;

share|improve this question

edited Mar 28 at 22:02

Jonathan Tuzman

asked Mar 28 at 19:42

Jonathan TuzmanJonathan Tuzman

1,60011 gold badge1111 silver badges2626 bronze badges

share|improve this question

edited Mar 28 at 22:02

Jonathan Tuzman

asked Mar 28 at 19:42

Jonathan TuzmanJonathan Tuzman

1,60011 gold badge1111 silver badges2626 bronze badges

asked Mar 28 at 19:42

Jonathan TuzmanJonathan Tuzman

1,60011 gold badge1111 silver badges2626 bronze badges

asked Mar 28 at 19:42

Jonathan TuzmanJonathan Tuzman

1,60011 gold badge1111 silver badges2626 bronze badges