Configuring for Android

Android Manifest

With the Fyber Unity Plugin version 9, we automatically add the necessary declarations to your manifest. If your app does not have a manifest yet we'll add Unity's default.

You can change this behavior (including feedback dialogs) on the Fyber's Edit Settings menu.

b010b76-fyber_settings_editor_menu.pngc033c6a-check-manifest-menu.png

You can then click the Check AndroidManifest button to make sure your manifest has the necessary entries, and they will be added If there were some missing. You can see the resulting output in the Unity's Console window.

The following are the needed entries.

Required Permissions

Permissions
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />

Required Activities

Activities
<activity android:name="com.fyber.ads.ofw.OfferWallUnityActivity" android:configChanges="orientation|screenSize" />

Integrating Google Play Services

We recommend you use the Google Play Services, as otherwise we aren't able to access your Google Advertising ID. This leads to limited ad inventory, as an increasing number of advertising campaigns require the identifier. This ID is also essential for tracking daily active users (DAU) on your app. Besides, it is required for using some mediated Ad Networks.

Note

Fyber SDK only requires the com.google.android.gms:play-services-ads library. Your app may require additional APIs from Google Play Services here.

Google Integration Tip

We recommend using the official Unity JAR Resolver plugin released by Google. The plugin is intended to be used by any Unity plugin that requires access to Google play-services or Android support libraries on Android. The goal is to minimize the risk of having multiple or conflicting versions of client libraries included in the Unity project. The plugin, as well as the requirements and usage intructions can be found here: Unity JAR Resolver

Google Play Services requires the following entry in your AndroidManifest.xml file inside the <application> element:

Google Play Services entry
<meta-data android:name="com.google.android.gms.version" android:value="@integer/google_play_services_version" />

We check your manifest for the previous Google Play Services entry and warn you if we don't find any. You can add it by going through the menu Fyber -> Edit SDK Settings and clicking on the button Add Google Play Services entry.

If you have not integrated Google Play Services yet, please refer to the Google Play Services documentation. And if you are integrating only some Google Play Service APIs, don't forget to add Google Mobile Ads.

Common Error

Forgetting to add Google Mobile Ads as part of your Google Play Services integration, could prevent some mediated ad networks to start, lead to poor performance or even cause crashes.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request