Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing AAR file in 1.4.0 Release #200

Closed
jfreeley opened this issue Jul 9, 2021 · 20 comments
Closed

Missing AAR file in 1.4.0 Release #200

jfreeley opened this issue Jul 9, 2021 · 20 comments

Comments

@jfreeley
Copy link
Contributor

jfreeley commented Jul 9, 2021

Hi,

There seems to be an issue with a missing AAR file again in the 1.4.0 release as happened with the 1.3.0 release #185. I'm guessing it's the same issue.

The firebase-common-android-debug-1.4.0.aar is the missing file in https://repo.maven.apache.org/maven2/dev/gitlive/firebase-common-android-debug/1.4.0/

@Reedyuk resolved the issue last time, so perhaps you could fix the issue again.

Thanks

@nphausg
Copy link

nphausg commented Jul 10, 2021

[``](url)
Screen Shot 2021-07-10 at 16 59 26
Screen Shot 2021-07-10 at 16 59 43

Me too, can you check @Reedyuk

@Reedyuk
Copy link
Collaborator

Reedyuk commented Jul 16, 2021

Thats odd, i have just published 1.4.1, i checked and it appears it's there this time, but i have feeling this issue might crop up again.
Screenshot 2021-07-16 at 11 31 00

@Reedyuk
Copy link
Collaborator

Reedyuk commented Jul 16, 2021

Can you confirm if this is working now? i have just published it so might need to wait atleast one hour from now until it appears.

@kkalisz
Copy link

kkalisz commented Jul 19, 2021

Hi, @Reedyuk I have just found the same issue (but other artifact) on 1.4.1

1.4.0
https://repo.maven.apache.org/maven2/dev/gitlive/firebase-common-android-debug/1.4.0 - aar missing
https://repo.maven.apache.org/maven2/dev/gitlive/firebase-app-android-debug/1.4.0 - aar present

1.4.1
https://repo.maven.apache.org/maven2/dev/gitlive/firebase-common-android-debug/1.4.1 - aar present
https://repo.maven.apache.org/maven2/dev/gitlive/firebase-app-android-debug/1.4.1 - aar missing

For 1.3.1 both artifact are present in artifactory.
I have also check other artifacts for 1.4.1 and 1.4.0 and it looks that aar files are in place

@nphausg
Copy link

nphausg commented Jul 20, 2021

Still the same
Screen Shot 2021-07-20 at 11 18 43

@gbirk
Copy link

gbirk commented Jul 21, 2021

For me as well:

implementation("dev.gitlive:firebase-firestore:1.4.1")

Screen Shot 2021-07-21 at 12 57 45 PM

@gbirk
Copy link

gbirk commented Jul 27, 2021

Do we have any workaround for this problem?

@tiagonuneslx
Copy link
Contributor

Do we have any workaround for this problem?

You could build and publish the project locally

@Nikola-Milovic
Copy link

Nikola-Milovic commented Aug 11, 2021

Any update on this issue? 1.4.1 and have this issue

@tiagonuneslx sorry, I am a bit stupid when it comes to this. I tried publishToMavenLocal have the library and all the .aar files in the local maven repo (on my disk) but I cannot to get it to compile. It's still erroring the same way, added mavenLocal as the repository, tried adding src/libs and some other methods I've found. Could you please provide a short summary on steps needed to get it to work?

@suntrix
Copy link
Contributor

suntrix commented Aug 17, 2021

Any update on this issue? 1.4.1 and have this issue

@tiagonuneslx sorry, I am a bit stupid when it comes to this. I tried publishToMavenLocal have the library and all the .aar files in the local maven repo (on my disk) but I cannot to get it to compile. It's still erroring the same way, added mavenLocal as the repository, tried adding src/libs and some other methods I've found. Could you please provide a short summary on steps needed to get it to work?

Workaround with publishToMavenLocal will work if you change the lib version (e.g. 1.4.1-local), it's because 1.4.1 is already cached in your local Gradle. You can also remove your Gradle cache (usually ~/.gradle/caches/*), but this will make all the dependencies to re-download.

@Reedyuk
Copy link
Collaborator

Reedyuk commented Aug 17, 2021

I have not had time to diagnose the problem its either a problem with the maven publish plugin or with the CI (github actions/sonartype).
When the release is made, it uploads it in two groups to sonartype and when i try to release this it fails complaining one of the groups is not signed(this group contains the missing package/aar file). It seems entirely random too, sometimes its firebase app, sometimes its common.
If anyone has come across this issue before, it would be helpful, i think its a bug with the maven publish plugin but havent had time to diagnose.

@HeyItsMedz
Copy link

Also getting this error with 1.4.1

image

@suntrix
Copy link
Contributor

suntrix commented Aug 28, 2021

I have not had time to diagnose the problem its either a problem with the maven publish plugin or with the CI (github actions/sonartype).
When the release is made, it uploads it in two groups to sonartype and when i try to release this it fails complaining one of the groups is not signed(this group contains the missing package/aar file). It seems entirely random too, sometimes its firebase app, sometimes its common.
If anyone has come across this issue before, it would be helpful, i think its a bug with the maven publish plugin but havent had time to diagnose.

@Reedyuk It looks like an issue with signing. I tested pure maven publish with GitHub packages on my repo fork. Everything's working fine & the multiplatform app that I'm using it with is happy. Here's a diff of what I've changed: master...suntrix:master-internal

@suntrix
Copy link
Contributor

suntrix commented Sep 1, 2021

@Reedyuk

I came across this issue today while publishing to GitHub Maven repo & it was failing with random package variants, so this might be the underlying cause of your issue -> gradle/gradle#11308

