Questions

Hello Median Support,

With active: true, the bottom tab bar renders during app launch before our JavaScript can run. With active: false, a runtime setTabs({enabled: true}) call succeeds (confirmed via on-screen debug) but the bar never appears. Is there a supported way to have the tab bar start hidden at launch but still be enableable at runtime? Or does active: false permanently disable it regardless of runtime calls?

My native iOS push notifications arrive empty even though:

Does the Starter plan allow setting a custom Android Package Name?

We've implemented a custom navigation pattern for our Bottom Tab Bar to avoid full page reloads on tab switch. All 5 tabs are set to Button Type "Run JavaScript," each calling a global function we've exposed on our page (window.syncBuyNavigate(path), which internally calls our SPA's client-side router — confirmed present in our deployed code via direct file inspection). Each button also calls median.tabNavigation.selectTab(index) afterward.
Despite this, tapping between tabs still shows the app's splash screen, as if the WebView is doing a hard reload/relaunch rather than executing our JavaScript in the page's existing context.
Our question: does the javascript:-URI execution triggered by a "Run JavaScript" tab button run in the same window/JS context as our page's own script (i.e., can it actually see and call a function we defined on window from our app's own code), or does Median evaluate it in an isolated/sandboxed context that wouldn't have access to our page's globals? If it's the latter, what is the correct way to call into our SPA's own JavaScript from a "Run JavaScript" tab button?

How do i get the uuid to match so i can install apps through vpn and management?

Asunto: Restaurar proyecto POS y asociar la versión 6.2

Why does the audio not work on demo? I am testing on a free account before I pay for the app build, but when I test it, there is no sound

const result = await median.revenueCat.login({ appUserID });

Hi Median Support,