[ASK] How to properly set Google IMA in the JWPlayer config

[normtronics]

What isn't clear?
Currently I am working on getting google IMA to work properly in the player. In order for the player to pick up the right client, we have to set the forceLegacyConfig to true in the JWConfig. Is there a way to get google IMA to work without having to force use the legacy config?

When I don't use the forceLegacyConfig the ad play callback just returns this:

DEBUG [handleAdPlay]:  {"client": null, "target": 2323, "type": null}

With the forceLegacyConfig set to true I see:

 DEBUG [handleAdPlay]:  {"client": "googima_sdks", "message": "onAdEvent", "type": 8}
 DEBUG [handleAdPlay]:  {"message": "onAdEvent", "reason": "external", "type": 6}
 DEBUG  [handleAdPlay]:  {"client": "googima_sdks", "message": "onAdEvent", "type": 0}

I would like to not use the legacy config if possible.

Here is an example config we are passing to the player:

let jwPlayerConfig = {
  advertising: {
    adClient: 'ima',
    adSchedule: [] // needed on android, without it android crashes 
  },
  autostart,
  forceLegacyConfig: true, // Would love to not have to use this 
  license: jwPlayerKey,
  playlist,
  styling: {
    colors: {
      timeslider: {
        progress: 'cf0000',
        thumb: 'cf0000',
      },
    },
    displayTitle: false,
    displayDescription: false,
  },
};

[Jmilham21]

@normtronics are you getting ad playback when not using forceLegacyConfig? I think the issue is probably related to the way we are parsing the adEvent callback, unless you aren't able to run ads using something like the example in SingleExample.js in our Example app.

[normtronics]

@Jmilham21 Apologies for the delay in my response.

Yes, the ads still run fine. It's the callback that isn't working correctly.