Questions

Hello Median Support Team,

I am having a persistent Android OneSignal registration problem with my app LivingBreadHub.

I have followed the current Median + OneSignal setup and have verified the Firebase and OneSignal configuration several times.

App configuration:

OneSignal plugin: Enabled

OneSignal SDK: v5 / Legacy Mode Disabled

OneSignal App ID: Configured

Automatic Registration: Automatic

Automatic Data Transfer: Automatic

Foreground Notification: Show

Firebase Service Account JSON: Uploaded to OneSignal

google-services.json: Uploaded to Median

Firebase Project ID: livingbreadhub-49730

Median Android package name: co.median.android.yexloej

Firebase Android package name: co.median.android.yexloej

The package names match exactly.

Problem on the Android device:

LivingBreadHub displays “Push notifications are not supported on this device.”

OneSignal → Analytics → Subscriptions shows Total Subscribed = 0 for my test device.

Android Settings → Apps → LivingBreadHub → Notifications shows “This app hasn't received any notification yet.”

No notification categories/channels are created.

Android notification permission is enabled.

I completely uninstalled the previous APK and installed a freshly rebuilt APK, but the problem remains exactly the same.

I also asked OneSignal's diagnostic assistant to audit the setup. OneSignal confirmed that:

Android/FCM is enabled and configured.

The FCM v1 Service Account credentials are valid.

There are no credential/configuration errors.

OneSignal has successfully registered an Android subscription at some point, confirming that the OneSignal App ID and FCM credentials are valid.

Their diagnosis is that my current device is failing to obtain/register an FCM token before the registration reaches OneSignal, pointing toward the client-side/native Android integration.

I have also verified that the Firebase project ID and Android package name are correct and identical between Median and Firebase.

Could Median please investigate whether the generated Android APK is correctly including and initializing the native Firebase/FCM and OneSignal SDK, particularly:

OneSignal SDK initialization

Firebase/FCM initialization

FCM token acquisition

OneSignal push subscription registration

Android notification channel creation

I would also like to know whether there is currently a known issue with the latest Median Android OneSignal integration or code generation that could cause this behavior.

I have already performed a clean uninstall/reinstall and a fresh rebuild, so I would appreciate a check of the native Android build/integration rather than repeating the basic Firebase/OneSignal configuration steps.

Thank you.