IssueTracker

error instantiating androidx.tracing.perfetto.StartupTracingConfigStoreIsEnabledGate

This looks like a minification issue

1. Are you using either minification of your app, or in your instrumented test? If so, can you try adding a keep rule for that class?
2. Is this class present in your apk's dex files, if you open the apk in studio? (if this is an instrumented test, check both your app and test)
3. Are you depending on androidx.compose.runtime:runtime-tracing via androidTestImplementation or implementation, and from what type of module?
4. What version of AGP are you using? I would expect the manifest entry for this class would mean the library doesn't need an explicit keep rule, but it could be b/328649293 depending on your AGP version / how the dependency is declared (fixed in AGP 8.6 canary 5, but a keep rule should work around it)

Edit: disregard, I doubt Robolectric is using any of the minification codepaths.

2. Let me check
3. Using implementation and it's added at the project level so all modules using compose are getting it
4. I'm on 8.1.1

An extra typo was introduced as part of cr/2431573.

See the number "3" at the end of the full-stop : https://source.corp.google.com/h/android/platform/frameworks/support/+/androidx-main:autofill/autofill/src/main/java/androidx/autofill/HintConstants.java;l=43;drc=83f915c2279272bcef85ffeb95dd58c43fee1083

We need to fix that, and re-ramp autofill all the way to stable.

Hi aurimas@google.com, will 1.3.0-alpha01 be deprecated soon? Is there any key date that we need to meet? Thanks!

#4 seems to suggest that you want to release a stable, #5 suggests you want to deprecate it. What do you want to do? Note, if you deprecate it the process is described here https://g3doc.corp.google.com/company/teams/androidx/api_guidelines/deprecation.md#for-entire-artifacts but you have to have a plan on where developers should move to instead of this library.

Hi @au...@google.com, we don't want to deprecate the library. I think @ji...@google.com wanted to know if there's any particular date that we need to graduate to stable, and what are the drawbacks of remaining in alpha?

go/androidx/releasing_overview#cadence has details on the cadence. I will note that 1.3.0-alpha01 was shipped 5/24/2023 - more than a year ago!

Any updates here? What's blocking this from going 1.3.0 stable?

It was last pushed to 1.3.0-beta01 previously.

Is there a way for us to use the same build and push to prod.

A lot has diverged since the last stable push, and reading the instructions, it seems like we should just do cherrypicks on top of that build. A fresh build is discouraged.

1. Is it possible to do fresh build (using what's pushed to beta).
2. If not, are there tools to find diff of the changes pushed since last stable push?

Please follow the instructions at go/androidx/releasing_rc01.

Thanks @al...@google.com. Just to confirm we are on the same page, we already have a prior stable version. If I understand correctly, we can follow the instructions at go/androidx/releasing_rc01 for 1.3.0 stable instead of following instructions at go/androidx/releasing_rc0X_or_stable.

Am I understanding that correctly?

Correct. go/androidx/releasing_rc0X_or_stable is for when you already released rc01 and need to release rc02 (or later) or stable. go/androidx/releasing_rc01 is when you are going from betaXX to rc01.

Project: platform/frameworks/support
Branch: androidx-main
Author: Simranjit Kohli <simranjit@google.com>
Link:      https://android-review.googlesource.com/3348649

Update Autofill to 1.3.0-rc01 BUG: 336368997

Update Autofill to 1.3.0-rc01 
BUG: 336368997 
 
Change-Id: Icd87385bbe138d773c5606b0b13353d814391b01

I set up 1.3.0-rc01 release in jetpad for Feb 12, 2025.

http://go/jetpad/globalreleaseinfo?releaseDate=1739383200000