Samuel Brucksch
Samuel Brucksch
Hi, Thanks for the reply, no we do not use the android auto extension (yet). But as you can see in the code above, we do exactly the same as...
I can reproduce this behaviour, when our app is running on AA and currently active on the screen. If I then install a new version of our app, while the...
Ok so I will add some logging for that user if onSurfaceDestroyed and onSurfaceCreated is called correctly, and if not, I will open an issue at Google and if both...
Great, thanks. Will add my findings to that issue then if there are any...
Is this possible from our app too? Then I could add that as well and check if it works for that user. This shouldn't work for the re-installation though, as...
Ok then I'll verify that with more logging. Thanks for your support so far.
Got the logs and it actually looks like "onSurfaceAvailable" is called two times right after another: ``` 06-07 11:32:19.838 10438 7917 7917 D MapRenderer: onPause 06-07 11:32:19.867 10438 7917 7917...
So on a first quick test the user said it worked, did not get another report yet for a longer test where he did more switching between the app. My...
Hi @kmadsen This happens in our production app too and there we do not use Android Auto lib, but pure map box. So this will not fix our issue i...
As additional information... We have 3 custom layers where we draw static data onto the map, like speed limit. The speed limit layer is still updating, so the rendering does...