Android开机完成后RxJava网络请求无数据返回问题求助

Hey there! Let's break down why your RxJava subscription isn't returning any data when handling the BOOT_COMPLETE intent, and fix the entire flow for your 4 network requests + notification logic.

First, let's tackle the core issue of your RxJava code not emitting data, then move on to the proper way to handle background work after a boot broadcast (since broadcast receivers have super short lifespans).

1. Fix the RxJava Subscription Issue #

The most likely culprits here are missing thread scheduling or an improperly implemented getAllItems() observable:

• You forgot subscribeOn(Schedulers.io()): Network requests can't run on the main thread (Android blocks this since API 11), and without specifying an IO thread, your request might never execute or throw a hidden exception. Add this to your observable chain:

  provider.getAllItems()
      .subscribeOn(Schedulers.io()) // Critical for network operations
      .observeOn(AndroidSchedulers.mainThread())
      .subscribe(...)
  

• Check getAllItems() implementation: Make sure your observable actually emits data via onNext() when the network request succeeds. If it's skipping onNext() and calling onCompleted() directly, your subscriber will never get any data. Double-check for unhandled errors in the provider code (use onError() in your subscriber to catch these!).

2. Don't Do Async Work Directly in a Broadcast Receiver #

Broadcast receivers are destroyed right after onReceive() finishes. If your RxJava network calls are asynchronous, the receiver will be gone before they complete, leading to canceled subscriptions or leaked resources. Instead, use WorkManager (the recommended way for background tasks in modern Android) to handle the heavy lifting:

Step 1: Update Your Manifest #

Add the required permissions and components:

<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
<uses-permission android:name="android.permission.INTERNET" />

<!-- Boot Completed Receiver -->
<receiver android:name=".BootCompletedReceiver">
    <intent-filter>
        <action android:name="android.intent.action.BOOT_COMPLETED" />
        <action android:name="android.intent.action.QUICKBOOT_POWERON" /> <!-- For some devices -->
    </intent-filter>
</receiver>

<!-- WorkManager Initializer (for AndroidX) -->
<provider
    android:name="androidx.work.impl.WorkManagerInitializer"
    android:authorities="${applicationId}.workmanager-init"
    android:exported="false"
    android:enabled="@bool/enable_work_manager_init" />

Step 2: Broadcast Receiver to Trigger WorkManager #

public class BootCompletedReceiver extends BroadcastReceiver {
    @Override
    public void onReceive(Context context, Intent intent) {
        if (Intent.ACTION_BOOT_COMPLETED.equals(intent.getAction())) {
            // Enqueue a one-time work request to handle network calls
            OneTimeWorkRequest dataFetchWork = new OneTimeWorkRequest.Builder(DataFetchWorker.class)
                    .build();
            WorkManager.getInstance(context).enqueue(dataFetchWork);
        }
    }
}

Step 3: RxWorker to Handle 4 Network Requests & Notification #

Use RxWorker (a WorkManager class built for RxJava) to manage your async flow safely:

public class DataFetchWorker extends RxWorker {
    private final YourDataProvider provider; // Inject or initialize your provider here

    public DataFetchWorker(@NonNull Context context, @NonNull WorkerParameters params) {
        super(context, params);
        provider = new YourDataProvider(); // Adjust based on your setup
    }

    @NonNull
    @Override
    public Single<Result> createWork() {
        // Define your 4 network request observables
        Observable<List<ContentValues>> request1 = provider.getAllItems().subscribeOn(Schedulers.io());
        Observable<List<ContentValues>> request2 = provider.getSecondItems().subscribeOn(Schedulers.io());
        Observable<List<ContentValues>> request3 = provider.getThirdItems().subscribeOn(Schedulers.io());
        Observable<List<ContentValues>> request4 = provider.getFourthItems().subscribeOn(Schedulers.io());

        // Combine requests: use concat() for sequential execution, zip() for parallel
        return Observable.concat(request1, request2, request3, request4)
                .toList() // Collect all 4 results into a single list
                .map(allResults -> {
                    // Your data comparison logic here
                    boolean meetsCondition = checkIfDataMeetsRequirements(allResults);
                    if (meetsCondition) {
                        sendNotification(getApplicationContext());
                    }
                    return Result.success();
                })
                .onErrorReturn(throwable -> {
                    Log.e("DataFetchWorker", "Failed to fetch data", throwable);
                    return Result.failure();
                });
    }

    private boolean checkIfDataMeetsRequirements(List<List<ContentValues>> allResults) {
        // Implement your comparison logic here
        // Example: Check if any result contains a specific value
        for (List<ContentValues> resultSet : allResults) {
            for (ContentValues values : resultSet) {
                if ("target_value".equals(values.getAsString("key"))) {
                    return true;
                }
            }
        }
        return false;
    }

    private void sendNotification(Context context) {
        // Build and send your notification
        NotificationManager notificationManager = (NotificationManager) context.getSystemService(Context.NOTIFICATION_SERVICE);
        
        // Create a channel for Android O+
        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
            NotificationChannel channel = new NotificationChannel(
                    "BOOT_ALERT_CHANNEL",
                    "Boot Data Notification",
                    NotificationManager.IMPORTANCE_DEFAULT
            );
            notificationManager.createNotificationChannel(channel);
        }

        Notification notification = new NotificationCompat.Builder(context, "BOOT_ALERT_CHANNEL")
                .setContentTitle("Data Alert")
                .setContentText("Found matching data after boot!")
                .setSmallIcon(R.drawable.ic_notification)
                .setAutoCancel(true)
                .build();

        notificationManager.notify(1001, notification);
    }
}

3. Critical Testing Tips #

• Test the broadcast: Use ADB to send the boot broadcast without restarting your device:

  adb shell am broadcast -a android.intent.action.BOOT_COMPLETED -n com.your.package/.BootCompletedReceiver
  

• Ensure app is not in "restricted" state: Some devices block boot broadcasts for apps that haven't been launched yet. Open your app at least once after installing it.
• Check error logs: Use Logcat to look for exceptions related to network calls, RxJava, or broadcast receivers.

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