Acme Printing developed an app for their custom printers. A new developer joined the company to maintain the app. He made an update to the original APK and created a new app signing key for the update. What is the reason the APK will fail to be updated in the Google Play Console?

Google Play requires all updates to an existing app to be signed with the exact same signing key as the original version. This security measure ensures the authenticity of updates and prevents unauthorized modifications or impersonation. If a new signing key is used, Google Play will reject the update, as it cannot verify that the new APK comes from the original developer. Deleting and redeploying is unnecessary and would result in a new app listing. Impersonation flagging is not directly related to the developer's identity but to the signing key. An APK file size of 1.0 GB is extremely large for an app and would likely be rejected for other reasons, but not specifically for a signing key mismatch.