Bug 40326 - Facebook Audience Network lock http requests
Summary: Facebook Audience Network lock http requests
Status: NEW
Alias: None
Product: Components
Classification: Xamarin
Component: Xamarin Components ()
Version: Production (addons.xamarin.com)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Israel Soto [MSFT]
Depends on:
Reported: 2016-04-13 05:00 UTC by Luigi Saggese
Modified: 2016-05-23 09:08 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 40326 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Luigi Saggese 2016-04-13 05:00:10 UTC
we have a big issue with FB Audience component.

We have integrating Facebook Audience Network on iOS with this placement "1565183867039238_1982661485291472" but on different devices and FB accounts API answer is always this 

[FBAudienceNetworkLog/FBAdProvider:137 <error>] Ad request error: Error Domain=com.facebook.ads.sdk Code=1001 "No fill" UserInfo={FBAdErrorDetailKey={ msg = "No fill. We are not able to serve ads to this person. Please refer to https://developers.facebook.com/docs/audience-network/faq#a12. If you are integrating Audience Network for the first time, you can use test ads https://developers.facebook.com/docs/audience-network/testing."; }, NSLocalizedDescription=No fill} 

We have referred also docs a12 but there are "No limits on iOS ads" and all accounts are logged to Facebook.

We have read carefully documentation and we have check condition of "No fill" on iOS and Android. 

We would like to use Facebook Native Ads in our job listing each 5 job advert we want show 1 Facebook Native Ads. 

What is strange is this case (on same device): 

Installing app in DEBUG MODE Facebook Native Ads are shown correctly 
Installing app in RELEASE MODE USING TESTFLIGHT Facebook Native Ads respond "No Fill" 
Installing app via APPSTORE Facebook Native Ads LOCK others HTTP requests. We have check it via Charles (http://www.charlesproxy.com/) and API call does not start because is in loading Facebook call. This happens on all devices that download app via APPSTORE. 

Our app is developed via Xamarin Component https://components.xamarin.com/view/fbaudiencenetworkios 

What seems really strange is same code on same device and same FB user (mine Luigi Saggese) on different release type have different behaviour. Debug Mode: OK 
Release Mode using TestFlight: "No Fill" without locking other API calls
App Store: No response locking other API calls 

On TestFlight mode we have found this answer on StackOverflow that seems realistic (http://stackoverflow.com/questions/29779758/facebook-native-ads-on-ios) "Test Flight rotates through a pool of IDFA's and hides the users true IDFA, making it difficult to identify a Facebook user – and that is required for delivering an ad." 

Please help us to solve this issue, we have also written to Facebook support and they say as that Xamarin is maintaining component.

Let us know,
Comment 1 Luigi Saggese 2016-05-18 08:21:50 UTC
Any news?
Comment 2 Luigi Saggese 2016-05-23 09:08:52 UTC
No updates after 50 days...