ID_CAP_PHONEDIALER required for advertising toolkit? RRS feed

  • General discussion

  • Hello,

    We would rather not have our app require phone calls (as it’s
    pretty scary sounding- “Applications that can place phone calls. This may
    happen without a visual indication for the end user.”), but it seems whenever
    we add the advertising assembly, this requirement shows up. Sure enough, if you
    perform the Capability requirements on the Microsoft Advertising dll, ID_CAP_PHONEDIALER
    is detected. We have to include the advertising assembly (I guess it isn’t one
    of the ones that is already present on the phone, like mscorlib and doesn’t
    need to be included in the xap). In all of the testing, it worked fine with ID_CAP_PHONEDIALER
    not present, and I think it handles the UnauthorizedAccessException, but we
    cannot specify that we don’t want this capability when we submit it, right?

    I suppose they must go together, so if we want advertising,
    we must also need the ID_CAP_PHONEDIALER, but if there is any other way, please
    let me know.


    • Moved by Shaun Taulbee Friday, February 11, 2011 8:14 PM Migration data
    Saturday, February 5, 2011 4:48 PM

All replies

  • Some advertisements shown by the Microsoft AdControl may launch a phone call when they are tapped by the user, so the capability is required.  Even if you remove the capability from your app, the capability will be re-added by the marketplace submission process.
    “Applications that can place phone calls. This may
    happen without a visual indication for the end user.”

    Where did you see this?  The phone call task only shows the dialer with the number pre-entered, and the user must start the call.
    Saturday, February 5, 2011 10:06 PM