Fragment通信方案选型：使用Bundle传参可能存在哪些问题？

Great question! It’s totally understandable to lean towards the simplicity of setArguments(), but there are several key problems with using it for dynamic Fragment-to-Fragment communication that make Google’s recommended interface approach a better choice. Let’s break them down:

1. Critical Illegal State Exceptions #

First off, your current code has a hidden crash risk: setArguments() can only be called before a Fragment is attached to an Activity. Once the Fragment is added to the FragmentManager (which it is, since you’re fetching it via findFragmentByTag()), calling setArguments() will throw an IllegalStateException. This is explicitly enforced by the Android framework—this method is designed for initializing a Fragment with data before it’s launched, not updating it post-creation.

Your code snippet would fail at runtime if the Fragment is already attached, which is almost certainly the case in your Activity stack scenario.

2. No Automatic UI/State Updates #

Even if you somehow avoided the exception (which you can’t reliably do), updating the arguments doesn’t trigger any lifecycle callbacks in the target Fragment. Unlike an interface method call that can directly trigger UI refreshes or state changes, the Fragment won’t know its arguments have changed unless you add extra code to re-read them manually. For example, if your Fragment’s UI depends on the "Status" boolean, you’d have to write a separate method to refresh the UI after setting the arguments—adding unnecessary complexity that interfaces avoid.

3. Missing a Clear Communication Contract #

Interfaces create an explicit, type-safe contract between Fragments: the sender knows exactly what methods to call, and the receiver knows exactly what data to expect. With setArguments(), there’s no such guardrail. Other developers (or future you) won’t know what keys the Fragment expects, what data types are required, or when those arguments are supposed to be updated. This leads to preventable bugs like typos in key names (you already have one in your code: trur instead of true) that won’t be caught until runtime.

4. Misusing the Intended Purpose of arguments #

The Bundle passed via setArguments() is built for initialization data—think of it like constructor parameters for a Fragment. It’s meant to pass data that the Fragment needs to create its initial state (e.g., a user ID for a profile Fragment). Using it for dynamic, ongoing communication goes against its designed purpose, making your code less intuitive and harder to maintain over time.

When Should You Use setArguments()? #

Reserve it for when you’re first creating a Fragment and need to pass data that it requires to initialize itself. For example:

Bundle bundle = new Bundle();
bundle.putBoolean("InitialStatus", true);
BottomFragment fragment = new BottomFragment();
fragment.setArguments(bundle);
// Then add the fragment to the manager

For dynamic communication between existing Fragments in your Activity stack, stick with the interface approach—it’s safer, more maintainable, and aligns with Android’s best practices.

内容的提问来源于stack exchange，提问作者V I J E S H