The game when trying to update closes, it reaches the right point but it closes and when entering exactly the same thing happens. I have an Amazon Fire 7, fire OS/android 7, with the more or less recommended requirements

Error.log :
main: 0x8fa4ce78
loaded media10.rlb
loaded media11.rlb
loaded media12.rlb
loaded media13.rlb
loaded media14.rlb
loaded media15.rlb
loaded demos.rlb
archive returned 3
build date Dec 5 2024 18:04:53
android_os_Build_MODEL: KFMUWI
Initializing job system with 3 threads and 32768 jobs per thread.
Using ETC1 mode.
[Fri Dec 6 09:31:34 2024] Found driver: "OpenGL ES 3 GKGL driver". Type 5, Pref 1, Version 150.0. Load @0x0db97ee1
[Fri Dec 6 09:31:34 2024] Instantiate address: 0x90bb8e1c
[Fri Dec 6 09:31:34 2024] Found driver: "OpenGL ES 2 GKGL driver". Type 5, Pref 0, Version 150.0. Load @0xa7e85d93
[Fri Dec 6 09:31:34 2024] Instantiate address: 0x90b28594
[Fri Dec 6 09:31:34 2024] Found driver: "Android OpenSL Audio driver". Type 1, Pref 1, Version 10.1. Load @0xb5d8f123
[Fri Dec 6 09:31:34 2024] Instantiate address: 0x90fc9404
Using multithreaded rendering.
Using 4 physics worker threads. and g_do_mp = 1
using armv7a.
DoGameMPJobs.

Thanks, we'll look into the problem.

Do you have the most recent Fire OS update?
Also, try removing all plugins if you have any installed.

We tried it on our Fire 7 Tablet (the same model as yours) with no problem.

Well, technically I have it updated to its latest version, I already reinstalled it and nothing, I don't know what exactly the problem is

My fire 7 is the ninth generation, it is the same, right?

And my device OS was updated this November 13, this being version 7.3.3.1

So, the device we have is supposedly identical to yours, it has the same "android_os_Build_MODEL: KFMUWI".

Ray updated it to the latest OS version, then installed the game from the Amazon store, patched it up to date, and had no problems running it.

Unless we can reproduce a problem, it's quite difficult for us to fix it.

Perhaps try completely un-installing the game and then doing a device reboot?

I will also throw out one additional possibility:

- Some devices have errors in their internal flash memory (basically the "device disk"). If you get "unlucky" and the game happens to be allocated to this space, that could introduce a problem. When an OS patch happens, the device would allocate new space to the game, for the update, so it's not infeasible.

Because of this, some degree of "messing around with storage space" might be helpful, like uninstalling a bunch of "large" apps, rebooting, and then re-installing VO. It might cause the game to be allocated to wholly new space, which would give you a chance of avoiding this issue, if it is what is impacting you.

I don't know if it is, but I already tried it too and it's still the same, I don't know why it stops and closes, it only happens with reading the newest update, and it hadn't happened to me before with other patches, since there was already another update in this time and nothing had happened to me, I had only left the game for a whole day and then this happens to me, I have already done everything I would say and even then I don't know why the problem is caused, what could I do? or what could have happened? so that he is in this situation with the game

We released an update 1.8.717.2 that should fix the problem.
Sorry for any inconvenience that this has caused.

This was a locale-specific issue, and it's a good illustration of why thorough bug-reports can be really helpful.

If you're using the game in a particular language, please include that in the report. We need as exact of a reproduction case as possible. If we had realized there was a different locale involved, we might have resolved this last week.

Anyway, thanks for the report and sorry it created a problem for people.