Receiving 401 on public artifacts.....

[renaudcerrato]

All of the sudden (today?), my public artifacts are throwing 401!

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':app'.
> Could not resolve all dependencies for configuration ':app:_debugCompile'.
   > Could not resolve com.github.renaudcerrato.EventBus:eventbus:0a62634c72.
     Required by:
         popsy:app:1.23.1
      > Could not resolve com.github.renaudcerrato.EventBus:eventbus:0a62634c72.
         > Could not get resource 'https://jitpack.io/com/github/renaudcerrato/EventBus/eventbus/0a62634c72/eventbus-0a62634c72.pom'.
            > Could not GET 'https://jitpack.io/com/github/renaudcerrato/EventBus/eventbus/0a62634c72/eventbus-0a62634c72.pom'. Received status code 401 from server: Repo not found or no access token provided
   > Could not resolve com.github.renaudcerrato:ViewPagerIndicator:2.4.1-gradle.
     Required by:
         popsy:app:1.23.1
      > Could not resolve com.github.renaudcerrato:ViewPagerIndicator:2.4.1-gradle.
         > Could not get resource 'https://jitpack.io/com/github/renaudcerrato/ViewPagerIndicator/2.4.1-gradle/ViewPagerIndicator-2.4.1-gradle.pom'.
            > Could not GET 'https://jitpack.io/com/github/renaudcerrato/ViewPagerIndicator/2.4.1-gradle/ViewPagerIndicator-2.4.1-gradle.pom'. Received status code 401 from server: Repo not found or no access token provided
   > Could not resolve com.github.renaudcerrato.DeepLinkDispatch:deeplinkdispatch:1f52af6aa0.
     Required by:
         popsy:app:1.23.1
      > Could not resolve com.github.renaudcerrato.DeepLinkDispatch:deeplinkdispatch:1f52af6aa0.
         > Could not get resource 'https://jitpack.io/com/github/renaudcerrato/DeepLinkDispatch/deeplinkdispatch/1f52af6aa0/deeplinkdispatch-1f52af6aa0.pom'.
            > Could not GET 'https://jitpack.io/com/github/renaudcerrato/DeepLinkDispatch/deeplinkdispatch/1f52af6aa0/deeplinkdispatch-1f52af6aa0.pom'. Received status code 401 from server: Repo not found or no access token provided
   > Could not resolve com.github.renaudcerrato.EventBus:eventbus-annotation:0a62634c72.
     Required by:
         popsy:app:1.23.1 > popsy:domain:1.23.1
      > Could not resolve com.github.renaudcerrato.EventBus:eventbus-annotation:0a62634c72.
         > Could not get resource 'https://jitpack.io/com/github/renaudcerrato/EventBus/eventbus-annotation/0a62634c72/eventbus-annotation-0a62634c72.pom'.
            > Could not GET 'https://jitpack.io/com/github/renaudcerrato/EventBus/eventbus-annotation/0a62634c72/eventbus-annotation-0a62634c72.pom'. Received status code 401 from server: Repo not found or no access token provided

Using gradle 2.14.1

[jitpack-io]

Hi,

Is the EventBus repository public? GitHub is reporting it as private (or nonexisting):
https://github.com/renaudcerrato/EventBus

[renaudcerrato]

It has been deleted at some point, since, as stated in the FAQ, you'll still serve artifacts after the repo is deleted.

[renaudcerrato]

What happens if a tag or repository is deleted on GitHub?

If the project was already built then JitPack will continue serving the existing artifacts. It will not rebuild the project at the new tag. In case you need to redo a release the best option is to create a new version on GitHub.

[renaudcerrato]

FYI @jitpack-io, I pushed again the EventBus repository - we're still experiencing the same error (we updated the commit ID accordingly of course)

[renaudcerrato]

UPDATE: the newly pushed EventBus repository is now working (even if we didn't wanted to push it again). But other artifacts are still throwing a 401:

https://jitpack.io/com/github/renaudcerrato/DeepLinkDispatch/deeplinkdispatch/1f52af6aa0/deeplinkdispatch-1f52af6aa0.pom

I guess the FAQ must be corrected?

[jitpack-io]

Thanks for the detailed information @renaudcerrato !

Looks like there was a bug and we're working on fixing it.
When JitPack detects a private repository it caches this result for 1 hour. That's why the repository was not available after your push.

[jitpack-io]

Update: the bug has now been fixed.
Thank you and sorry for the trouble!

[renaudcerrato]

Thanks! Le jeu. 8 déc. 2016 09:02, JitPack.io <notifications@github.com> a écrit :

…

Update: the bug has now been fixed. Thank you and sorry for the trouble! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#986 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB12xfRbonEWepggARHyPYDq0N70X8i2ks5rGA4OgaJpZM4LENbc> .

[sng-handy]

Hi, seems the ViewPagerIndicator repo is now gone as well?

[renaudcerrato]

Yes, we removed all of them since we were relying on your cache.

…

On Mon, Dec 12, 2016 at 2:24 PM sng-handy ***@***.***> wrote: Hi, seems the ViewPagerIndicator repo is now gone as well? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#986 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB12xWQkB23Fx2g_Z-I6cDEg2C3RWy-aks5rHZ95gaJpZM4LENbc> .

[atilacamurca]

When JitPack detects a private repository it caches this result for 1 hour.

This should be in FAQ. I had the same problem and only find the solution here. My problem is that I had a private repository, then request a package, get No access token message, change to public, but the message was still the same.