Eugene
Eugene
the same. this is because they replace your current adapter with their SkeletonAdapter when you call skeleton.show(). and they set your adapter again after you call skeleton.hide()
Please use this decision in the lib if it is possible https://stackoverflow.com/questions/14066038/why-does-an-image-captured-using-camera-intent-gets-rotated-on-some-devices-on-a
Problem with rotated bitmap is faced only without using crop. I'll test it tomorrow and will let you know about the results.
I used code from the stack overflow link, that I've mentioned before, for rotating photo correctly.
@NazarKacharaba in my application I can reproduce it every time. I need to know what can be a reason.
@NazarKacharaba UPD. It happens on different devices. Main step to reproduce - create a very long route (f.e. Los Angeles - New York) and launch guidance.
@NazarKacharaba seems like I've found a real reason for this ANR. Starting `MapDataPrefetcher.fetchData(route: Route)` with a very long route as a parameter causes this problem. How to start a big...
No. Just start navigation immediately. Should I wait until fetching is done?
Thank you. I will try on Monday and let you know the result.
Here is my full request, api key has been replaced with "HERE_IS_MY_API_KEY" [text.txt](https://github.com/heremaps/here-android-sdk-examples/files/4360131/text.txt)