I developed this react Native mobile application called "ClkApp". I Published my application using expo and I can see the application on my phone.
Now, I want to publish this application on Google play. I completed all the required steps including paid the fee of 25 dollars. One of the step requires that I generate a signed APK. I saw some tutorials how to generate the Signed APK and all of them build the application using android studio and go to Build -> Generate Signed APK. I tried to open my app on Android studio, but I don't see any option under Build menu other than "Analyze APK" and "deploy Module to app engine". there is another option called "make", but that is disabled. Below is the image:
I created a new test application using android studio and I can see the options like generate signed APK, Build etc. for this test application. I don't want to create "ClkApp", my original app", application using android studio because that will take lot of time. Is their any way, I can generate the APK on this existing application and don't have to use android studio at all.
Any help will be greatly appreciated.
Since you have build your app with Expo. You can use Expo to generate apk (standalone app)
After you configure app.json and run expo build:android
Check this for details https://docs.expo.io/versions/v32.0.0/distribution/building-standalone-apps/
Related
Ok I am starting to get into the Flutter programming. I am in the process of implementing Flutter in Android Studio.
My question is when publishing a Kotlin app you have to publish with a .aab file for uploading to Google Play.
My question is that when I get to the publishing aspect of Flutter. Is the publishing straight forward, or do I need to convert anything to the .aab file to upload to the Play Store?
Will Android Studio convert everything needed for it to be .aab file?
You can open the Android module of your Flutter app in Android Studio and then generate a signed bundle like for a native Android app.
Tools -> Flutter -> Open for Editing in Android Studio
Build -> Generate Signed Bundle / APK ...
The docs also describe how to do this manually via command line.
I would highly recommend reading the deployment document
https://docs.flutter.dev/deployment/android
also before publishing you need a generate a signing key, and use that key to sign the app.
also don't forget to change version In pubspec.yaml file
and you can read it more on the link or just youtube "Flutter deployment "
I am a little bit confused about two differents behavior and I would need some help.
I am working on an android application with App Links implemented.
I have configured my project to use a keystore for Released build version.
When I use RUN Application of Release version from Android Studio, my application will be opened as a deeplink (disambiguation dialog open when click on a link).
When I generate a SIGNED APK using the same keystore, my application is opened as an app link (direct to the app without dialog).
I have analyzed the two apps (Build APK & SIGNED APK):
RUN Application : App Link status is in ask mode when application is installed;
Signed APK : App Link status is in always mode when application is installed;
Is anyone could explain me what are the differences between RUN Application and Generate Signed APK which could lead to these two different behavior ?
Thanks
Build APK: this is testing APK you can say.in this, we don't need to use Keystore. And in this build Keys are not restricted as we use in Google maps or Facebook SDK. Not big
Signed APK: This is purely a live build you can say. we use live credentials in this build we normally won't use this build for testing.we generate Signed APK after complete testing normal APK.
BIG DIFFERENCE is that play store only accept the SIGNED APK.
So we generate signed APK normally when we have to submit our app to play store.
I am assuming you created the assetlinks.json using the release keystore.
Actually, in regards to app link, there is no difference between the RUN Application(release build) and the Signed APK.
The verification of the assetlinks.json file is done during the app installation. When you run the application from the android studio, the disambiguation dialog is showing because in the device, you might already have a pre-installed version of your app. So when you run the application, the app is not uninstalled and then installed. It just refreshes the code. So the assetlinks.json verification is not done.
So to test app links while running from android studio, first uninstall the app from the device/emulator, and then try triggering app link. The disambiguation dialog will not be shown.
You don't have to uninstall the app every time you want to run the application. But if you have changed the assetlinks.json file(at server side) or the manifest entry in manifest file, then uninstall the app and then run the application(release build) from android studio. The disambiguation dialog will not be shown.
I have build a full instant app project in Android Studio 3.5. I can easily run my instant app project on emulator in a debug mod and everything is working correctly.
instant app project on emulator:
https://i.imgur.com/98MUn2N.jpg (screenshot)
So I compiled this project and Android Studio create 2 file for me.
Output files:
instant-app.json
instantapp-release.zip
my question: How use from this two files for publish to my users, in fact I need my user open https://www.armandl.com/ and my instant app opened such as my debug mod run on emulator.
You would need to upload your zip file to Release management > Android Instant Apps section.
Check out Distribute your instant experience guide for more details about instant app publishing process.
Note: Before publishing your instant app, you must upload an APK of your installed app (on the App releases page).
I am about to create version 2 of an application that was first written using Ionic framework.
I would like to verify one thing that concerns updating the original app on Google Play Store.
When I create a new project in Android Studio :
I should give the same package name as the original app
I should sign with the same keystore and passwords
Is there anything else I have to take into consideration?
Play Store Ionic to Native App Transition :
1.On google play store publishing ionic app are same process as publishing native app.
2.Develop build and deploy any cross platform app(ex:ionic,cordova) and later easily move to native app.
3.In Android Native App build gradle file , package name(application ID) should be same for different versions of app(in your case ionic). Also signing certificate(keystore) remain same during version change.
Hy I am trying to package the wearable app using Android studio 1.0.1 and I am following the steps given on this link https://developer.android.com/training/wearables/apps/packaging.html and I followed the steps over 3 successfully . but when go for 4th step , that is to click the Build menu on AS and to click the signed apk , but after that I got a selection box , weather to sign the mobile apk or to sign the wear app.
Now this is a point which is confusing for me , Should I go for Mobile app and It is all done and I would be able then to install the app on mobile and it will push the wear app to wearable or should I first signed the wear app and then paste this signed app in the mobile app and then select the sign mobile app , ??? what should I do to make it work
I think that my question is quite clear now. waiting for help
You have to simply create a module of your wear app with the same applicationId. In addition you add to your gradle script file of your mobile app:
dependencies {
//something bla bla
wearApp project(':mywearable')
}
Generete from Android Studio menu your release APK for your mobile app. You'll see actually that two apk are generated, the mobile and the wear apk but it's only a convenience for you. If you check the mobile apk you'll see the wear app inside, so don't worry use always to publish the mobile apk.
You should build and sign your just mobile application. Wearable aplication will be signed automatically and introduced inside mobile .apk
You could check this opening the .Apk generated as a .zip. Wear apk will be in res/raw/ folder.