There is a 3rd possible workaround i can think of, if really really insisting on designing the channel for FHD only:
- Do not supply the 3rd, optional parameter `view` in showAds()
When present, it indicates to RAF to use the native-RSG implementation which currently exhibits the issue.
If no 3rd param however, RAF would suspend roSgScreen temporarily - then use the legacy (SDK1) ads implementation, which does not have the issue - and then resume RSG. NB: when using the RAF's non-native-RSG implementation, the getAds()/showAds() calls have to be done "the old way" - from the main thread, not from a RSG task.
That's a temporary band-aid to be sure. The issue will be resolved in a following version of RAF.