Thanks. I’m sure that code sample will be useful in future.
Just to round off this topic, I have now learnt that Capacitor only works when the main Activity is active - the bridged WebView does not keep running while the Activity is paused/stopped. Since Android can’t activate additional Activities when another app is in the foreground, my immediate use for responding with data to system events (specifically via the AutoFillService) is invalid and I’ll instead need to develop some native code entirely unrelated to Capacitor.
So it’s totally my fault for not understanding some of the basics of Android application structure until now. Still, perhaps it’s interesting to see that these fundamental rules of Android apps can sometimes be unknown to developers whose first introduction to creating a mobile app is through the Capacitor getting started guide.
