Skip to main content
Version: v1.1.0

Platform differences

The plugin reports the same callbacks and result codes on both platforms. Where the native SDKs differ and the plugin can't close the gap, the difference is listed here.

Not available on one platform​

FeatureAndroidiOS
initializeSdk(nonTrackingUrl:)Ignored✓
setSourceApp, setItunesId (SKAdNetwork)Ignored✓
PrebidFullscreenControls.supportSKOverlayIgnored✓ (core and GAM)
PrebidFullscreenControls.isAutoCloseOnCompletionEnabledIgnored✓ (interstitials only)
Rewarded skip controls✓Ignored
Rewarded adFormats (core; Android always requests banner and video) and minimum size (PrebidFullscreenControls.minSizePercentage, core and GAM; AdMob and MAX rewarded have none)Ignored✓
Original API pbAdSlot, impOrtbConfig, globalOrtbConfig on a PrebidMultiformatAd that Prebid Android serves with its multiformat PrebidAdUnit: native with any other format or with isInterstitial / isRewarded, rewarded with a banner, and video without banner sizes outside a fullscreen adIgnored: PrebidAdUnit has no setters; use PrebidTargeting.setGlobalOrtbConfig. Other units send them on both, and gpid is sent on both in every case✓
Native response image width / height (PrebidNativeImage)null✓
Interstitial / rewarded adPosition (core)Always fullscreen (pos 7): no setter on Prebid Android's fullscreen units✓
PrebidMobile.setDebugLogFileEnabledIgnored (getDebugLogFileEnabled returns null)✓
PrebidMobile.getTimeoutMillisDynamicnull: Prebid Android writes Prebid Server's timeout into getTimeoutMillis✓
PrebidMobile.setLocationUpdatesEnabledIgnored (getLocationUpdatesEnabled returns null): Android reads the last known location✓
PrebidTargeting.getAppKeywords, getSourceApp, getItunesIdEmpty / null✓
PrebidInstreamVideoAd.generateInstreamUriForGam size 320x480Throws, like any size but 640x480 and 400x300✓
Banner videoParameters (core, GAM, AdMob, MAX)SDK defaults✓
Interstitial / rewarded videoParametersmaxDuration caps the rendered video✓ every field
App keywords (PrebidTargeting.addAppKeyword and the rest)Logged and ignored: set app.keywords with setGlobalOrtbConfig✓
Original API SKAdNetwork (activateBannerSKAdNetwork, activateInterstitialSKAdNetwork, activateSKOverlay, supportSKOverlay)No-ops✓

Behavior the plugin aligns​

