Questions
Cold Start Splash Screen ANR & Firebase Credentials Removal
In a previous question, we shared an issue we are having where our Android app hangs on the splash screen logo during a cold start, leading to a system ANR (Input dispatching timed out / jdk.internal.misc.Unsafe.park).
In your analysis of our Android logs, you noted that the build issue/hang relates to the OneSignal integration and recommended removing our Firebase credentials from the Median build configuration.
Could you explicitly clarify the exact steps for removal? Does removing the credentials mean we should completely delete the google-services.json file from the Median Dashboard > Build and Deploy > Google Services section?
iOS Universal Link opens app but loses deep-link path on cold start
Podés pegarlo, pero yo lo haría un poco más minimalista porque el portal es público.
No es sensible compartir:
Google Play Data safety – which device IDs does my Median app collect?
Hello,
Security
Does media support Flags Secure
Android app bundle signing ID
Hi there - I receive an error when uploading the aab file to Google Play Store (Your Android App Bundle is signed with the wrong key) with the expected and actual key used. I've entered the Android developer fingerprint for the app into the ADI registration snippet but seem to be on the wrong track altogether -any assistance to resolve this would be appreciated
Release Key
Hi Median Support,
Keystore files missing from Android source download (Starter plan)
Hello,
Two Blocking Issues Android
Hi Median Team,
We recently rebuilt our Android app with targetSdk 36 and found two blocking issues in the generated Android project. Both worked correctly in our previous targetSdk 34 build.
App ID: 1nxdn54wp33fe8f80gxd3g15v4
Affected build: 4.1.7 / versionCode 119 / targetSdk 36
Test device: OnePlus 13 / Android 16
App Store rejection on device type (iPad Air M3, iPadOS 27.0
Hi Median team,
My paid Starter app has already been published to Google Play Internal Testing using the Android package name org.proweightloss.app.
My paid Starter app has already been published to Google Play Internal Testing using the Android package name org.proweightloss.app.
After rebuilding the app, Median reverted the Android Package Name to the default co.median.android... value and the field is now locked. Google Play rejects the new AAB because the package name no longer matches the existing app.
Please reset/update the Android Package Name for this licensed Median app to:
org.proweightloss.app
I need future AAB builds to continue using this existing Google Play package name.