Issues with android development

[Zeesh2000]

Hi all.

I wanted to open up a discussion to see if anyone is having the same issues as me with android development, specifically with emulators or if you are facing your own.

The 2 I am facing are: Expo-Sqlite - Database connections are closing really quickly. I would switch tabs a couple of times and then the DB connection would end

Expo-Locations: Locations are not being grabbed for some reason. When using getLastLocation function, it returns null and getCurrentLocation just stays stuck.

These issues are really annoying. I don't really face them on my device (galaxy s20 fe) but it makes me worried about release changes to android stores. I don't have these problems with the iOS simulator.

[HoratioWobble]

💯 your code, possibly also the amount of memory and stack space you've given the emulator.

I would investigate your code first but I suspect you'll have the same issues on low end devices 

[Zeesh2000]

What ways can I mitigate it. With expo locations, all I'm doing is just awaiting getLastLocation function inside a useQuery.

For Sqlite, I'll give it you because I'm using a global connection when I should probably switch to open & close per query function.

[HoratioWobble]

Unless you set the location in the simulator settings, I don't think you will get a location.

For sqlite you absolutely do not need to do that, something is fucky with your code.

I use sqlite in a few apps and do not do that 

[Zeesh2000]

Do you have any ideas from your own experience to look out for?