We have a web app for FireTV. Amazon wrapped this app into an Android APK after deprecating web apps.
Questions:
If I replace this APK file with one I created, does the new file have to be signed?
Does the new APK file I create have to have the same package ID as the one Amazon used when it initially wrapped my web app?
The API wrapper Amazon provided is named app-debug.apk, so it looks like a debug version was used. I’m guessing when I upload my own wrapper, I should use a release version?
Background:
There have been problems with how Amazon wrapped our app. I’m finally getting around to replacing the APK with one I’ve created to wrap our app in a way that addresses these problems.
Thank you for your questions about replacing the auto-generated APK wrapper for your Fire TV web app.
1. Does the new APK have to be signed?
Yes. You must upload a signed APK. You can sign it with your own keystore — Amazon Appstore manages the distribution signature through your developer account. From the documentation: "Even if you lose the keystore youcreated to sign your release builds, it won’t affect your ability to push out updates to your app because yourapp’s signature is associated with your Amazon developer account."
Yes. Your new APK must use the same package name (application ID) as the auto-generated APK currently live in the store. From the documentation: “your package name must remain the same as your previous binary file.”
Yes. Amazon Appstore will reject debug builds. Generate a signed release APK from Android Studio (Build > Generate Signed Bundle/APK > select release build variant).
Since your app was originally auto-generated by Amazon during the web app migration, if you encounter any issues uploading your replacement APK through the Developer Console, please let us know and we can assist further.