Presence Publisher

org.ostrya.presencepublisher

Republished from GitHub / F-Droid by the Zapstore main account.

[<img src="https://f-droid.org/badge/get-it-on.png" alt="Get it on F-Droid" height="75">](https://f-droid.org/packages/org.ostrya.presencepublisher) [<img src="https://play.google.com/intl/en_us/badges/static/images/badges/en_badge_web_generic.png" height="75" alt="Get it on Google Play">](https://play.google.com/store/apps/details?id=org.ostrya.presencepublisher&pcampaignid=pcampaignidMKT-Other-global-all-co-prtnr-py-PartBadge-Mar2515-1)

First release: Nov 25, 2025, 1 total release.

Most recent release: Nov 25, 2025.

Repo

Appears in 0 app stacks.

0 sats / 0 zaps received in the past year.

Sats Received

Underlying data available via MCP: app_zaps, app_releases.

Zap Count

Underlying data available via MCP: app_zaps, app_releases.

Releases

Nov 25, 2025 2.7.0

The main reason for this release was a bug I encountered in my own setup, where I have multiple Wi-Fi networks all connected to the same home network. I sometimes saw disconnect events and then the devices reported being disconnected for hours, even though it was clearly connected. It took some time (and debug logs) to figure out that a new Android feature was to blame. More recent Android devices can be connected to several Wi-Fi networks at the same time. What happened was that one network got connected, the previous network got disconnected, and since I only tracked "connected" or "not connected", I got stuck on being disconnected. The solution is that devices with SDK 31+ (i.e. Android 12) now track all connected networks at once. This leads to a :warning: breaking change :warning: : the `connectedWifi` message now returns a list instead of a string. Otherwise only minor changes: * update to target SDK 36 * support for insets in the UI * (expected) better logging performance by formatting strings only if the log level is active

More…

* changes in message context providers to avoid SecurityException due to missing permissions