I am converting my angular PWA to APK .
I followed same tutorial as this link:
https://medium.com/#christof.thalmann/convert-angular-project-to-android-apk-in-10-steps-c49e2fddd29.
I am able to create APK without signing its opening correctly .
I created keystore and I signed , after signing and generating new
APK,while installing app is showing App is not installed.
Any
help is highly appreciated
Related
I have developed an app which is ready to launch on play store.I have signed the app as ionic app publishing documents said.When my signed apk was ready i copied the apk to my device and tried installing it but, it says 'You cant install this application'.I dont have any previous apk installed on my device.I have tried opening the signed apk in android studio and tried installing it from their, it worked.I just want a confirmation that should i upload this apk to playstore or do i need to find the bug.
I followed these steps
im developing an app in react native, but i have some problem in deploying to Play Store. I already generating an upload key using keytool as the react native's documentation said, and i got a file named <my-upload-key>.keystore. Im done with editting build.gradle and gradle.properties to configure my upload key.
My problem is what should i choose with these options, should i choose
"Let Google create and manage my app signing key (recommended)"
OR
"Export and upload a key and certificate"??
Once i choosed the "Let Google create and manage my app signing key", then my app successfuly uploaded and published in playstore, but when i download it from play store, my app wont open and only show white blank screen. My app running well when im using generated APK from react native.
If i choose Export and upload a key and certificate, they want the file uploaded as zip file containing the PEM file.
Am i miss a step in uploading the app to Play Console?
i already solve my problems.
The problem is not on my signing key or upload key or generated keystore.
All is fine by choosing letting google to manage our signing key.
But the problem is on the SoLoader in react-native 0.61.4, many people have same issue with me, the issue was the app being force closed when the app uploaded to playstore or shows only white blank screen.
The solution is to add some configuration on android/app/build.gradle
Here is the code to add in build.gradle
configurations.all {
resolutionStrategy {
force "com.facebook.soloader:soloader:0.8.0"
}
}
add this code to the file's root, all is done.
Please follow React-native's official documentation for signing APK & Publishing to Playstore
Just signing with the method described in Official Documentation and Publish to Playstore with "Let Google create and manage my app signing key". when you succesfully publish you will get new signing certificate and credential so next time you can use this new certificate for signing your APK .
If your App was succesfully published but it is not working or getting crashed there must be an error in your App, are you 100% Sure that it was mistake in publishing not in App?
Just follow below steps:
https://medium.com/#klpdjolanta/13-steps-to-deploying-react-native-android-app-to-google-play-store-using-android-studio-c2ec0c434145
and also try to understand below:
https://medium.com/google-developer-experts/exploring-google-play-app-signing-b4d296f4ee9
I have an already published (to Google Play) APK that was built by Expo.
The key was also created by Expo. Until now everything works great.
I tried to build an app-bundle because now it is the recommended way to build apps for Android. It also helps to reduce app size.
I followed this documentation (that is not 100% clear).
I ran expo opt-in-google-play-signing and followed the instructions.
Eventually the certificates in Google Console were created successfully.
In Release Management > App Signing it now says "App signing by Google Play is enabled for this app".
But it looks like those certificates were not successfully uploaded to Expo (I am not sure if this is the problem).
I am building the app-bundle with this command: expo build:android -t app-bundle.
But the problem is when I am trying to upload the app-bundle in the Release Management in the console it says that the app is signed with a wrong upload certificate.
I tried everything that I was able to find in the searches but nothing helped.
I am completely lost. Can someone please instruct me how I can correctly build the app-bundle and successfully upload it to Google Play?
I have made a tutorial to describe the steps you need to follow. What it is important is that you, once you create the certificates in Google Play, use the MD5 as password for your upload key and your store key.
I am trying to upload my app to the playstore but when I upload the APk this error appears, "You uploaded an APK or Android App Bundle file that was signed in debug mode. You must sign your APK or Android App Bundle in launch mode." I am not sure what to put in the com.company.name thing, or if that is the problem or not.
I did the app using Unity and I am not sure if maybe I did a mistake when I was building into the APK. This is the first app that I publish an APP and it is for a school project. Any help on the subject would be great.
In Android, you create something called a KeyStore. Android Studio creates a debug KeyStore by default, and most people don't even think about it. However, if you want to 'Release' your app to the public, you need to 'sign' it with a 'Release KeyStore'. So, Google how to create a Release KeyStore, and do that first. Then, when building your app for release, at least in Android Studio, you would go to Build/Generate Signed Bundle/APK. Then, you would select your Release KeyStore and enter the passwords and alias. This will then sign your app for Release, and you'll be able to upload it to the App Store.
You need to sign your app with a unique key. You can read more about it here - https://developer.android.com/studio/publish/app-signing
Here you can see how to sign your app in Unity: https://answers.unity.com/questions/326812/signing-android-application.html?childToView=600281#answer-600281
i m working on android applications, i want to login in my application with Google+.
that works fine before publishing my application on Google Play Store.
but when i download my application from store google+ login not woking and showing Toast" an internal error occured " i have followed all the steps.created New project on google developer console , given SHA1 key generated from cmd command (located in .android folder in c drive).then why i fail to login with G+ .pls help out me here.
You have to create seperate SHA1 keys for debug and production.
The keystore for debug is located inside the eclipse sdk, while for production can be created using the Eclipse-> Export->Android apk option.
Hope it helps!