I have put my app on testing and then i moved it directly from testing to production after that i got error while installing the app as can't install *** . So we have put a new build directly to the production and stopped the tracing in testing. But still we are getting the same error as **can't install ** ***
Error screenshot
Related
Can't install play store build in any device. Installation fails with cant install "App name " pop up. Release build is working fine in all devices(I tried sharing the build to friends), testlab run was also success full, no error pre-launch report.
The app was rejected initially as I added all age group but did not provide the test account details(All access in the app is restricted). As I provided it, play store approved it and the app was published. I have tried to upload the apk file instead of .aap.Still, the issue persists. I ran it in the test lab and could find no issues. There are no issues in the pre-launch report.
android:testOnly="false" //in manifest
android.injected.testOnly=false // gradle.properties
I uploaded the signed .aap build to play store. After getting published I could download but as the installation process starts it stops with a pop up Can't install "App name". The log that I got during this process is
Error -504 while installing com.xxxx.xxxx.xxx.xxxx: INSTALL_FAILED_TEST_ONLY: installPackageLI
But it is not a test build, it is a signed release build.I have already added android:testOnly="false" in manifest and android.injected.testOnly=false in gradle.properties. As mentioned in other discussions, it is not device specific as I couldn't install in any device.
The Jenkin PlayStore upload plugin seems not working for me, always get the following weird error. Manually upload the jenkin apk builds works just fine. Any idea or guess why?
The following is the Jenkins output console, and thanks so much in advance.
Archiving artifacts
Authenticating to Google Play API...
- Credential: xxxxxxx
- Application ID: com.xxx.xxx
ERROR: Build step failed with exception
java.lang.NullPointerException
at org.jenkinsci.plugins.googleplayandroidpublisher.Util.getPublisherErrorMessage(Util.java:97)
at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.publishApk(ApkPublisher.java:383)
at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.perform(ApkPublisher.java:198)
at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)
at hudson.model.Build$BuildExecution.post2(Build.java:186)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)
at hudson.model.Run.execute(Run.java:1749)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:421)
Build step 'Upload Android APK to Google Play' marked build as failure
Looking at the source code it appears that a PublisherApiException is being thrown with no error messages.
This is super strange, because looking at the source this list should always be populated.
So I can't see any way this could happen with the current source. You might want to try updating your plugin, or running it in a debugger (or adding print statements) to see what is going on.
I am new to Appium and I am trying to run manual and automated tests on the AWS Device Farm. While I am trying to 'Create a new run', it wants me to upload an apk file.
Create a new run
But, when upload the apk and run the test, it gives me the below error during the 'Setup Suite' phase.
Error:
Package com.google.android.calculator is already installed as a default system app
Error message
Please let me know if you need additional info that I may have missed to resolve the issue. Many thanks in anticipation!
You are seeing this error because you're uploading a system app that is already installed on the device.
There is a work around where you could upload a dummy apk and in your Appium tests specifically target the calculator app.
I am trying to prepare my app for release.
When I run the app from android studio it works fine. But when I upload a beta build to the Play Store or I run adb install android/app/app-release.apk and try to run the app on my phone, it shows the Unfortunately App, has stopped message.
How can I debug this? Is there a way to run the release build on my phone through android studio so that I can view the logs?
I have never tried, but leave your device plugged in to USB. Run adb logcat in the terminal.
There's probably additional settings to filter for your specific application package
My android app works very well in debug mode and when I generate the signed apk. When I applied Proguard I don't get any error. But when I installed the signed apk with proguard the app crash, I don't know what is the error because I only got "Unfortunately, my app has stopped".
Please give me a cable to know how can I detect what happens with my app, thanks