Daniel

I'm using version 7.2.0 because I need to support android v19 and above. When I click on the map it shows the current lat and lng coordinates in the display...

I suspected it had something to do with the API key because the reverse geocoding didn't work. Then I came across [this](https://adevintaspain.github.io/Leku/extra/#google-places) website, which I think should be made more...

Damn. Guess he didn't have the time... Did you find a solution in the end?

I'm getting the exact same crash report on Firebase Console on a released app. I'm using dependency `app.rive:rive-android:4.2.0` with startup `androidx.startup:startup-runtime:1.1.1` The user is using an Oppo A57 running Android...

Wow, you have been busy in 2023. I'll give it a try but I unfortunately was not able to replicate this since this was reported by Firebase Crashlytics. I initialise...

I've had the same issue since September 2023 (my comments [here](https://github.com/rive-app/rive-android/issues/269#issuecomment-1725029854)). This is not just limited to Emulators and happens on all Android versions. I'm currently using this library `app.rive:rive-android:8.3.0`....

Hi @umberto-sonnino I am unable to reporduce this crash but I have reports on Crashlytics indicating the same crash as mentioned above. * Devices: Samsung Gallaxy J4 Core Samsung Gallaxy...

I was having a similar problem and @umberto-sonnino suggested I should upgrade the library to v8.3.0. Thats the second to newest version on [Maven Central](https://mvnrepository.com/artifact/app.rive/rive-android). Now I'm getting an `UnsatisfiedLinkError`...