The 'problem' is due to the switch from Amazon's `aws-sdk-android` lib to the `minio-java` from minio. For more information refer Īt io.minio.BucketArgs$Builder.validateBucketName(BucketArgs.java:57)Īt io.minio.BucketArgs$Builder.bucket(BucketArgs.java:72)Īt .s3.S3Impl.checkAuthentication(S3Impl.kt:342)Īt .s3.S3CloudContentRepository$Intercepted.checkAuthenticationAndRetrieveCurrentAccount(S3CloudContentRepository.kt:167)Īt .s3.S3CloudContentRepository$Intercepted.checkAuthenticationAndRetrieveCurrentAccount(S3CloudContentRepository.kt:62)Īt .InterceptingCloudContentRepository.checkAuthenticationAndRetrieveCurrentAccount(InterceptingCloudContentRepository.kt:194)Īt .DispatchingCloudContentRepository.checkAuthenticationAndRetrieveCurrentAccount(DispatchingCloudContentRepository.kt:182)Īt .(ConnectToS3.java:21)Īt .cloud.ConnectToS3UseCase$Launcher$2.call(ConnectToS3UseCase.java:92)Īt io.FlowableFromCallable.subscribeActual(FlowableFromCallable.java:39)Īt io.(Flowable.java:14935)Īt io.(Flowable.java:14882)Īt io.FlowableSubscribeOn$n(FlowableSubscribeOn.java:82)Īt io.$ExecutorWorker$n(ExecutorScheduler.java:288)Īt io.$n(ExecutorScheduler.java:253)Īt .runWorker(ThreadPoolExecutor.java:1167)Īt $n(ThreadPoolExecutor.java:641)

: fooBar : bucket name does not follow Amazon S3 standards. For more information refer Īt io.minio.BucketArgs$Builder.validateBucketName(BucketArgs.java:57)`ĭĚctivityLifecycle onResumeFragments -1% Using 1.6.0 the communicate fail with an `: fooBar` due to `bucket name does not follow Amazon S3 standards. Update to Cryptomator for Android version 1.6.x

Use a vault stored in a bucket with the name `fooBar` in Cryptomator for Android version 1.5.xĢ. I agree to follow this project's ()īucket names that does not follow Amazon S3 standards cannot be used since Cryptomator version 1.6.0ġ. I have searched (htt … ps:///cryptomator/android/issues?q=) for duplicates

Backblaze s3