Studio acting strange after adding s3 maven repo

I added an s3 bucket as a maven repo, it works as my dependencies are found and downloaded

However studio (9) starts acting weird after that everytime i go to project properties.
When changing the db, the settings are not saved. and the locales that are configured in my app.properties are no longer displayed. It has a whole bunch of strange side effects, eg settings not being read from app.properties Changes not being reflected in the build.gradle (eg uberjar settings), …

I went up and down my revision tree finding the commit that caused this, this is how i found it. just add the following section under buildscript.repositories in the build.gradle

    maven {
        url "s3://inserturlhere/releases"
        authentication {
            awsIm(AwsImAuthentication)
        }
 }

Note that there are no warnings or errors at all.

Thank you for reporting the issue.
We’ll check it.

Hi @knstvk
did anyone already had a chance to look into this?

I know it seems like a detail, but i constantly have to balance between either studio getting messed up or my CI failing if I commit my gradle.build by accident.

Any workaround that does not include “don’t use s3 as maven repo” is welcome :smiley:

Hi.

Studio fails to resolve the repository with AWS credentials. The issue will be fixed in the upcoming release.

The ticket is resolved but after downloading the latest version of studio the problem is still there.

Hi,

Yes, unfortunately the ticket above is not applicable for your case.
The problem was fixed in STUDIO-6609. Will be available in the next Studio release.

1 Like