Open danieldanielecki opened 1 year ago
Might be the case https://github.com/tamotam-com/tamotam-app/commit/78730f57635c5e47224b9339d3443fe31db88c88 fixed the problem along with https://github.com/tamotam-com/tamotam-app/commit/7c1ea75120f3d26121c01d97c46db0ca1812d869#diff-5b67d53caccb8942be5646b7959ad6189d445eaf98b0af1ae38d7d61424991b5R21
It still happens on Android sometimes.
It looks like fixed in https://github.com/tamotam-com/tamotam-app/commit/3fc980dcefbff70386442f4e64cccb0d7558f6b5, more information: https://github.com/software-mansion/react-native-reanimated/issues/5067.
Tested on my old Android device, and it breaks after waiting for about 1 minute to launch load all/most events, then it breaks. Might be because of the Android phone is old, so needs to be debugged. No problems on iOS.
It's crashing on Android
, also on a new one, and sometimes straight after launching the app, but the error is being displayed each time: during relaunching and launching. The error is about some things related to location Encountered an exception while executing exported method getCurrentPositionAsync on module ExpoLocation: Found interface com.google.android.gms.location.FusedLocationProviderClient, but class was expected (declaration of 'com.google.android.gms.location.FusedLocationProviderClient' appears in /data/app/~~wXw/...
) - see screenshot, and it happens every single time regardless if that's a first launch, or another one.
It looks like there are 2 issues with Android: permission related to location and storage. In storage case, it really happens also for newer Android devices: when all events will load, then on relaunching it indeed breaks, which might be a problem related to space on a device.
Location:
Storage: simply crashing the app at some point (when most likely all events load) with a message TamoTam has a bug
, It has a bug. Try to clean cache memory of TamoTam.
, or something like that, but sometimes simply crashing without any message/popup with any message.
The location one is a bit strange, as it has been working completely fine for quite some time.
Both issues are only on Android
, iOS
is completely fine!
It might be due to the high amount of data stored. Needs to be debugged. For Android, it happens more often, even on the first launch, but it might be due to an outdated device.