GB Quad Plus, Mut@nt HD51, AX HD61, 80cm dish and Supreme Dark motor. Sony STR-DN 1060, Sony UHP-H1 Bluray, Odroid N2+ (CoreElec), Monitor Audio Bronze 5.1 speakers
It does not matter what image you are on, so you are correct. However, the swaps are done using the file on your box. If the ABM version check passes, you can update the provider files using the "update provider files" function in ABM.
As the regions have different numbering, this may be the cause of the issue and may need fine tuning. This is why I had asked for your debug log so that I could run with the options you set.
I am presuming you updated the provider files.
EDIT:
There is an old issue where transferring by FTP does not cause the cache version to be overwritten. This is why I always delete providers.cache when manually transferring files across.
EDIT 2:
Can we please not start adding satellites.xml file into this discussion. It is irrelevant to ABM, other than for validating orbital position.
Last edited by abu baniaz; 24-02-23 at 21:28. Reason: cache file, satellites.xml
ABM updates on software update/reflash. This is always allowed because all the files (py, xml, so) are changed in sync.
It is also possible to update provider files via the ABM menu between builds. This is only allowed if the version matches.
If you swap in xml files from a different version manually ABM is most likely going to crash.
We only bump the version when incompatibilities would cause a crash.