We were getting weird errors around the service not calling startForeground() that I couldn't reproduce. I figure it must be something with how we only sometimes start the FcmFetchService in the foreground. So I think the safest thing to do is to just use GenericForegroundService. |
||
---|---|---|
.. | ||
assets | ||
java | ||
jniLibs | ||
proto | ||
res | ||
AndroidManifest.xml |