I am working on displaying an iAd advertisement before a video plays, but the ad is not playing and I receive the following error:
Error Domain=ADErrorDomain Code=0
"The operation couldn’t be completed. (ADErrorDomain error 0.)"
There is no clear solution to me. So I have some doubt whether iAd is available in my region or not.
iAd is supported in India. You can see it included in the most recent list of iAd supported countries.
Your issue may be that you've set your iAd Testing Fill Rate to 0% on your development device.
Go to Settings>Developer>Fill Rate> and set it to 100%.
Also, make sure you're giving your advertisement time to load before trying to present it. Check out my implementations of iAd's Pre-Roll Video Ads here: Swift, Objective C.
Related
We are currently using Facebook Audience Network with AdMob mediation on our iOS app. We are using latest version for FAN(5.2.0) and Google Ads(7.41.0) from CocoaPods. The implementation is done fully done as per the documentation here - https://developers.google.com/admob/ios/mediation/facebook and tested the implementation using tools here - https://developers.facebook.com/docs/audience-network/testing however no error was found.
The issues are facing are that
1) The ad icon image is not being sent by Facebook to AdMob, we checked using direct Facebook Native ads and icons are present there but the same ad data shows icon as 'nil' when passed through mediation
2) We are seeing gray ad choices icons(as attached) however upon clicking the icon the app crashes with stack trace in FB library(stack trace attached).
Can any once advise on how we can get rid of these issues?
Just set adOptionsView.nativeAd = nativeAd
When you open the Health app, it updates it's values from somewhere, but if you don't actually open the app, the Healthkit only seems to update randomly (and very scarsely). For example, Step data objects don't get pulled from (wherever the iOS source comes from) or the Apple Watch until you actually open the Health app.
Is there a way to update the information programmatically? Or is the Health app itself just querying CoreMotion and making its own Step object that way? (This wouldn't help me much, since I'm actually trying to use the Healthkit to monitor heart rate)
You cannot control how frequently HealthKit imports data from the Apple Watch. If you want to get live values for readings that come from CoreMotion on the phone itself, such as step counts, you can use HKObserverQuery or HKStatisticsCollectionQuery with an updateHandler.
I'm exploring the end user experience for a beacon prototype but I'm struggling to find any end-user scenarios that involve the app becoming active / opening up on the screen when within range.
I can get the app to send a notification and this is the most likely experience on both Android and iOS but does anyone know if it is possible to get the app to open up?
It's unlikely that I'd want real customers to have their experience interfered with in this way, I think it's ok if the app is already running and is open but not if it's running but not open.
Thanks
On Android this is possible. The reference app for the Android Beacon Library demonstrates how to do exactly this.
On iOS, it is not possible due to OS security restrictions. See here for details. The best you can do is send a local notification to the user when the beacon is detected, then if the user gestures to it, bring up the app.
I have a problem with iAd. I have followed many tutorials that are of excellent quality, and a few days ago I was able to correctly insert iAd in a test application.
Now the method does not work even if I try to create a new application with only the iAd as a test! I cannot understand the problem appears to me the following text.
I use xCode 5 and iOS 7 SDK.
iAD prova[3158:a0b] [AppDeveloper] ADBannerView: Unhandled error (no delegate or delegate does not implement didFailToReceiveAdWithError:): Error Domain=ADErrorDomain Code=3 "The operation couldn’t be completed. Ad inventory unavailable" UserInfo=0xa5aaaf0 {ADInternalErrorCode=3, ADInternalErrorDomain=ADErrorDomain, NSLocalizedFailureReason=Ad inventory unavailable}
2013-09-20 12:24:59.887 iAD prova[3158:a0b] [AppDeveloper] ADBannerView: Unhandled error (no delegate or delegate does not implement didFailToReceiveAdWithError:): Error Domain=ADErrorDomain Code=5 "The operation couldn’t be completed. Banner view is visible but does not have content" UserInfo=0xa5af280 {ADInternalErrorCode=5, ADInternalErrorDomain=ADErrorDomain, NSLocalizedFailureReason=Banner view is visible but does not have content}
There are errors in the code, I read about this user "ajay" who posted this:
Finally I solved problem myself, none of the blog didn't give any solution. I am not getting Test ad in the simulator it is coming in the device only by changing of the internal proxy settings. It's good experience for me and also my suggestion is while your operating with IOS device make sure to take proxy free device so that at least you can eliminate some of the issue related to proxy, don't forget to work proxy related stuff at the end product.
But I do not understand how I should proceed.
Also, you can change your fill rate in Settings.app. Set it to 100% if you want it to show up all the time.
I got the same error message on both a real device and a simulator with iOS 7. But same code works well and iAd banner can show on iOS 6 simulator. Looks like Apple's iAd server does not provide any Ad for iOS 7. Maybe it is a bug.
I can't get the real ads to work, in the xcode simulator i can see the test ads,now i'm using Xib and AdViewController to display the ad.
This are the message that i recieve:
Unable to fill ad request. This is a common situation.
AdMob: Did fail to receive ad in AdViewController
I need some help wiith this issue because i'm stuck, thanks.
You'll get real ads in your real, submitted app. On the simulator, only the test ad to show that things are working.
When using the simulator you'll get a mix of situations. Sometimes you'll get test ads and things will work. Sometimes you'll actually get simulated errors. The latter is so that you can test your code so that it can handle all situations when dealing with ads.