如何在Android后台Service中实现WebView的JavaScriptInterface通知触发

Hey Ivan, let's break down how to solve this problem—getting your notification trigger to work even after closing the app from the recent list.

Is it feasible to run the JavaScriptInterface in a background Service? #

Yes, it's possible, but there are some critical caveats to keep in mind:

• WebView is a UI-heavy component designed for Activity contexts, so hosting it in a Service requires careful lifecycle management to avoid memory leaks.
• On Android 8.0+, background Services are heavily restricted, so you'll need to use a Foreground Service to keep your WebView running reliably.
• A Service-hosted WebView won't render any UI, but it can still execute JavaScript and communicate with your WebAppInterface perfectly.

Step-by-Step Implementation #

1. Create a Foreground Service to Host the WebView

This Service will initialize the WebView, load your remote page, and keep running in the background. Here's how to set it up:

public class WebViewMonitorService extends Service {
    private WebView mBackgroundWebView;

    @Override
    public void onCreate() {
        super.onCreate();
        // Initialize WebView on the main thread (required for WebView operations)
        mBackgroundWebView = new WebView(this);
        WebSettings webSettings = mBackgroundWebView.getSettings();
        webSettings.setJavaScriptEnabled(true);
        
        // Attach your JavaScript interface
        mBackgroundWebView.addJavascriptInterface(new WebAppInterface(this), "Android");
        
        // Load the same remote page your Activity uses
        mBackgroundWebView.loadUrl("http://serveraddress/your-monitoring-page");

        // Set up Foreground Service (mandatory for Android 8.0+)
        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
            NotificationChannel channel = new NotificationChannel(
                "webview_monitor", 
                "Server Monitor", 
                NotificationManager.IMPORTANCE_LOW
            );
            NotificationManager notificationManager = getSystemService(NotificationManager.class);
            notificationManager.createNotificationChannel(channel);

            Notification foregroundNotification = new NotificationCompat.Builder(this, "webview_monitor")
                .setContentTitle("Monitoring Server")
                .setContentText("Keeping an eye on your devices")
                .setSmallIcon(R.drawable.ic_monitor)
                .build();

            startForeground(1001, foregroundNotification);
        }
    }

    @Override
    public IBinder onBind(Intent intent) {
        return null; // No binding needed for this use case
    }

    @Override
    public int onStartCommand(Intent intent, int flags, int startId) {
        // Restart the service if it's killed by the system (when resources allow)
        return START_STICKY;
    }

    @Override
    public void onDestroy() {
        super.onDestroy();
        // Properly clean up WebView to avoid memory leaks
        if (mBackgroundWebView != null) {
            mBackgroundWebView.removeJavascriptInterface("Android");
            mBackgroundWebView.loadUrl("about:blank");
            mBackgroundWebView.stopLoading();
            mBackgroundWebView.setWebViewClient(null);
            mBackgroundWebView.setWebChromeClient(null);
            mBackgroundWebView.destroy();
            mBackgroundWebView = null;
        }
    }
}

2. Update WebAppInterface for Service Compatibility

Modify your interface to send notifications directly from the Service context (no need to rely on Activity methods anymore):

public class WebAppInterface {
    private final Context mServiceContext;

    public WebAppInterface(Context context) {
        mServiceContext = context;
    }

    @JavascriptInterface
    public void showTempHumUnavailableNotification(String message) {
        sendAlertNotification("Temp/Hum Sensor Unavailable", message);
    }

    @JavascriptInterface
    public void showSecurDudeAlertNotification(String message) {
        sendAlertNotification("Security Alert", message);
    }

    private void sendAlertNotification(String title, String content) {
        NotificationManagerCompat notificationManager = NotificationManagerCompat.from(mServiceContext);

        // Create notification channel (Android 8.0+)
        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
            NotificationChannel alertChannel = new NotificationChannel(
                "device_alerts", 
                "Device Alerts", 
                NotificationManager.IMPORTANCE_HIGH
            );
            notificationManager.createNotificationChannel(alertChannel);
        }

        Notification notification = new NotificationCompat.Builder(mServiceContext, "device_alerts")
            .setContentTitle(title)
            .setContentText(content)
            .setSmallIcon(R.drawable.ic_alert)
            .setPriority(NotificationCompat.PRIORITY_HIGH)
            .setAutoCancel(true)
            .build();

        notificationManager.notify((int) System.currentTimeMillis(), notification);
    }
}

3. Declare Permissions and Service in Manifest

Add the necessary permissions and register your Service in AndroidManifest.xml:

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

<application ...>
    <service
        android:name=".WebViewMonitorService"
        android:foregroundServiceType="dataSync" />
</application>

4. Start the Service from Your Main Activity

Trigger the Service when your app launches to start background monitoring:

@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);

    // Start the background monitoring service
    Intent serviceIntent = new Intent(this, WebViewMonitorService.class);
    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
        startForegroundService(serviceIntent);
    } else {
        startService(serviceIntent);
    }

    // You can keep your original Activity WebView if needed, but it's no longer required for notifications
}

A Better Alternative: Ditch WebView Entirely #

While the above works, using a WebView for simple server checks is overkill. You can achieve the same result with lightweight network requests (like OkHttp) in the Service, which uses fewer resources and avoids WebView-related bugs:

private void checkDHT11Status() {
    OkHttpClient client = new OkHttpClient();
    Request request = new Request.Builder()
        .url("http://serveraddress/OnomeWeb/resources/data/tmp/onomeDHT11On")
        .build();

    client.newCall(request).enqueue(new Callback() {
        @Override
        public void onFailure(@NotNull Call call, @NotNull IOException e) {
            // Request failed = sensor unavailable
            sendAlertNotification("Temp/Hum Sensor Unavailable", "Connection lost");
            // Schedule next check (e.g., every 30 seconds)
            scheduleNextCheck();
        }

        @Override
        public void onResponse(@NotNull Call call, @NotNull Response response) throws IOException {
            if (!response.isSuccessful()) {
                // Non-200 response = sensor data unavailable
                sendAlertNotification("Temp/Hum Sensor Unavailable", "Data not accessible");
            }
            // Schedule next check
            scheduleNextCheck();
        }
    });
}

private void scheduleNextCheck() {
    new Handler(Looper.getMainLooper()).postDelayed(this::checkDHT11Status, 30000);
}

This approach is faster, more stable, and uses less memory than running a full WebView in the background.

内容的提问来源于stack exchange，提问作者Ivan S.