This was just observed when installing the latest artifact APK.
I believe it has to do with when dependencies have changed, between releases.
There should be a mechanism to handle this, but right now this does not work.
In this scenario, the current working solution is to delete the app first, and then reinstall it using the latest APK.