Newbe Dev Stack

Answer : As long as your application complies with the regulations of AppGallery, there should not be any problem it. https://developer.huawei.com/consumer/en/doc/30202 AppGallery does not have any restriction on the language application developed with, no need to worry about it; flutter, cordova, react.native, xamarin they are fine. Just a point to take care. If you are using SDKs or services those depend on Google Play services, when you have published your application on AppGallery, it will be visible only for Huawei devices supports Google Play Services. In theory, yes it could. Huawei uses an OS called Harmony OS. The Arc compiler in Harmony OS supports all the major programming languages including C/, C++, Java, JavaScript and Kotlin. Flutter compiles Dart code to native device code (Java, and Kotlin for Android and Swift for iOS). Huawei is making an Arc compiler that supposedly makes it easy to turn Android apps to Harmony OS apps. What does this mean for Flutt...

Answer : There are three ways to generate your build as per the buildType . (In your case, it's release but it can be named anything you want.) Go to Gradle Task in right panel of Android Studio and search for assembleRelease or assemble(#your_defined_buildtype) under Module Tasks Go to Build Variant in Left Panel and select the build from drop down Go to project root directory in File Explore and open cmd/terminal and run: Linux: ./gradlew assembleRelease or assemble(#your_defined_buildtype) Windows: gradlew assembleRelease or assemble(#your_defined_buildtype) If you want to do a release build (only), you can use Build > Generate Signed apk . For other build types, only the above three options are available. You can find the generated APK in your module/build directory having the build type name in it. It is possible to take any existing Android Studio gradle project and build/sign it from the command line without editing any files. This makes it very n...

Answer : To help people who might search for answer to this same question, it is important to know what type of projects you are using in Studio. Gradle The default project type when creating new project, and the recommended one in general is Gradle. For a new project called "Foo", the structure under the main folder will be Foo/ settings.gradle Foo/ build.gradle build/ Where the internal "Foo" folder is the main module (this structure allows you to create more modules later on in the same structure without changes). In this setup, the location of the generated APK will be under Foo/Foo/build/apk/... Note that each module can generate its own output, so the true output is more Foo/*/build/apk/... EDIT On the newest version of the Android Studio location path for generated output is Foo/*/build/outputs/apk/... IntelliJ If you are a user of IntelliJ before switching to Studio, and are importing your IntelliJ projec...

Answer : try this 1) Change the extension of your .apk to .zip 2) Open and remove the folder META-INF 3) Change the extension to .apk 4) Use the jarsigner and zipalign with your new keystore. hope it helps If you are looking for a quick simple solution, you can use Google's apksigner command line tool which is available in revision 24.0.3 and higher. apksigner sign --ks release.jks application.apk You can find more information about apksigner tool, at the developer Android site. https://developer.android.com/studio/command-line/apksigner.html Or, alternatively, you may use an open-source apk-resigner script Open Source apk-resigner script https://github.com/onbiron/apk-resigner All you have to do is, download the script and just type: ./signapk.sh application.apk keystore key-pass alias zip -d my_application.apk META-INF/\* keytool -genkey -v -keystore my-release-key.keystore -alias alias_name -keyalg RSA -keysize 2048 -validity...