Fragment中OnActivityResult回调异常求助：定位服务跳转后回调至Activity

Hey, let's tackle this problem step by step. I've run into similar issues before when dealing with location settings and Fragment callbacks, so here's what you can do to fix both the callback routing and the crash issue:

1. Route onActivityResult to Your Fragment #

First, the reason your callback is hitting the Activity instead of FragmentA is easily fixable—you just need to make sure your Activity forwards the result to its attached Fragments. In your ActivityA's onActivityResult method, call the parent implementation:

@Override
protected void onActivityResult(int requestCode, int resultCode, Intent data) {
    super.onActivityResult(requestCode, resultCode, data);
    // The super method automatically passes the result to all attached Fragments
}

Now you can override onActivityResult directly in FragmentA to handle the user's choice:

@Override
public void onActivityResult(int requestCode, int resultCode, Intent data) {
    super.onActivityResult(requestCode, resultCode, data);
    // Use a unique request code you define, e.g., 1001
    if (requestCode == YOUR_LOCATION_REQUEST_CODE) {
        LocationManager locationManager = (LocationManager) getContext().getSystemService(Context.LOCATION_SERVICE);
        boolean isLocationEnabled = locationManager.isProviderEnabled(LocationManager.GPS_PROVIDER) 
                || locationManager.isProviderEnabled(LocationManager.NETWORK_PROVIDER);
        
        if (isLocationEnabled) {
            // User enabled location, proceed with your logic
        } else {
            // User refused, close the app
            if (getActivity() != null) getActivity().finish();
        }
    }
}

2. Fix the Fragment Activity Launch Crash #

The crash when launching the location settings from FragmentA is almost certainly due to an improperly constructed Intent or missing safety checks. Here's the correct way to build and launch the intent safely:

private void promptUserToEnableLocation() {
    // Create the intent to open location settings
    Intent locationSettingsIntent = new Intent(Settings.ACTION_LOCATION_SOURCE_SETTINGS);
    
    // Critical: Check if any app can handle this intent to avoid crash
    if (locationSettingsIntent.resolveActivity(getContext().getPackageManager()) != null) {
        // Launch from Fragment using startActivityForResult with your unique request code
        startActivityForResult(locationSettingsIntent, YOUR_LOCATION_REQUEST_CODE);
    } else {
        // Fallback if device doesn't support location settings page
        Toast.makeText(getContext(), "Cannot open location settings", Toast.LENGTH_SHORT).show();
        if (getActivity() != null) getActivity().finish();
    }
}

Common crash causes to avoid:

• Typos in the intent action (double-check Settings.ACTION_LOCATION_SOURCE_SETTINGS)
• Using a null Context (always use getContext() instead of getActivity() if possible, and add null checks)
• Forgetting to verify the intent can be resolved (the resolveActivity check prevents "no activity found" crashes)

3. Bonus: Use the Modern Activity Result API (AndroidX) #

If your project uses AndroidX, ditch the old startActivityForResult entirely. The new ActivityResultContracts API lets you handle callbacks directly in the Fragment without relying on the Activity:

// Define the launcher in your Fragment's onCreate method
private ActivityResultLauncher<Intent> locationSettingsLauncher;

@Override
public void onCreate(@Nullable Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    
    locationSettingsLauncher = registerForActivityResult(
        new ActivityResultContracts.StartActivityForResult(),
        result -> {
            // Check if location is enabled after user returns
            LocationManager locationManager = (LocationManager) getContext().getSystemService(Context.LOCATION_SERVICE);
            boolean isLocationEnabled = locationManager.isProviderEnabled(LocationManager.GPS_PROVIDER) 
                    || locationManager.isProviderEnabled(LocationManager.NETWORK_PROVIDER);
            
            if (isLocationEnabled) {
                // Proceed with your app logic
            } else {
                // User didn't enable location, close app
                if (getActivity() != null) getActivity().finish();
            }
        }
    );
}

// Then launch the settings with this method
private void promptLocationEnable() {
    Intent intent = new Intent(Settings.ACTION_LOCATION_SOURCE_SETTINGS);
    if (intent.resolveActivity(getContext().getPackageManager()) != null) {
        locationSettingsLauncher.launch(intent);
    } else {
        Toast.makeText(getContext(), "Cannot open location settings", Toast.LENGTH_SHORT).show();
        if (getActivity() != null) getActivity().finish();
    }
}

This approach is cleaner, avoids request code conflicts, and keeps all location-related logic contained in FragmentA.

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