[notifications][android] fix notification categories in standalone ap…

…ps (expo#10624)

* fix notification categories in standalone apps

* Update CHANGELOG.md

CHANGELOG.md

@@ -16,6 +16,7 @@ Package-specific changes not released in any SDK will be added here just before
 
 ### 🐛 Bug fixes
 
+- Fix `NotificationsHandler` & `ExpoNotificationCategoriesModule` reading from the wrong SharedPreferences files, resulting in categories not being applied in Android standalone apps. ([#10624](https://github.com/expo/expo/pull/10624) by [@cruzach](https://github.com/cruzach))
 - Set mIntentUri from intent in DetachActivity.onCreate to fix Linking.getInitialURL in Android standalone apps ([#10535](https://github.com/expo/expo/pull/10535) by [@esamelson](https://github.com/esamelson))
 - Only update the splash screen when it receives update configuration values on iOS ([#10512](https://github.com/expo/expo/pull/10512) by [@brentvatne](https://github.com/brentvatne))
 - Only update the splash screen when it receives update configuration values on Android ([#10522](https://github.com/expo/expo/pull/10522) by [@esamelson](https://github.com/esamelson))

android/expoview/src/main/java/host/exp/exponent/experience/DetachedModuleRegistryAdapter.java

@@ -12,6 +12,8 @@
 import java.util.List;
 import java.util.Map;
 
+import expo.modules.notifications.notifications.categories.ExpoNotificationCategoriesModule;
+import expo.modules.notifications.notifications.handling.NotificationsHandler;
 import expo.modules.notifications.notifications.scheduling.NotificationScheduler;
 import host.exp.exponent.kernel.ExperienceId;
 import host.exp.exponent.utils.ScopedContext;
@@ -50,8 +52,10 @@ public List<NativeModule> createNativeModules(final ScopedContext scopedContext,
     // Overriding expo-file-system FileSystemModule
     moduleRegistry.registerExportedModule(new ScopedFileSystemModule(scopedContext));
 
-    // `NotificationScheduler` needs to share `SharedPreferences` object with the notifications services, we don't want to use scoped context.
+    // Certain notifications classes should share `SharedPreferences` object with the notifications services, so we don't want to use scoped context.
     moduleRegistry.registerExportedModule(new NotificationScheduler(scopedContext.getBaseContext()));
+    moduleRegistry.registerExportedModule(new ExpoNotificationCategoriesModule(scopedContext.getBaseContext()));
+    moduleRegistry.registerExportedModule(new NotificationsHandler(scopedContext.getBaseContext()));
 
     // Adding other modules (not universal) to module registry as consumers.
     // It allows these modules to refer to universal modules.