Release your build on the Google play store for Internal testing

This year for the very first time I was making a test release on the Google play console. And when I was going through the process of understanding how to do it. It was very confusing to understand how to do it. So much back and forth to understand the app signing key. So here in this article, I am gonna write it in very simple language to help folks like me. Help them make their first release. We will just cover very basic things and not go in very deep about what is best for the app. So as we all know mostly we have separate env for development, testing, and release. You can just have 2 as well one for development and one for release according to your need. Now for diff env, you will have diff build flavors as well. Release flavor will be prod debug and prod release. Debug build variant is for debugging and testing, release is just for releasing. You will not be able to see any logs here. For generating a release build you need a singing key. <h1>How to Sign your app:</h1> Android requires that all APKs be digitally signed with a certificate before they are installed on a device or updated. When releasing using <a href="https://developer.android.com/guide/app-bundle" rel="noopener ugc nofollow" target="_blank">Android App Bundles</a>, you need to sign your app bundle with an upload key before uploading it to the Play Console and Play App Signing takes care of the rest. For apps distributing using APKs on the Play Store or on other stores, you must manually sign your APKs for upload. <a href="https://levelup.gitconnected.com/release-your-build-on-the-google-play-store-for-internal-testing-86c01c4a651f">Read More</a>