4. Compilation

To make a build of your game complete with the integrated Yumi SDK, please do the following steps:

1) Click File, choose Build & Run to compile, and complete the build and run screen that follows as needed.

2) Screen Orientation. While many games force a specific orientation, some allow for either portrait or landscape. Yumi, however, requires you to pick a default. The screen orientation in Unity3D shall also need to match the settings of AndroidManifest.xml file, as a conflict may lead to crash after starting application. The following image shows where this is set in the build process

3) Click【Build And Run】on the main screen and wait.

5.Conclusion

This concludes our integration document. We hope your project has gone smoothly, and we wish you well in monetizing your game with ads. Please don’t hesitate to reach out to your operations or technical support contact if you need any assistance in solving integration problems. We also value and welcome your feedback on this document and for the integration process in general. Thank you!

6.Exhibit A

Using your own AndroidManifest.xml file

To use your own file, please do the following:

(1) Add Permission(s)

Adding this 2nd permission (optional) will generally improve the ad fill rate.

<!-- yumi sdk start -->
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.READ_PHONE_STATE"/>
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.MOUNT_UNMOUNT_FILESYSTEMS"/>
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.DOWNLOAD_WITHOUT_NOTIFICATION" />
<uses-permission android:name="android.permission.CALL_PHONE"/>
<uses-permission android:name="android.permission.SEND_SMS"/>
<uses-permission android:name="android.permission.WRITE_CALENDAR"/>
<!-- yumi sdk end -->

Caution: If app targetSdkVersion is 23 or above, you will need to call the following permission check code. If the user has not previously provided permission, we will need to prompt user authorization via a popup. This process needs to be called before instantiating an ad. The android-support-v4.jar also will need to be added prior.

Caution: If app targetSdkVersion is 23 or above, you will need to call the following permission check code. If the user has not previously provided permission, we will need to prompt user authorization via a popup. This process needs to be called before instantiating an ad. The android-support-v4.jar also will need to be added prior.

uad.CheckPermission();

Note: The third-party platform adapter component registration details will be generated on our website automatically when you choose which Ad Networks you intend to work with.

7.Exhibit B

Options for Banner/Interstitial/Rewarded Video Access

1. Banner Options

a) Banner callback: The following callback messages are available to developers that would like to track or take certain game control actions (pause, unpause, etc.) conditional on these various ad status conditions. To use this option, inherit Assets.YumiUnityAdUtils.BannerAdCallbackListener [check] interface and use any of the following callback codes.

onBannerPreparedFailed(string data)

callback when banner loading failed, get failure reason via data.

onBannerPrepared(string data)

callback when banner loading success.

onBannerExposure(string data)

callback when banner show success.

onInterstitialClosed(string data)

callback when banner closed.

onBannerClicked(string data)

callback when banner clicked.

Sample:

#region Banner Callback
    //callback method when banner loading failed
    public void onBannerPreparedFailed(string data)
    { 
       ZplayLogger.Log("onBannerPreparedFailed:" + data); 
	}
	//callback method when banner loading success
    public void onBannerPrepared(string data)
    {
       ZplayLogger.Log("onBannerPrepared:" + data); 
	}
	//callback when banner show success
    public void onBannerExposure(string data)
    {
       ZplayLogger.Log("onBannerExposure:" + data); 
	}
	//callback method of banner close event
    public void onBannerClosed(string data)
    {
       ZplayLogger.Log("onBannerClosed:" + data); 
	}
	//callback of  banner click event
    public void onBannerClicked(string data)
    {
       ZplayLogger.Log("onBannerClicked:" + data); 
    }
    // callback method of Prepared
    #endregion

b) Banner width controls: The parameter status of isMatchWindowWidth can be used to autoexpand the banner width to the screen width, or to leave it in its default size. We recommend using the default “false” status (do not expand) to improve ad display performance. See below for the code to utilize, and also to see examples of the two banner display possibilities.

YumiUnityAdUtils.AddBannerAd(gameObject.name, isMatchWindowWidth);

2. Interstitial Options

Callbacks: The following callback messages are available to developers that would like to track or take certain game control actions (pause, unpause, etc.) conditional on these various ad status conditions. To make use of this option, inherit Assets.YumiUnityAdUtils.InterstitialAdCallbackListener interface and use any of the following methods.

onInterstitialPreparedFailed(string data)

callback when interstitial loading failed, get failure reason via data.

onInterstitialPrepared(string data)

callback when interstitial loading success

onInterstitialExposure(string data)

callback when interstitial show success.

onInterstitialExposureFailed(string data)

callback when interstitial show failed

onInterstitialClosed(string data)

callback when interstitial closed.

onInterstitialClicked(string data)

callback when interstitial clicked.

Sample:

#region InterstitialAd Callback
    //callback method when interstitial loading failed
    public void onInterstitialPreparedFailed(string data)
    { 
       ZplayLogger.Log("onInterstitialPreparedFailed:" + data); 
    }
    //callback method when interstitial loading success
    public void onInterstitialPrepared(string data)
    { 
       ZplayLogger.Log("onInterstitialPrepared:" + data); 
    }
    //method when interstitial show success 
    public void onInterstitialExposure(string data)
    { 
       ZplayLogger.Log("onInterstitialExposure:" + data); 
    }
    // method when interstitial show failed
    public void onInterstitialExposureFailed (string data)
    { 
       ZplayLogger.Log("onInterstitialExposureFailed:"); 
	}
    //callback of interstitial close event
    public void onInterstitialClosed(string data)
    { 
       ZplayLogger.Log("onInterstitialClosed:" + data); 
    }
    //callback of interstitial click event
    public void onInterstitialClicked(string data)
    { 
       ZplayLogger.Log("onInterstitialClicked:" + data); 
    } 
#endregion

3. Rewarded Video Options

Callbacks: The following callback messages are available to developers that would like to track or take certain game control actions (pause, unpause, etc.) conditional on these various ad status conditions. To make use of this option, inherit Assets.YumiUnityAdUtils. MediaAdCallbackListener interface and use any of the following methods.

onMediaExposure(string data)

when rewarded video starts successfully.

onMediaClosed(string data)

callback when rewarded video closed.

onMediaClicked(string data)

callback when rewarded video clicked. Note: this method does not guarantee 100% callback depending on the platform

onIsMediaPrepared(string data)

callback when rewarded video prepared。prepared : data=true。Note：This method is only called once IsMediaPrepared(),this callback will be initiated

Sample:

#region MediaAd Callback
	// bonus callback method of rewarded video 
    public void onMediaIncentived(string data)
    { 
       ZplayLogger.Log("onMediaIncentived:" + data);
	}
	// callback method of rewarded video show completed
    public void onMediaExposure(string data)
    { 
       ZplayLogger.Log("onMediaExposure:" + data);
	}
	// callback method of rewarded video close event
    public void onMediaClosed(string data)
    { 
       ZplayLogger.Log("onMediaClosed:" + data);
	}
	// callback method of rewarded video click event
    public void onMediaClicked (string data)
    { 
       ZplayLogger.Log("onMediaClicked:" + data);
	}
	// callback method of Prepared
    public void onIsMediaPrepared (string data)
    { 
        ZplayLogger.LogError("yumiMobi SDK Media Is Prepared :" + data);
		if (Convert.ToBoolean(data))
		{
			//Video requests success., stop run IsMediaPrepared
	     	ZplayYUMIHelper.Instance.GetRotaIsMediaPrepared = true;
		}
	}
#endregion