Marshmallow及以下API出现循环依赖错误，高版本布局正常求助

Hey there, let's dig into this Marshmallow-and-below circular dependency issue you're facing! It's super weird that the same layout works fine on newer APIs but breaks on older ones—let's break down possible causes and fixes:

Circular dependency errors almost always include a specific chain in Logcat (look for tags like LayoutInflater or AndroidRuntime). For example:

Circular dependency between views with IDs @+id/viewA and @+id/viewB in ConstraintLayout

Grab that specific info first—it'll save you tons of guesswork. If you haven't already, filter Logcat to show only errors and look for the full stack trace.

You're using android.support.constraint.ConstraintLayout, and older versions of the support ConstraintLayout had bugs with complex constraint chains on pre-Marshmallow devices:

• Simplify constraints temporarily: Remove non-essential constraints from your parent TabLayout Fragment or child Fragment layouts, then re-add them one by one to find which one triggers the loop.
• Avoid bidirectional constraints: For example, if you have app:layout_constraintTop_toBottomOf="@id/viewX" on View Y, and app:layout_constraintBottom_toTopOf="@id/viewY" on View X, that's a direct loop. Adjust one side to use a fixed margin or anchor to the parent instead.
• Upgrade ConstraintLayout: If you're on an old version (like 1.0.x), bump it to the latest stable support version for API 23 compatibility (e.g., com.android.support.constraint:constraint-layout:1.1.3—it's the last stable support release that works well on pre-Marshmallow).

Pre-Marshmallow devices handle Fragment lifecycle callbacks slightly differently, which can lead to accidental circular references:

• Load child Fragments in onViewCreated(): Don't initialize child Fragments in the parent's onCreate()—wait until the parent's view is fully inflated. This prevents child Fragments from trying to reference uninitialized parent views.
• Avoid holding strong references to parent Fragments: If your child Fragment's Spinner/RecyclerView adapters need to communicate with the parent, use an interface callback instead of directly holding a reference to the parent Fragment. For example:

  // In child Fragment
  interface ChildCallback {
      fun onSpinnerItemSelected(item: String)
  }
  
  private var callback: ChildCallback? = null
  
  override fun onAttach(context: Context) {
      super.onAttach(context)
      callback = context as? ChildCallback
  }
  

• Use requireContext() instead of parent Fragment references: When initializing adapters, use requireContext() instead of parentFragment to avoid unnecessary strong links.

Sometimes indirect resource references (like drawables or styles) cause loops on older APIs:

• Test with default styles: Temporarily remove custom backgrounds, dividers, or styles from your Spinner/RecyclerView. If the error goes away, one of those resources is likely causing a loop (e.g., a style that inherits from itself, or a drawable that references another drawable which loops back).
• Avoid theme attribute loops: If you're using ?attr/ references in your layout, make sure the theme attributes don't create a circular chain (e.g., an attribute that references another attribute that references it back).

Double-check that your support libraries are aligned and compatible with API 23:

• Make sure com.android.support:support-fragment and com.android.support:appcompat-v7 are on the same version as your ConstraintLayout. Mismatched versions often cause odd behavior on older devices.
• If you're migrating to AndroidX, ensure all dependencies are fully migrated (mixing support and AndroidX libraries is a common source of pre-Marshmallow bugs).

Start with the error logs to get specific, then work through these steps—you'll likely find the issue is either a wonky constraint or an early Fragment initialization.

内容的提问来源于stack exchange，提问作者Coder