I added the suggested setting to gradle.properties in my PR (https://github.com/GitLiveApp/firebase-kotlin-sdk/pull/215/files#diff-3d103fc7c312a3e136f88e81cef592424b8af2464c468116545c4d22d6edcf19).

@Reedyuk
Copy link
Collaborator

Reedyuk commented Sep 7, 2021

@suntrix I have merged in and just a moment ago released 1.4.2, give it an hour and can you confirm it worked or not.
I'm still not 100% sure it was resolved, so let me know.

@Nikola-Milovic
Copy link

@Reedyuk

Unable to build Kotlin project configuration

org.gradle.internal.resolve.ArtifactNotFoundException: Could not find firebase-app-debug.aar (dev.gitlive:firebase-app-android-debug:1.4.2).
Searched in the following locations:
    https://repo.maven.apache.org/maven2/dev/gitlive/firebase-app-android-debug/1.4.2/firebase-app-android-debug-1.4.2.aar
	at org.gradle.internal.resolve.result.DefaultBuildableArtifactResolveResult.notFound(DefaultBuildableArtifactResolveResult.java:28)
	at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.CachingModuleComponentRepository$LocateInCacheRepositoryAccess.resolveArtifactFromCache(CachingModuleComponentRepository.java:345)
	at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.CachingModuleComponentRepository$LocateInCacheRepositoryAccess.resolveArtifact(CachingModuleComponentRepository.java:297)
	at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.ErrorHandlingModuleComponentRepository$ErrorHandlingModuleComponentRepositoryAccess.lambda$resolveArtifact$15(ErrorHandlingModuleComponentRepository.java:181)
	at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.ErrorHandlingModuleComponentRepository$ErrorHandlingModuleComponentRepositoryAccess.tryResolveAndMaybeBlacklist(ErrorHandlingModuleComponentRepository.java:237)
	at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.ErrorHandlingModuleComponentRepository$ErrorHandlingModuleComponentRepositoryAccess.performOperationWithRetries(ErrorHandlingModuleComponentRepository.java:203)
	at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.ErrorHandlingModuleComponentRepository$ErrorHandlingModuleComponentRepositoryAccess.resolveArtifact(ErrorHandlingModuleComponentRepository.java:179)
	at org.gradle.api.internal.artifacts.ivyservice.ivyresolve.RepositoryChainArtifactResolver.resolveArtifact(RepositoryChainArtifactResolver.java:100)
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.artifact.DefaultArtifactSet$LazyArtifactSupplier.calculateValue(DefaultArtifactSet.java:273)
	at org.gradle.api.internal.artifacts.ivyservice.resolveengine.artifact.DefaultArtifactSet$LazyArtifactSupplier.calculateValue(DefaultArtifactSet.java:244)
	at org.gradle.internal.model.CalculatedValueContainer$CalculationState.lambda$attachValue$0(CalculatedValueContainer.java:216)
	at org.gradle.internal.Try.ofFailable(Try.java:39)
	at org.gradle.internal.model.CalculatedValueContainer$CalculationState.attachValue(CalculatedValueContainer.java:211)
	at org.gradle.internal.model.CalculatedValueContainer.finalizeIfNotAlready(CalculatedValueContainer.java:184)
	at org.gradle.internal.model.CalculatedValueContainer.finalizeIfNotAlready(CalculatedValueContainer.java:175)
	at org.gradle.api.internal.artifacts.transform.TransformingAsyncArtifactListener$TransformedArtifact.finalizeValue(TransformingAsyncArtifactListener.java:176)
	at org.gradle.api.internal.artifacts.transform.TransformingAsyncArtifactListener$TransformedArtifact.run(TransformingAsyncArtifactListener.java:125)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$QueueWorker.execute(DefaultBuildOperationExecutor.java:199)
	at org.gradle.internal.operations.DefaultBuildOperationQueue$WorkerRunnable.runOperation(DefaultBuildOperationQueue.java:241)
	at org.gradle.internal.operations.DefaultBuildOperationQueue$WorkerRunnable.doRunBatch(DefaultBuildOperationQueue.java:222)
	at org.gradle.internal.operations.DefaultBuildOperationQueue$WorkerRunnable.lambda$runBatch$0(DefaultBuildOperationQueue.java:212)
	at org.gradle.internal.resources.AbstractResourceLockRegistry.whileDisallowingLockChanges(AbstractResourceLockRegistry.java:70)
	at org.gradle.internal.work.DefaultWorkerLeaseService.whileDisallowingProjectLockChanges(DefaultWorkerLeaseService.java:185)
	at org.gradle.internal.operations.DefaultBuildOperationQueue$WorkerRunnable.lambda$runBatch$1(DefaultBuildOperationQueue.java:212)
	at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:213)
	at org.gradle.internal.operations.DefaultBuildOperationQueue$WorkerRunnable.runBatch(DefaultBuildOperationQueue.java:200)
	at org.gradle.internal.operations.DefaultBuildOperationQueue$WorkerRunnable.run(DefaultBuildOperationQueue.java:172)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
	at java.base/java.lang.Thread.run(Thread.java:834)

@suntrix
Copy link
Contributor

suntrix commented Sep 15, 2021

@Reedyuk confirmed - AARs are still missing :(

I found this https://getstream.io/blog/publishing-libraries-to-mavencentral-2021/

@regentropft
Copy link

same problem occurs with dev.gitlive:firebase-database:1.4.X releases

@michaelbukachi
Copy link

@Reedyuk Any updates on this?

@Reedyuk
Copy link
Collaborator

Reedyuk commented Oct 5, 2021

This issue is now fixed from version 1.4.3 onwards.

@Reedyuk Reedyuk closed this as completed Oct 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests