Develop Reference

What is this Error:Null error i got when creating signed apk from my debugged apk?

The link to the source code which i used to create debug apk, and try to create signed apk from it https://github.com/ritik2410/Elegant_Calculator
When i was trying to create a signed apk from my previously debugged apk, this 2 errors pop up:
2 errors at once
Error: C:\Users\pc\AppData\Local\Android\Sdk\build-tools\32.0.0\zipalign.exe -f 4 C:\Users\pc\AppData\Local\Temp\android4.apk C:\Users\pc\ApkProjects\app-debug\app-debug.apk
Unable to open 'C:\Users\pc\AppData\Local\Temp\android4.apk' as zip archive
After that i attempt to find the android4.apk in the location , and it is there ,its size is 0 bytes.
The second error right behind it was :
Error: null
This error was vague. I theorized its because the android4.apk was empty, but i wasnt able to find a fix. I was not able to classify which was the problem that caused this bug to happen. Can you suggest an possible fix to this problem?

I have an error when I want to publish apk to the Google Play developer console

I use Android Studio for development. When i finish the code source, I build and sign, but they tell me that your keystore is not correctly created, you have to convert it to pk20 so I use APK Signer to sign my APK. When I upload it to the console they told me this error :
Failed to run aapt dump badging:
W/ResourceType(471346): Bad resource table: header size 0x0 or total size 0x4b52 is not on an integer boundary
ERROR: dump failed because the resource table is invalid/corrup

Try to update your JDK for the latest version. It fixed the issue in my case.

Trying to build Flutter app for distribution. Execution failed for task ':app:appDistributionUploadRelease'

I'm trying to build an apk to upload to Firebase App Distribution.
When I run ./gradlew assembleRelease appDistributionUploadRelease I get this error:
FAILURE: Build failed with an exception.
What went wrong: Execution failed for task ':app:appDistributionUploadRelease'.
Missing app id. Please check that it was passed in and try again
The app ID is specified in [my project]/android/app/build.gradle.
How can I fix this error?
edit: I found that I can just upload the apk file manually to Firebase App Distribution but the warning said that I would need to fix the problem before I could use Codemagic.

I was found the same problem, I found that just add appId
firebaseAppDistribution {
appId="your app id"
releaseNotes="Release notes for full version"
testers="full#testers.com"
}
Read the document
https://firebase.google.com/docs/app-distribution/android/distribute-gradle#step_3_configure_your_distribution_properties

Failed to run aapt dump badging:AndroidManifest.xml is corrupt

I am new to android.
i get this error when i try to upload update of my app to google play.
Failed to run aapt dump badging:W/ResourceType(19538): Bad resource table: header size 0x708b or total size 0x2f2432a is larger than data size 0x1ce1c
ERROR: AndroidManifest.xml is corrupt
i tried ALMOST VERYTHING google fixes.but nothing works.
please help.
It gave me that 'uploading in debuggable mode' thiny too but i managed to fix it.
sorry about my bad english.

I went through the same problem recently (with the very similar error message) and I also had a lot of trouble to solve, but finally I got it like this:
I used the PhoneGap Builder to generate the APK (so I recommend using the same one); Remembering that to test manages the APK with the same blank key (it's the default markup);
After generating, I used Apk-Signer (https://shatter-box.com/knowledgebase/android-apk-signing-tool-apk-signer/) to generate the key (.keystore) - this package serves, too , To sign and align the application; However, for that case I used ONLY to generate the key;
Go back to the Phone Gap, in the Android options, select 'add a key ...', then select your keystore generated in APK-Signer, and activate the rebuild;
Ready! Now just download the APK, go to google play and be happy.

I ran into a similar problem not so long ago it turned out to be an issue with #+id
A similar question has been asked before and got me through my problem, I will link the post as it is very informative.
Android style Resources compile (aapt) failing : Bad resource table: header size 0xc
Hope this helps you, wish you the best of luck.

I'm new to android too, and I had the same problem, and what worked for me was as simple as :
Zipalign the apk file by a tool called "Advanced APK tool" (download it from xda forum)
then reupload apk file to store without any problem detected,
Best of luck!

Try using a latest version of aapt, from your Android SDK directory,
<Android_SDK_directory>/build-tools/<build_tools_version>/aapt

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.