TopicNative differenceWhat you get
Banner auto-refreshiOS refreshes every 60 s by default and clamps 0 to 15 snull / 0 disables refresh on both
Original API auto-refreshPrebid Android's PrebidAdUnit can't refresh; iOS ignores intervals under 30 sRefresh works on both, clamped to 30–120 s
Status check disablediOS reports "skipped"succeeded on both
Empty seat bidAndroid reports successprebidDemandNoBids on both
Requests before initAndroid drops them silently; iOS runs themOn Android, in every package: onAdFailed ("The Prebid SDK is not initialized"), or prebidSdkNotInitialized from the Original API, PrebidMultiformatAd and instream video. GAM native reports onFetchDemandFailed('prebidSdkNotInitialized'), then loads the GAM ad alone
Native impressionFired when a tracker request succeeds (never without trackers)PrebidNativeAdView: viewability, half the view for 1 s, including Flutter's clipping, once per ad. PrebidGamNativeAd keeps Prebid's tracker callback
Banner onAdClickediOS reports a click that leaves the app through a separate callbackonAdClicked for every click, once (core and GAM banners)
Native custom layout clicksPrebid Android clicks a registered view; Prebid iOS has no click APIPrebidNativeAd.performClick on both
Stored auction responsePrebid iOS clears it when a banner is deallocatedKept until you clear it
PrebidTargeting.setAppName, setBundleNamePrebid iOS has no app-name or bundle setterSent on both; on iOS through the global OpenRTB config (your own app.name / app.bundle there wins on both)
Interstitial / rewarded winningBid (core)Prebid iOS keeps the bid internalSet on both: on iOS the plugin's event handler keeps the bid Prebid hands it
AdMob native impOrtbConfig, globalOrtbConfigPrebid Android's mediation native unit has no settersSent on both: on Android the plugin runs the auction with the native unit inside it
Creative factory timeoutsiOS stores secondsMilliseconds on both
pbAdSlot on interstitial / rewarded (every package) and on AdMob / MAX banners and native adsPrebid iOS has no setter on these unitsSet on both through imp.ext.data.pbadslot in impOrtbConfig (yours wins)
gpid on banners, interstitials and rewarded ads (every package) and on AdMob / MAX nativeNeither SDK has a setter on these unitsSet on both through imp.ext.gpid in impOrtbConfig (yours wins)
PrebidTargeting.setUSPrivacyStringNeither SDK has a setter: both read IABUSPrivacy_String from the IAB storageWritten to the IAB storage (SharedPreferences / UserDefaults), so it persists across launches until cleared with null, like a CMP's value
Google Mobile Ads version checkPrebid checks the GMA version only when the app passes itWith GMA linked, initializeSdk passes it on both (a warning in the log if Prebid doesn't support it)
Log level nonePrebid iOS has no such level; Prebid Android's NONE logs everythingSilent on both
Log level or listener changed after initializeSdkPrebid Android applies them only when it initializesApplied right away on both
PrebidMobile.setLogListenerAndroid filters by level before its logger; iOS's logger replaces the console oneMessages at or above the log level, instead of the console, on both

Remaining differences​

  • Banner refresh bounds: Prebid clamps the banner interval to 30–120 s on Android and 15–120 s on iOS.
  • Banner impression tracker (Original API): iOS tracks the current bid; Android attaches the GAM view when the next auction's bids arrive. See impression tracking.
  • Runtime server switch: on iOS setPrebidServerUrl throws for a malformed URL and leaves the nonTrackingUrl from initializeSdk in place, and getPrebidServerUrl returns the URL the current user's auctions use. Android accepts any string.
  • Calling initializeSdk again: Android reports succeeded without a new status check (and waits for an initialization that native code started); iOS runs the initialization and the status check again.
  • Creative timeouts from Prebid Server: Android applies cftbanner / cftprerender from the response's ext.prebid.passthrough (and getCreativeFactoryTimeout returns them); Prebid iOS reads them but doesn't use them.
  • Rendering API caching (iOS): creating an Original API ad unit turns useCacheForReportingWithRenderingApi on.
  • Native request ext fields: an asset's ext (on its title, img or data object) is sent on both platforms; NativeAsset.assetExt and NativeEventTracker.ext only on Android, because Prebid iOS has no asset-level ext and doesn't serialize the tracker's.
  • Log levels: Android has no verbose or severe: they log at debug and error.
  • Interstitial and rewarded "leaving the app": iOS reports it separately from the click; the plugin reports the click (onAdClicked) on both and doesn't forward it.
  • Result codes: both platforms report the same names for the same outcome. A few exist on one platform only: prebidInvalidContext, prebidInvalidAdObject, prebidInvalidNativeRequest and prebidSdkNotInitialized on Android; prebidServerNotSpecified, prebidInvalidResponseStructure, prebidInternalSDKError, prebidWrongArguments, prebidNoVastTagInMediaData and prebidSDKMisuse on iOS. prebidUnknownError is an iOS code; on Android it only stands for a code from a newer Prebid than the plugin knows.
  • Prebid version: Android pins an exact Prebid version, iOS accepts a range. See Compatibility.

Not exposed, on purpose​

  • Prebid Android's PrebidMobile.setPbsConfig (not exposed by the plugin): Prebid writes it from Prebid Server's response (ext.prebid.passthrough), and its timeouts take precedence over the app's. Set the creative timeouts with setCreativeFactoryTimeout and setCreativeFactoryTimeoutPreRenderContent.
  • BannerView.setStoredAuctionResponse (iOS): it sets the process-wide stored auction response, not one for the banner. Use PrebidMobile.setStoredAuctionResponse.
  • Native getWinEvent / getImpEvent (Android): Prebid fires the win and impression events itself. The Original API returns them in PrebidBidResponse.events for apps that report them on their own.
  • Plugin renderers (registerPluginRenderer): a renderer is a native object, so register it from the app's native code (MainActivity / AppDelegate) before loading ads; Prebid then uses it for the plugin's ads too. The plugin's views don't forward the renderers' own events (PluginEventListener on Android, PluginEventDelegate on iOS).