v9.1.18

Fixed

• Android: Fixed AbstractMethodError on RoomDatabase.createOpenHelper when consumer apps resolved androidx.room:room-runtime < 2.6.0. Root cause: the core AAR's Maven POM was empty (published via raw artifact() instead of from(components.release)), so Room and all other core dependencies were invisible to Gradle dependency resolution in consumer projects. The fix:
  • Core AAR now publishes a proper POM via from(components.release) with android.publishing.singleVariant("release"), exposing all runtime dependencies including Room 2.8.4
  • React Native bridge module now declares room-runtime:2.8.4, sqlite:2.6.2, and sqlite-framework:2.6.2 as api dependencies to guarantee they participate in consumer classpath resolution
  • Fixed fresco incorrectly scoped as api in core build.gradle — changed to implementation (not part of the public API)
  • Aligned guava (33.3.1 → 33.5.0) and work-runtime (2.8.0 → 2.11.1) versions between core and bridge to prevent silent downgrades

Note for consumers with custom dependency pinning: The core AAR POM now exposes its runtime dependencies. If you have resolutionStrategy.force or strictly constraints on any of these, verify compatibility after upgrading.

Full Changelog: https://github.com/marcocrupi/react-native-notify-kit/blob/main/CHANGELOG.md

yarn add react-native-notify-kit@9.1.18