teads / TeadsSDK-iOS

Teads SDK for iOS - Premium branded "outstream" ads
https://support.teads.tv/support/solutions/articles/36000314785-ios-sdk-developer-guide
MIT License
27 stars 11 forks source link

Sample App — All inRead Direct ads failed to deliver #225

Closed mrbodich closed 7 months ago

mrbodich commented 1 year ago

The issue:

If I select inRead or Native format, Direct provider, any Creative, and then any sample in the Integrations section, no ads are showing there. I am getting this error in the console:

🚨 [TeadsSDK:error] No ad delivered from server.

Expected behaviour:

Ads are loading and showing in any sample in the Integrations section.

Steps to reproduce:

  1. Clone the repo
  2. pod install
  3. Open TeadsSampleApp.xcworkspace
  4. Run the app
  5. Select inRead tab
  6. Select Direct provider
  7. Select any Creative
  8. Open any example in the Integrations section
elneruda commented 1 year ago

Hello @mrbodich, thank you for reaching us, depending on the region you are trying to request an ad, you could encounter some limitations. Can you try to select different creatives like Vertical, Square or Carousel?

mrbodich commented 1 year ago

Hello @elneruda, I've tried other Creatives, this section does not affect the result. Still getting the same error. I am working from Ukraine, never had any similar limitations (tried 2 different internet providers here, optical connection and LTE). Tried VPN, but I am getting another, some security check error when using it, not related to the discussed error.

🚨 [TeadsSDK:error] No ad delivered from server. (IVT DoubleVerify)
Error fetching banner: 3 - notFilled - No ad delivered from server. (IVT DoubleVerify)
mrbodich commented 1 year ago

Hello @elneruda, hope you are doing well. Here is what I am getting now when I have created my own code. Maybe it will help to better understand, as it has a description. I do not get the second row when running the Teads Sample App. Used same PIDs from the Teads Sample App.

🚨 [TeadsSDK:error] No ad delivered from server.
Error fetching banner: 3 - notFilled - No ad delivered from server.
mrbodich commented 1 year ago

UPD: I thought that was test ads saying Teads The global media platform, was confused because of differently looking items on tableviews for Native. But now see that there was not ads but just placeholders. So, getting the same error for Native ads. (the goal for us is to use inRead though)

🚨 [TeadsSDK:error] No ad delivered from server.
didFailToReceiveAd: 3 - notFilled - No ad delivered from server.
mrbodich commented 1 year ago

We have tried to build the app physically in 2 countries:

With the same result:

🚨 [TeadsSDK:error] No ad delivered from server.
didFailToReceiveAd: 3 - notFilled - No ad delivered from server.

⚠️ But the Android works well both Sample App and Teads library in the own app. So, we tried to understand why and found the issue.

You have put different publisher page URLs to Sample Apps for different platforms. iOS — https://www.teads.tv/ — ❌ does not work for any platform/country Android — http://teads.com/ — ✅ works for any platform/country

So for now the temporary solution for me is using http://teads.com/ on iOS, please investigate this and let me know the final solution.

mrbodich commented 1 year ago

UPD: http://teads.com/ is not working anymore too (tested in Ukraine and Poland, on iOS and Android)

Maybe there is some other way to test Teads ads? Unfortunately I could not find that in docs. Can you please help with this?

freddydotcom commented 1 year ago

I encounter the same problem. Did you already look into this matter?

elneruda commented 1 year ago

Hello @mrbodich sorry for the delay, I've made multiple tries on my own running behind VPN (Ukraine) with the PID 84242 This one could be the one that fills the most in our test placement list.

The publisher URL is the value that refers to the same content being seen by the end user that can be also reached through the publisher's website. In some cases you could have no URL to provide because the content is only available on the app and not on the website; in this case, you don't have to call the method pageUrl method.