An internal test version has been launched as an update of existing playstore application. And tried the link given after application approval.
It is available for download on all devices, except Android 9 devices. I've tried with every internal test emails, but it doesn't work. Also erased playstore caches and turned on developer options, but still have problem.
We have published another app and it is downloadable in all devices. Anybody please help me find a solution and do we have any restrictions on the release of the internal build of an existing playstore application? The issue is only in Android 9 devices.
Related
Noticed this very strange behavior with my android application
Installed app from play store with version name 3.1 App is working
fine.
Due to new correction,I've installed App via USB connection or by
sharing apk files with same version name.
App is working fine with newly added features but
After certain time/days i found that the newly added feature is
gone and I'm using the play store version...
Additional info:
The same issue occurred in android version 11,12,9 followed by the above process.
However, I have no idea why would it is happening and how to prevent this behavior.
visited this below link for the similar issue and found nothing related to my issue.
Why does Android app rolls back to a previous version after device shutdown?
My guessing is your play store has a function that called update automatically which is opend,your apk on Phone is version behind the play store version
Found the solution for this Silly Issue.
from last one month i observed that my release apk which is not in production but has the same version name was auto updated to production version i it is for all the apk user.
I tried to disable the of google play store setting of auto update and after few day is not replaced by the production version.
:)
I seem to be having a problem with limiting the size of my installed Android Application. During development I used Android Studio to deploy my application to my testing device. The app took a total of 2.32 MB in storage when freshly installed.
The problem in size came up when I published my application to the Google Play Store for alpha testing. I uninstalled the same app I had loaded with Android Studio, then downloaded the one I listed on the Google Play Store. The funny thing is that the same app now takes up 4.11 MB in storage.
How did this occur? The testing environment is the same, therefore what additional libraries or information would need to be added to the app causing it to take up the extra 1.79 MB?
TL;DR
App installed on testing device via Android Studio: 2.32 MB in storage
Same app installed on the same testing device through the Google Play Store: 4.11 MB in storage
Why is there such a significant increase in the size of my application? No other variables aside from installation source have changed.
That's because compiling & installing app into one target device and all devices is different.
When you click the run button, you are targeting only single device.
When deploying a signed release apk, you are targeting all screen densities, intel and arm processors. It includes extra files. It makes your apk file bigger.
Check out this existing answer on SO. Android release apk bigger than debug
The answers point out how a debug version only includes resources for the connected devices screen density. For production all images/res are included. Also, you should be able to further reduce size of your apk by using pro guard if you aren't already.
I have been trying to install an app to other's devices both by downloading the APK and Google Play alpha testing. It installs on the handheld just fine, but for some reason it takes anywhere from 2 hours to 2 days to install onto the wearable.
The size of my wear APK is less than 2 MB, and the mobile's Gradle matches the wear Gradle as it should.
These devices are pretty old, I believe they are on Android 4.4. Does this have an effect? Android Wear still works for them. We have tried many combinations of restarting the watch, reinstalling the app, and doing a factory reset.
I appreciate any help.
Figured it out. The watch was queuing the apk because the Google Play version was too high (I was using 9.0.0), I lowered it to 7.5.0 (in the Wear gradle) and now it's installing quickly.
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've found today that my recently published app on the Android Market,
is not showing up on this device Market: Samsung Apollo.
I've already followed this tutorial to make my app accesible to almost all devices configurations
and it still don't show on that device's Market.
What am I doing wrong?
Did you use the copy protection functionality when uploading the apk?
That can be the issue.
What version of Android did you build against? Does that phone run a compatible version?