How to access Sonatype Nexus Repository Manager after Jira deactivation?

I’m having trouble uploading an Android AAR file to Maven Central. I made an account with GitHub and got a namespace on Central Sonatype. I signed the artifact with GPG in Android Studio.

When I try to publish, I get this error:

Could not GET '...' Received status code 401 from server: Content access is protected by token

It looks like my Sonatype Nexus login info is wrong. Since Sonatype Jira is gone, I can’t make OSSRH credentials anymore. How can I get into Sonatype Nexus now to publish my build? Any ideas would be great. Thanks!

Hey there, I’ve been through this transition too and it can be a bit of a headache. One thing that really helped me was switching to the Gradle Nexus Publish Plugin. It streamlines the whole process and handles a lot of the authentication stuff behind the scenes.

Make sure you’ve got your sonatype.properties file set up correctly with your new token from central.sonatype.com. Also, double-check that your build.gradle is pointing to the right repository URL - it should be something like ‘https://s01.oss.sonatype.org/service/local/staging/deploy/maven2/’.

If you’re still hitting walls, try clearing your Gradle cache and doing a fresh build. Sometimes old credentials get stuck in there and cause issues. Hope this helps you get your AAR published!

In my experience, after Jira was deactivated I found that the key was to move over to the new Sonatype system. Start by signing in at https://central.sonatype.com using your GitHub credentials then create a new user token from your profile page. Replace your old credentials with this token in your configuration file so that your publishing system can use it. It is also important to verify that your groupId matches your approved namespace on Sonatype. Adjusting these settings helped me resolve the authentication issues and publish successfully.

yo, i had the same issue. try checkin ur gradle file, make sure ur using the right repo url. also, double check ur namespace matches what sonatype gave u. if thats not it, maybe try regenerating ur token on central.sonatype.com. that fixed it for me. good luck!