Windows AdMediatorControl not displaying test ad - windows-phone-8

I'm setting Microsoft Advertising through Ad Mediator.
I did all required setups* but the ad doesn't appear on emulator.
It is set up to:
Application ID: test_client
Ad Unit ID: Image480_80
I'm building it for Windows Phone 8.
*added Connected Service, set up Microsoft Advertising there, checked capabilities, put AdMediatorControl into drawing surface
Does anyone encountered such problem?

Fixed the problem. Maybe it'll be interesting for someone else.
Ad Mediator stops working if there are other advertising plugins even if they are not used in game.
In my case it were prime31 ads.

Related

Agora.io: android.permission.CAMERA not compatible with Oculus device

I'm developing an VR Video Chat application using Agora.io api and Unity3D Engine, in which a main user streams his webcam from a standalone Pc to users equippped with an Oculus device.
As soon as I try to upload the VR app to the Oculus Server, I got that error:
This app uses permission(s) that are not compatible with this device: android.permission.CAMERA.
How do I overcome that issue?
Any suggestions?
I haven't programmed for Oculus yet but here are some ideas:
First you may try just to set android:required=“false” in the manifest to see what happens?
Secondly check the official Oculus documentation here to see if helps? https://developer.oculus.com/blog/tech-note-android-plugins-and-permissions/?locale=en_US
"You will need to modify your Android Manifest file. Because the Oculus Quest doesn’t have cameras (well, none that can be used for this demo) we will get rid of the camera use requirement ( ) located on line 9 in the folder Assets/Plugins/Android/AgoraRtcEngineKit.plugin "
This is a quote from this quick start tutorial which will get you up and running with Agora.io Video chat and Oculus Quest. It explains how to stream your webcam from a standalone PC to Oculus Quest. https://medium.com/#jake_agora.io/live-realtime-video-to-vr-oculus-quest-6bbb74e4fc63
Just in case anyone else falls into this. The solution posted where you remove the entry from the Agora included manifest doesn't work anymore, and I can't identify where its being added from, perhaps Agora can post a solution. The only way around it is to export from Unity, edit the Manifest to remove the unwanted camera permissions and then build in Android Studio.

Can GoogleAds.dll be re written for windows uwp

I know there's a admob GoogleAds.dll for windows phone 8, can we decompile it and rewrite by changing the adview control with some uwp control ? Will it be a violation ? Is it possible to do this ?
If you already have ad boxes created before the announcement has been issued that you could no longer generate ad for wp from admob you can re-insert the code, but otherwise it is no longer possible, regards.

WIndows Phone AdMediation control doesn't work with adduplex

I've integrated the AdMediation control into my Windows Phone app. This works fine for pubCenter and Google AdMob but not for adduplex.
According to the documentation, I've used the App ID from adduplex (App key in adduplex dashboard) but I still get a configuration error banner displayed. I found this blog post a few days ago. The post says that I have to use the Ad unit ID (banner in adduplex dashboard) instead of the App key but this it does not work either.
Can somebody who is using the AdMediation control with adduplex explain me the right way?
AdDuplex uses new identifiers since the introduction of AdDupplex Interstitial ads.
The AppId identifier has been replaced with AdUnitId and AppKey, but the ad mediator still uses an older version of AdDuplex SDK at the time of writing.
How to make it work
The conceptual changes made in AdDuplex are backwards compatible. The Ad unit ID is made to be interchangeable with App ID used by older SDKs.
So you will just have to set the App ID in the Ad Mediator configuration to AdDuplex Ad unit Id.
I still get the ad configuration error
If you are using an emulator for testing you will still get the ad configuration error. For some reason ad mediator uses a different configuration when run in an emulator. It basically ignores your settings and just uses 0 for App ID
There is a workaround for this. The test configuration can be edited in the AdMediator.config file, which is added to the project with the ad mediator control. Find the TestConfiguration tag and change it's AppId value from 0 to your Ad unit Id
Double check the ID which you've provided, whether it's the Windows Phone Store ID or the App ID provided by adduplex. Found a workaround here too.
Adduplex showing error "ad unit configuration error"
I solved this exact same problem changing the config in the project to the Ad Unit Id (the 5-6 digit number).
What did not work for me was only changing the config in Dev Center > AdMediator.
So you probably need an update for your app with the updated Ad Unit Id.

VS2013 deploys Windows Phone app to emulator only after 'Rebuild Solution' command

Something weird happened to one of my C# Windows Phone 8 Silverlight projects.
It's a simple page with one TextBox I'm experimenting with, building a customized style for it. First I placed a TextBox on the PhoneApplicationPage, generated a style template for it using the 'Edit Template\Edit a Copy' command from the context menu in the designer. Now I'm changing some setters and property values in the style, but when I hit F5, an old version of my project is launched in the emulator - all my recent changes aren't taken into account. The latest changes are reflected in the launched app only after I issue the 'Rebuild Solution' command from the Build menu.
The XAML markup has no errors, and it seems all stuff is correct. Other WP8 projects are built and deployed to the emulator ok too. The problem does not depend on the selected emulator (WVGA 512Mb, 720p, etc). Restarting VS/emulator has no effect too.
What it can be and how to fix it?
Some more info. For any normal project I see this in the Output window when I hit F5 (the app full path was shorten to save space):
But for the problem project, the output log ends on the line '1> Xap packaging completed successfully' and the old version of the app is opened in the emulator immediately.
It seems, I have managed to find the reason of this strange issue. This can happen if the name of a WP app includes spaces! I noticed that if we create a new project and use the space character in its name, the spaces are replaced with the underscore characters on the phone (for instance, "WP Test App" is deployed under the name "WP_Test_App"). I also found this while searching for a solution of this problem:
App doesn't get updated then debugging - incrmental update not correctly working?
I played a little bit with the names of my project and solution, i.e. removed the spaces in them, and it helped to solve my puzzle.
BTW, as the author of the question under the above link states, this problem never occurred in the WP 7.1 SDK - it is specific only for the WP 8 SDK.

using camera class in android in flex

The default camera showing up is the back camera using Camera getCamera
I want to know how to switch to front camera.
Also Camera names length is showing only length as 1 and not 2 , but i am having a front and back camera on galaxy tab, so i think it should show 2 names.
Please let me know a way out to this.
I am using air 3.1 , which is the latest version at present.
and the application is built in Flex 4.6 version
Air for Android only supports the back facing camera -- at least that might have been the case until very recently.
I have downloaded and saved the AS3 API reference from Adobe. On my local copy of the docs, it says this about the Camera.names property:
On Android, only one camera is supported, even if the device has more than one camera devices. The name of the camera is always, "Default."
However, when I look at the docs online, that comment is no longer there. So maybe Air 3.2 (released yesterday) now supports both cameras on Android!
Online docs:
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/media/Camera.html#names