bintray / gradle-bintray-plugin

Apache License 2.0
1.28k stars 197 forks source link

Publish failing with 400 error but no debugging information #335

Open samtstern opened 4 years ago

samtstern commented 4 years ago

Plugin Version: 1.8.4 and 1.8.5

I am trying to publish a new version of my library and all my builds fail like this:

* What went wrong:
Execution failed for task ':library:bintrayUpload'.
> Could not upload to 'https://api.bintray.com/content/firebase/geofire/geofire-android/3.1.0/com/firebase/geofire-android/3.1.0/geofire-android-3.1.0.aar': HTTP/1.1 400 Bad Request [message:Error occurred while uploading]

It's not the aar itself. If I remove that from the publication then the failure is the javadocJar, if I remove that then the sourcesJar and if I remove that then the pom.

Is there any way I can find out what is wrong with my request? There's nothing in --debug

samtstern commented 4 years ago

Note that this repo was previously able to publish and even if I revert to the last published commit and run publish again (with a bumped version number) it fails with this error. This implies it's a backend change/bug or somehow an error with my account.

samtstern commented 4 years ago

I can reproduce this with curl so it may not be related to the plugin.

The file I want to upload

$ ls -al common/build/outputs/aar/common-release.aar
-rw-r--r--  1 samstern  primarygroup    13K Nov 10 12:06 common/build/outputs/aar/common-release.aar
samstern@samstern-macbookpro3 geofire-android

Uploading:

$ curl -i --user $BINTRAY_USER:$BINTRAY_KEY -X PUT -T common/build/outputs/aar/common-release.aar https://api.bintray.com/content/firebase/geofire/geofire-android-common/3.1.0/com/firebase/geofire-android-common/3.1.0/geofire-android-common-3.1.0.aar
HTTP/1.1 100 Continue

HTTP/1.1 400 Bad Request
Server: nginx
Date: Tue, 10 Nov 2020 12:38:52 GMT
Content-Type: application/json
Content-Length: 44
Connection: keep-alive

{"message":"Error occurred while uploading"}
samtstern commented 4 years ago

Can't upload files through the UI either: Screen Shot 2020-11-10 at 5 00 22 PM