No tags present in clone used for build [113668706]

WAI

Bug

Status Update

No update yet.

Description

ni...@gmail.com

created issue #1

Aug 31, 2018 10:47PM

If I clone the source repo that mirrors my github repo, I can see that all the tags I've created in the github repo are present in the gcloud source repo mirror. But the checkout that's done automatically as a prelude to my cloudbuild.yaml is missing all tags. This prevents

https://github.com/goreleaser/goreleaser from being able to build a changelog based on the commit messages of changesets introduced since the last release/tag.

More details can be found in the PR I created to add instructions for using Goreleaser with cloudbuild:

https://github.com/goreleaser/goreleaser/pull/780

Comments

kn...@google.com <kn...@google.com> Sep 4, 2018 07:14PM

Assigned to kn...@google.com.

kn...@google.com <kn...@google.com> #2Sep 4, 2018 08:55PM

Reassigned to gc...@google.com.

We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.

kn...@google.com <kn...@google.com> #3Sep 4, 2018 10:32PM

Due to the pattern I am noticing when researching the other reports of this bug, I have a feeling this ticket will be closed as "Won't Fix (Obsolete)" when it clearly is not. I can confirm that this issue exists in Android 10, so unless Android 10 is obsolete, and this issue is not reproducible in the current Android versions, I would hope to see this get fixed before the Android 11 release.

Tickets reporting this issue but closed:

ni...@gmail.com <ni...@gmail.com> #4Sep 4, 2018 11:18PM

This also very likely affects the new Jetpack App Startup library which heavily relies on ContentProviders.

Given those (Firebase, Jetpack App Startup) are official Google products I am wondering whether this means that Android Backup will be sunsetted soon or otherwise would need extensive changes to its implementation (which would likely be hard to roll out to older devices as AFAIK it's shipped with the OS). Would be great to get some official statement here so that we have enough time to migrate away our apps from Android Backup to some other backup service.

jo...@google.com <jo...@google.com> #5Aug 16, 2019 03:09AM

It's been a bit over a year since I reported this issue, and I have a feeling that it hasn't been resolved in Android 12. Nudging this ticket a bit to hopefully get some eyes on this, especially since Hilt seems to require the Application class to be extended.

jo...@google.com <jo...@google.com> Aug 17, 2019 01:32AM

Status: Won't Fix (Intended Behavior)

ap...@google.com <ap...@google.com> #6Aug 17, 2019 04:11AM

The issue of apps restarting in Restricted Mode after a crash has been fixed in Android T.