I'm setting a custom buffer screen to display before call an ad pod. It seems that it takes the device a few seconds to actually call RAF from the network and parse the pod and then display the buffer screen. Any way to get the this to work faster?
The question is unclear to me. Can you show MWE (minimal working example) of the code or explain in detail what are you doing?
Typically, in the CSAI, preroll case you'd call `.getAds()` and then `.showAds()`. `.setAdBufferScreen()` applies only to the latter, as the name implies. There is no "buffering" during the former, when VAST/VMAP is fetched and parsed. Plus, you one be doing that in a background thread during content play, so that fn has no UI. If you interrupt main content, call getAds, then call showAds, then resume content - and want to keep it that way, w/o complications - then you can show some splash screen during the `getAds()` call.
PS. i wonder if some new tech in the upcoming RAF 2.4 may help your case. when do you show ads and how do you determine the ad breaks position? Are there mid-rolls? is there 1 or more ads per breaks?