Seems the CI is failing because the example app is still using the old plugin syntax. I can open a PR for that sometime soon

Looks good to me 👍

Seems the CI is failing because the example app is still using the old plugin syntax. I can open a PR for that sometime soon

fixed in here
#2482

Wait, I think we shouldn't remove the AndroidServiceStartType option completely, because there are two valid values for this setting: the START_NOT_STICKY and START_REDELIVER_INTENT. The first would cause the foreground service to stop entirely if the system needs to pause that activity. And the latter would schedule the foreground service to resume when resources are available, correct? I don't think it's right to only allow use of the START_NOT_STICKY mode, because many people may want their notifications to persist.

If a value has to be hard-coded, it should be the START_REDELIVER_INTENT option so foreground services will continue to be reliable on Android. But I can see a use for both, so I suggest keeping the option in place, setting the default to START_REDELIVER_INTENT, and removing the START_STICKY option, because that one is not supported by this library.