Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Users report issues with closing interstitial Ads #94

Closed
UnbackedFan opened this issue Apr 25, 2020 · 4 comments
Closed

Users report issues with closing interstitial Ads #94

UnbackedFan opened this issue Apr 25, 2020 · 4 comments

Comments

@UnbackedFan
Copy link

UnbackedFan commented Apr 25, 2020

I am having few users report to me that the interstitial ad is not responsive (cannot click the x button to close the ad) or that they get a black screen only. I have tried to reproduce it in simulators and on my iOS devices but I was not able to. I was hoping someone else might have had such issues and could help me resolve it.

Here's some additional information.

  • Device tested on: iPod touch 7th gen v13.1.3 and iPhone 4 v9.3.5
  • User device where issue occured: iPhone 6 v12.4.6
  • I am using the libGDX framework to develop my app for iOS.
@obigu
Copy link
Collaborator

obigu commented Apr 28, 2020

You should specify which versions of ad framework(s) and bindings your are using. It happens that some campaigns cause a bug with in ad network SDK (for example some playable ads) and some ad networks SDK versions are also not very stable. If it's just a few users that have reported that is the most probable cause of this issue.

@UnbackedFan
Copy link
Author

I am using the latest robopods version which is 2.2.3-SNAPSHOT and the Google Mobile Ads framework version 7.52.0 if I'm not mistaken. I wasn't sure how to verify the version from the framework file itself. Does the binding support the latest Google Mobile Ads framework which is 7.58.0?

@obigu
Copy link
Collaborator

obigu commented Apr 28, 2020

Latest RoboPods version is 2.2.3 (README was outdated). Bindings were created for version 7.42.2. The farther from the version the bindings were created for the more possible changes the API has suffered. Usually, changes in the "minor" (2nd) version number indicate no major changes in the API have occurred. You will probably be able to use 7.58.0 with current bindings except if you need to use recent additions to the API. The kind of issue you describe doesn't seem related to a binding issue.

@UnbackedFan
Copy link
Author

Alright, I'll try the latest framework version. Thank you for your time.

@obigu obigu closed this as completed Jul 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants