I’m stuck trying to upload an Android AAR file to Maven Central. I made an account with GitHub and got my namespace on Central Sonatype’s site. I signed my artifact with GPG in Android Studio.
When I try to publish, I get this error:
Could not GET 'https://s01.oss.sonatype.org/service/local/staging/deploy/maven2/io/github/username/repo_name/0.9-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Content access is protected by token
It looks like my Sonatype Nexus login info is wrong. But Sonatype got rid of Jira, so I can’t make OSSRH credentials anymore. How do I log in to Nexus now to publish my stuff? Any ideas?
As someone who’s recently gone through this transition, I can relate to your frustration. The move away from Jira caught many of us off guard. Here’s what worked for me:
Make sure you’ve created an account on the new Sonatype Community Site, which now serves as the central hub for managing OSSRH credentials.
Once your account is set up, generate new credentials specifically for Nexus access to replace your old Jira-based ones.
If you’re using Gradle for your Android project, update your gradle.properties file with the new username, password, and, if necessary, the correct server URL.
Double-check your GPG key configuration, as sometimes authentication issues arise from an incorrect setup rather than Nexus credentials.
If you continue to face issues, contacting Sonatype support helped me sort out some quirks during migration. Stick with it, and you’ll find that publishing becomes much smoother after this transition.
i had this issue too. now all nexus login deets are on the sonatype community site. just signup there, grab your new creds, and update your gradle configs. if it still acts up, drop a note to support. cheers!
Having recently made the switch to the new Sonatype Community Site, I found that generating fresh credentials solved most of my publishing issues. After signing up there, I updated my build scripts to use the new credentials instead of the old Jira-based ones. In my setup using Gradle, modifying the gradle.properties file with the correct username, password, and server URL was essential. I also confirmed that my GPG key was properly configured to avoid any authentication problems. If you continue to experience issues, contacting Sonatype support can provide further assistance.