App 2.40.1: an update always reaches the installer screen
The car refuses the installer session, and only a refusal thrown at once opened the installer screen; one that came back through the session's result ended in a toast, so the update downloaded and then nothing seemed to happen. Now any result but success or the driver's cancel opens the installer screen with the verified APK, as does a confirmation that cannot be shown, and a session silent for 20 s is abandoned for it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LhzAVaUyqcw5PkGjz4mWW6
This commit is contained in:
@@ -110,3 +110,10 @@ That screen needs a `file://` URI on the car build: a read grant on our FileProv
|
||||
when it comes from the system user (`not exported from UID 1000`), and the installer reports the
|
||||
unreadable file as "There was a problem parsing the package". On the emulator the session still
|
||||
installs silently.
|
||||
|
||||
The refusal does not always come at once: the platform may also answer a moment later, through
|
||||
the session's result (`OtaInstallResultReceiver`). Since 2.40.1 that answer opens the installer
|
||||
screen too, as does a confirmation the platform asks for but cannot show; only **Cancel** on that
|
||||
screen ends the update there. And if the session says nothing at all for 20 s, the app abandons
|
||||
it and opens the installer screen. Before 2.40.1 a late refusal ended in a short message only:
|
||||
the update downloaded and then nothing seemed to happen.
|
||||
|
||||
Reference in New Issue
Block a user