I am in the final stages of getting my first android app ready to go out to the play store. To test my final signed release build I emailed the APK to my phone and installed as an 'Unknown App'.
Everything looks to be working fine except my GCM push registration process. I don't seem to be getting a response from google when I try register. If I deploy this same build from my IDE to the phone everything works fine, no code changes at all..
Are their any restrictions on GCM registration? Does the app have to be deployed from the Play store for this process to work?
Any guidance would be great!
Related
when we try to update our compiled app over the old app(installed from amazon store) on Kindle, we get this error:
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
We have verified versionCode that increased, the package name is the same. We think we signed with the same key.
Could please anyone help me? I am new to Android though.
I saw this same error message when attempting to test the upgrade process of our application on Kindle devices accessing the Amazon App Store. I was locally building and signing the app and deploying via $ adb. I ensured that the build configuration was the same (i.e. -release) and that the version number had been incremented properly, but I was still receiving the error upon installation until the application was completely uninstalled. Forcing our users to uninstall for the upgrade was not an acceptable delivery mechanism.
Strangely, the issue did not occur when testing the same process on Samsung devices accessing the Google Play store. The source of the issue for me turned out to be the fact that Amazon removes your developer signing from uploaded .apk files and re-signs your built application with a different key store. Once our update got accepted for publishing, we were able to confirm that the upgrade worked as expected without having to uninstall the app.
I'm using apache cord for my application. The problem is this: If I'm building an application with a command Cordova build android (without --release), then everything connects successfully to the server. But if I collect applications for release, I can not connect to the server.
The application was published in Google Play. The assembly was successful. Maybe it's something to do with Google?
What can be the difference between the behavior of debug and relay applications?
cordova 8.0.0;
android-targetSdkVersion 23;
ok request
You almost certainly have a different signing key for your release application, and need to add the signing key for your release application as authorized to your server.
I have created an App on www.hockeyapp.net manually which created an AppID for me. Also, I have integrated the HockeyApp sdk in my Android app and included the AppId i got from the manual creation on the HockeyApp. I have tried uploading the apk to the hockey app in beta mode and downloaded from the page provided for app distribution which worked fine.
Now I want to upload my Android app to the store. I want to know will the app directly send crash reports to HockeyApp as I have included the AppID and sdk in it while creating the .apk or should I first upload it to HockeyApp and then download it from there and then upload to the store?
I am confused on how it works with Store apps. Any help is appreciated.
If you have integrated the HockeyApp SDK and signed the apk, you can now upload it to the store. You will automatically get the crash reports in the HockeyApp crashes section. You just have to integrate the SDK and test it. If it works fine in your test, then it will work fine on store too.
Yesterday I created an Android app using Delphi XE6, built it with Release configuration and targeted App Store, and ran deployment without installing to any device.
I then uploaded the resulted APK to Google Play Store with success, but when the app downloaded and installed on my device (ZTE N986D), it crashed.
THE SAME APK downloaded to the device via http server running on my laptop was fine and working without any error/crash.
I did triple checks everything (debug/release mode, provisioning, deployment files, etc.) with no luck. I also did try on 3 differend Android devices with exactly same result.
For now I believe that this is not a bug on Delphi XE6.
Is an APK getting changed when uploaded to Google Play Store?
Here is link to the app:
https://play.google.com/store/apps/details?id=org.cenadep.pnup.qrkasir
Any help and thought would be appreciated.
1) You need to generate a keystore for sign your APK.
Please follow this link to create a keystore: http://docwiki.embarcadero.com/RADStudio/XE6/en/Creating_a_Keystore_File
2) After, follow this: http://docwiki.embarcadero.com/RADStudio/XE6/en/Deploying_Your_Signed_Android_Application
I was having problems earlier implementing in-app billing for android. I have fixed that issue, but following that is another issue. When I run the application on my phone and another test account phone, I get the error: "This version of the application is not configured for Market billing." I have installed the new version of the app to the Android market as an APK and added the items. When it opens the in-app billing, it shows the name of the item to purchase from the Android market, but gives me the error. When I tried the static example from Google, that worked.
Thanks
To get this to work you need to sign the package with your release key/certificate, upload to the Market and save it (without activating). Then install the release APK to your device to be able to test. The APK you install on the phone has to have the same version and be signed with the same certificate for IAB testing to work. Details here.