You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
None of the service types appear to be a reasonable choice for our Lnd service, so perhaps we should use specialUse and explain via metadata that our intent is to run Lightning network node persistently for the user, in order to receive incoming payments, et cetera.
The text was updated successfully, but these errors were encountered:
I think abusing mediaplay might work as a fallback
I'm afraid they will punish us if we aren't honest.*
Right now I'm leaning towards using specialUse. I found out that you're supposed to declare your service in the Play Console, which gives us an opportunity to clearly explain what we want to do.
*) I use suppose we could use mediaPlay and introduce podcasting support like Breez has lol.
Or make Blixt into a music player playing music from John Berg and Dj Kazic.
In Android 14, foreground services must explain the intent of the service.
https://developer.android.com/about/versions/14/changes/fgs-types-required
This will hopefully make phone vendors respect AOSP foreground service policies, which has been a huge problem in the past.
Samsung for example is promising to follow it: https://developer.samsung.com/mobile/app-management.html
None of the service types appear to be a reasonable choice for our Lnd service, so perhaps we should use
specialUse
and explain via metadata that our intent is to run Lightning network node persistently for the user, in order to receive incoming payments, et cetera.The text was updated successfully, but these errors were encountered: