The splash image name issue (by which the CLI would always save the splash as
/splash/resin-logo.png whereas balenaOS v2.53.0 and later expects
/splash/balena-logo.png) was fixed in balena CLI version 12.14.13.
But reading the first message in this thread and this command:
balena preload ./device.img --app APP_NAME --commit current --splash-image ./logo.png
I wonder if there is another issue. I have found that if the
balena preload command is executed multiple times on same image file for the same commit, it prints the message
"Nothing new to preload" (which is correct) but also it does not update the splash image. In my testing, this only happens when that message is printed:
$ balena preload balena-cloud-test-rpi-raspberrypi3-2.53.9+rev1-v11.9.9.img -a test-rpi --commit current -s new_logo.png
Building Docker preloader image. [========================] 100%
Nothing new to preload. (BalenaError)
The workaround (especially in an automated scenario) would be to always preload a “fresh” (never before preloaded) OS image file. Then there will always be something to preload, and the splash image will be updated.
I have created a CLI issue requesting that the splash image be updated even if there is “Nothing new to preload”: https://github.com/balena-io/balena-cli/issues/2008