IssueTracker

Sorry, I believe my team can't act on this information in its current state. We're not sure how to reproduce.

Can you either provide a repro project? Or a very clear set of repro steps starting with a new project?

Here you are test project.

Thank you! We'll take a look.

One thing I just learned from the data binding compiler folks is that <fragment> tags are actually ignored intentionally, so if you look at the code the compiler generates, any <fragment> with an id on it won't be found there.

In other words, this:

activity_main.xml

   <fragment
        android:id="@+id/id1"
        android:layout_width="match_parent"
        android:layout_height="match_parent" />

    <TextView
        android:id="@+id/id2"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content" />
        android:text="Hello World!" />

generates this:

ActivityMainBinding.java

public final class ActivityMainBinding implements ViewBinding {
  @NonNull
  private final ConstraintLayout rootView;

  @NonNull
  public final TextView id2;

  private ActivityMainBinding(@NonNull ConstraintLayout rootView, @NonNull TextView id2) {
    this.rootView = rootView;
    this.id2 = id2;
  }

^ Notice no id1 in there

So for me, what I need to do is make sure <fragment> tags don't generate binding fields in the IDE.

But for you, there's no reason to wait for that fix, because it doesn't help you. I'm not sure what you're trying to accomplish here, but you'll have to do it without using an ID on your <fragment> tag. This seems like an intentional design decision by the data binding team.

Starting in 4.2 Canary 9, we will no longer show fields for <fragment> tags to match the behavior of the data binding compiler.

Apologies to OP because this probably isn't the fix they were hoping for :)

See my comment #5 for more details.