Have there been any updates / solutions to this? Our developers don't have 'publish' rights in production - they modify the app and associated app objects in a dev environment; export the app to a qvf, which an admin then imports into the use environment, and then published to the stream. Yes, we are publishing to the correct stream with the same (original published) name. As in @TusharDev_Qlik's post above, we have managed a work around: We delete the updated objects in the published version, and then publish the updated app with the updated objects over the existing app. And YES, we know how to publish to the correct stream, and replace the correct app with the new one.
This workaround is too cumbersome for all but the most essential situations. This error looks like a fundamental issue with the publish/replace process, which is supposed to overwrite the prior versions of objects when an new app is publish/replaced over an existing one.