Develop Reference

Android Studio - Signed SDK, task failed 'android:mergeReleaseResources"

As the title says, when I run Build->Generate signed APK (The APK I am going to upload to the google play store) -> Build Type = release, Signature V1 and V2 both checked -> Finish I get the error
org.gradle.api.tasks.TaskExecutionException: Execution failed for task
':android:mergeReleaseResources'
I have googled for quite some time and can't find another person who had the same exact error as me.
I have a correctly generated Keystore, the passwords are correct (I have seen the error the gradle spits out when its an incorrect password, and it's different)
I have the log coppied to a google doc if you want to take a look. I don't understand log language... https://docs.google.com/document/d/10jr5y9bxCPuNsB484k2Gysv4MeMs4pNJK8oBVMuYMLA/edit?usp=sharing
What does this error message mean, and what can I do to fix it?
Thanks in advance

Bitbucket : The requested URL returned error: 402

I changed password on bitbucket, and now Android Studio can't make push error on Event Log:
Push failed: Failed with error: fatal: unable to access 'https://USERNAME#bitbucket.org/USERNAME/REPOSITORY.git/': The requested URL returned error: 402
How to solve it?

This just happened to me and the fix was to remove some users from my repositories.
Bitbucket's free plan comes with unlimited private repos so, deleting your repos may not have any effect. However, you can only add a maximum of 5 users with the free plan.

This server response is due to the fact that you have exceeded the free limit for Bitbucket. You have two options:
Upgrade your Bitbucket server license
Delete some old repos you don't need anymore.

Android: Handle App Link Verification failure at install time

I added app link feature with autoVerify set for my app following link
On testing the app, it worked in the begining. Then after reinstalling the build, not working.
On debugging what I found is the response time for my .well-known/assetlinks.json file is > 1sec.
which gives timeout error on test-url https://digitalassetlinks.googleapis.com/v1/statements:list?source.web.site=https://example.com&relation=delegate_permission/common.handle_all_urls
{
"maxAge": "599.999999353s",
"debugString": "********************* ERRORS *********************\n* Error: deadline_exceeded: Timeout occurred while fetching Web statements from https://example.com./.well-known/assetlinks.json (which is equivalent to 'https://example.com/.well-known/assetlinks.json') using download from the web (ID 1).\n********************* INFO MESSAGES *********************\n* Info: No statements were found that match your query\n"
}
Looks like because of this timeout, verification is failing.
I would like to know whether app/system retry verification at any point later if verification failed on install (may be because of connection issue or temporary website down)?

Unfortunately Android M does not automatically reattempt verification if it fails due to timeout or connectivity issues. As you found in this guide the next attempt will occur on app update or re-install.

How to solve a Secret file bindings issue

I have a problem with one of my jenkins build.
I have configured in my global credentials, a keystore for one of my android build. This keystore is needed for when I have to sign my apk in order to distribute my app on Google Play for example.
So in the job, I have configured a Secret file binding to allow jenkins to copy the keystore file to a temporary location and sets a variable, let's call it SECRET_PATH, to that location. I can then provide gradle with the value of this variable on the command line when invoking the gradle script (in the switches section).
But then the build fails each time :
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':myapp:packageRelease'.
> Failed to read key ******** from store "/home/jenkins/slave/secretFiles/3607aab3-6e27-497a-b198-7d9a3aeb2913/keystore": Keystore was tampered with, or password was incorrect
it is as if the location /home/jenkins/slave/secretFiles/3607aab3-6e27-497a-b198-7d9a3aeb2913/keystore didn't even exist.
In the job configuration, the help tip on the Bindings sections also mentions this :
Warning: if the master or slave node has multiple executors, any other build running concurrently on the same node will be able to read the contents of this file.
It is exactly as if another concurrent build were running and deleted the location where the keystore was. This is really weird.
One more thing, I am using a master/slave topology where everything is dockerized. Not sure the docker itself is involved though. I think it's purely a Jenkins issue but I am giving this information so that you guys have some context.
Have you guys ever experienced this weird behaviour where jenkins seems to be unable to "resolve" the secret file bindings ?
Any help would be really appreciated.
thanks in advance,

Failed to read key ******** from store "/home/jenkins/slave/secretFiles/3607aab3-6e27-497a-b198-7d9a3aeb2913/keystore": Keystore was tampered with, or password was incorrect
it is as if the location /.../keystore didn't even exist.
No, the error message is correct — the file does exist, but most likely the store password or key password you are providing is incorrect.
If the keystore did not exist, you would get an error something like:
File '/.../release.keystore' specified for property 'signingConfig.storeFile' does not exist.
You can double check this by running file $SECRET_PATH/keystore, or ls -l $SECRET_PATH/keystore, or using keytool or something similar.
You don't mention injecting the keystore and key password(s) at all into the job — how are you doing that?
First make sure that building and signing the release version works as expected with Gradle from the command line.
Then you could try doing the same in Jenkins, by passing in the filename and password via the Gradle step (though this isn't a great idea if you're using the Job Config History plugin, for example).
Once that works, you can use the credential binding plugin to inject the file, and to inject the password.

Error deploying artifact: Failed to transfer file Return code is: 401

I am trying to upload my library, ListBuddies, to maven. To do that I am using the gradle-mvn-push github project of #ChrisBanes . I follow all the steps that he mentioned on his repo plus some others that are needed before that repo is used:
I opened a Jira issue and I waited until It got resolved
I have created GPG keys
I configurate ListBuddies's build.gradle files and the gradle.properties
I have created another local gradle.properties at "/Users/jpardogo/.gradle/gradle.properties"
local gradle.properties file (signing keys are only need for release so should not be a problem for the SNAPSHOT):
//These are the username/password that I use for:
//[JIRA](https://issues.sonatype.org)
//and [NEXUS](https://oss.sonatype.org
NEXUS_USERNAME=jpardogo1
NEXUS_PASSWORD=jira-pass
//This is the key ID that I obtain doing "gpg --list-keys" on the terminal
signing.keyId=my-keyid
//This is the paraphrase I set when I first created the key
signing.password=my-paraphrase
//That's the path to my secret key ring
signing.secretKeyRingFile=/Users/jpardogo/.gnupg/secring.gpg
Look like everything is setup properly but when I do:
gradle clean build uploadArchives
At the end I receive code ERROR 401:
:library:uploadArchives
Uploading: com/jpardogo/listbuddies/library/1.0.0-SNAPSHOT/library-1.0.0-20140209.151716- 1.aar to repository remote at https://oss.sonatype.org/content/repositories/snapshots/
Transferring 67K from remote
:library:uploadArchives FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':library:uploadArchives'.
> Could not publish configuration 'archives'
> Error deploying artifact 'com.jpardogo.listbuddies:library:aar': Error deploying artifact: Failed to transfer file: https://oss.sonatype.org/content/repositories/snapshots/com/jpardogo/listbuddies/library/1.0.0-SNAPSHOT/library-1.0.0-20140209.151716-1.aar. Return code is: 401
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED
I have been looking for an answer the whole day of yesterday and today as well but I couldn't solve it. The error 401 reason is good explain in here, but I couldn't solved anything and I also read that It could be due user permissions problem although I register on Jira as the guide says.
I hope you can help me with that and If you need any more information, please let me know. Thanks.
EDIT: I want to update the question with the link to the jira ticket and its comments.

I finally solved it. All the configuration was ok. The problem was on the file gradle.properties. Because I copy paste the structure of the file, a hidden tabulation reminded next to the NEXUS_USERNAME, so the username actually was being sent with the tabulation and I was receiving a authentication error.
Sometimes things are more simple than you think, and you don't see them. The first thing I will do the next time will be to check the format of the files.

I had exactly the same problem, and the reason was: my password (generated) contained a backslash \.
Solution: Backslashes need to be escaped in gradle.properties!
Example:
ossrhPassword=partBeforeBackslash\\\\partAfterBackslash
instead of:
ossrhPassword=partBeforeBackslash\partAfterBackslash

For me the problem was that I was uploading a version that already exists in the rep. The solution was just to change the 'version' in the build.gradle file.