Skip to content

4.4.2 — URGENT: fixes broken incoming calls for system-managed (voice) apps

Choose a tag to compare

View all tags
@murugancmi murugancmi released this 14 Aug 04:37
· 2 commits to main since this release
v4.4.2
ae679b9

Upgrade immediately if your app resolved ^4.3.17 to 4.4.0/4.4.1 and uses a system-managed (non-selfManaged) phone account — e.g. voice apps on @telecmi/piopiy-native.

4.4.0's zombie-call sweep cycled (unregister + re-register) the Telecom phone account at app start and before incoming calls. For self-managed accounts that is harmless — but cycling a CALL_PROVIDER (system-managed) account destroys its user enablement, after which Android refuses the app's incoming calls until the user manually re-enables the account in phone settings.

4.4.2 gates every account-cycling site to self-managed accounts only. After upgrading, affected users may need to re-enable the calling account once (Settings → Apps/Calls → Calling accounts) — the enablement destroyed by 4.4.0 does not restore itself.

Upgrade note (Android): if your app's own AndroidManifest.xml re-declares io.wazo.callkeep.VoiceConnectionService (older piopiy setup guides had this), the build now fails with a manifest-merger conflict on foregroundServiceType. Remove the app-level <service> declaration — the library manifest provides it with the full type set.

Assets 2
Loading