@poolse/react-native 2.16.2 → 2.17.0

package/CHANGELOG.md

@@ -4,6 +4,31 @@ All notable changes to `@poolse/react-native` are documented here.
 Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/);
 versions follow [semver](https://semver.org).
 
+## [2.17.0] — 2026-08-24
+
+### Fixed
+
+- **Ringback played an iPhone ringtone.** On iOS the library resolves
+  `startRingback("_DEFAULT_")` to `/Library/Ringtones/Marimba.m4r`, so
+  the caller heard the sound the callee's phone makes. `_DTMF_` is
+  remapped to `_DEFAULT_`, so the only correct option is to ship a tone:
+  `CallScreen` now asks for `_BUNDLE_`, and the app supplies
+  `incallmanager_ringback.mp3`. If it is absent the library falls back
+  to the ringtone, which is no worse than before.
+
+## [2.16.3] — 2026-08-24
+
+### Fixed
+
+- `RingToneModule` is loose again, like `LiveKitModule`. Spelling the
+  real signatures out made `react-native-incall-manager` unassignable —
+  function parameters are contravariant, so any difference at all (an
+  argument required rather than optional, `number | number[]` rather
+  than `number[]`) means no app can pass the module in, and it breaks
+  again on the next upstream change. Narrowed at the point of use.
+
+  2.16.1 and 2.16.2 both attempted this and shipped without it.
+
 ## [2.16.2] — 2026-08-24
 
 ### Fixed

package/dist/index.cjs

@@ -5902,8 +5902,8 @@ function CallScreen({
     const ringing = calls.phase === "ringing-out";
     if (!ringing && !showingIncoming) return;
     try {
-      if (ringing) inCallManager?.startRingback?.("_DEFAULT_");
-      else inCallManager?.startRingtone?.("_DEFAULT_");
+      const start = ringing ? inCallManager?.startRingback : inCallManager?.startRingtone;
+      start?.("_DEFAULT_");
     } catch {
     }
     return () => {