Questions

when i created a ecom app using median and razorpay i cant see the option to pay using upi but have card,netbanking,and wallet,i added link handling rules,deeplink etc tried many times o devolopment

iOS doesn't save or suggest passwords on the app's login screen. It works fine in Web browser (mobile and desktop) but not in the app.

I am trying to set up this integration with iOS IPA Build Configuration. The key that has been generated definitely has an Admin role. When I upload the key and information, I get an error that the key requires an admin role.

I am trying to upload my '.mobileprovision' file to configure my iOS IPA Build. However, the file is either not being read/being uploaded to the median website. No error/message being show either.

Hi, following up on my original question on this topic as my question hasn't had a reply yet, though I can see a question submitted after mine has already been answered. I'd really appreciate a response, as this is a live issue affecting a launched app.

We are experiencing an issue where clicking a verified deep link successfully opens our native Median app, but instead of routing the webview to the specific target path, the app consistently drops the user onto the configured Initial URL (the homepage).

OneSignal is configured with App ID, JavaScript Bridge is enabled on Starter plan, but median_library_ready never fires and onesignal.register() never shows the iOS permission prompt. onesignalInfo() always returns empty. What am I missing in the Median App Studio configuration?"

Hi, I'm hoping for some help diagnosing an issue that appeared between our TestFlight build and our App Store release.

Summary: Push notifications using targetUrl in Additional Data (per your docs: median.co/docs/open-url-from-notification) correctly deep-link into the app on warm start (app already open/backgrounded), but on cold start (app not running), tapping the notification opens the app at the homepage instead of the target URL.
What changed: This worked correctly in our TestFlight build (tested prior to release). After submitting to the App Store in mid-May, cold-start deep linking broke. We also noticed a new "Powered by Median" native launch screen appeared around this time, suggesting our App Store build was running a newer/different native wrapper version than our working TestFlight build.
We've since rebuilt and resubmitted (approved and live on our test devices as of yesterday -6th July 2026) with no other changes - the issue persists identically. So this isn't a stale-build issue; the current build has the same problem.

Diagnostics we've gathered (via our own telemetry logging before/during app load):

"I'm on the Free plan. My current app has Bundle ID. Does upgrading to Starter allow me to change the Bundle ID in App Studio to match my existing App Store Connect app? I need to update my existing app submission, not create a new one."

please i need this "Android SHA-1 certificate fingerprint"