Upgrade Guide

This section describes the required actions you may need to take when upgrading to a certain version of Easy Mobile. Please visit this place before upgrading Easy Mobile to avoid unwanted issues.

  • The steps described for a particular version apply when you upgrade from an older version to that version or a newer one.
  • Versions not listed here don't require any special upgrade steps.

Upgrading to version 2.12.0

To ensure a smooth upgrade from an older version to 2.12.0, please follow these instructions:

  • Backup your project.
  • Remove folders Editor and Scripts under the Assets/EasyMobile folder.
  • Import the new package.

Also, in this version we added a new param named 'failureReason' to the InAppPurchasing.PurchaseFailed event. Therefore please update your corresponding event handler if any with this new param. See the example code in chapter In-App Purchasing.


Upgrading to version 2.8.1

In version 2.8.1 we renamed the native Android library folder from "EasyMobile" to "EasyMobile.androidlib" to comply with Unity 2020 requirements. If you're upgrading from an older version to 2.8.1, follow the steps below to avoid build errors on Android platform:

  • Backup your project.
  • Remove folder Assets/Plugins/Android/EasyMobile (the new one will be generated later)
  • Import the new package.

Upgrading to version 2.5.0

To ensure a smooth upgrade from an older version to 2.5.0, please follow these instructions:

  • Backup your project.
  • Remove everything under the Assets/EasyMobile folder except two folders Generated and Resources.
  • Import the new package.

Upgrading to version 2.4.1

This version updated the setup process for AdMob to leverage the new settings UI of the Google Mobile Ads Unity plugin, which was introduced in its version 3.18.0. As a result, this version is no longer compatible with Google Mobile Ads versions older than 3.18.0. If you're upgrading to Easy Mobile Pro 2.4.1, make sure to upgrade the Google Mobile Ads plugin to version 3.18.0 or newer, if applicable.


Upgrading to version 2.3.2

If you're upgrading to version 2.3.2 or newer from an older version, remove the following folders before importing the new package:

  • Assets/EasyMobile/Plugins/iOS
  • Assets/EasyMobile/Scripts/Native/iOS

Upgrading to version 2.3.0

To ensure a smooth upgrade from an older version to 2.3.0 or newer, please follow these instructions:

  • Before importing the new package, remove everything under the Assets/EasyMobile folder except two folders Generated and Resources.
  • After importing the new package, and if you're targeting Android, use menu Assets > Play Services Resolver > Force Resolve to update the native Android library.

Upgrading to version 2.2.0

  • If you're upgrading to version 2.2.0 from Easy Mobile Pro 2 (version 2.0.0 to 2.1.3), remove two folder Assets/EasyMobile/Demo and Assets/EasyMobile/Scripts before importing the new package.
  • If you're upgrading to version 2.2.0 from Easy Mobile Pro 1 (version 1.0.0 to 1.3.0), follow the same instructions for upgrading to Unity 2.0.0.

Upgrading to version 2.1.1

  • This version is compatible with the ironSource Unity SDK version 6.7.12 which unfortunately, makes it incompatible with older versions of the ironSource SDK. If you upgrade to this version of Easy Mobile, make sure you also upgrade the ironSource SDK in your project (if any) to version 6.7.12 or newer.

Upgrading to version 2.0.0

  • Version 2.0.0 is a major update which introduces lots of changes and improvements. To make the product better, we had to make some necessary changes that break backward compatibility. Therefore we recommend a clean upgrade if you are moving from an older version to Easy Mobile Basic 2.0.0 or newer. That means you should remove the Assets/EasyMobile folder completely before importing the new version and setup the plugin again (re-apply previous settings in the Settings UI).
  • Version 2.0.0 also removes the longtime EasyMobile prefab. Now you no longer have to add it to the first scene of your app. Instead you would call the RuntimeManager.Init method (see Using Easy Mobile > Initializing).

Upgrading to version 1.2.0

Version 1.2.0 is a major update in which Easy Mobile has been renamed to Easy Mobile Pro and lots of improvements and modifications were introduced, most notably API changes. If you're upgrading from an older version to 1.2.0, we strongly recommend removing the old version completely before importing the new one to avoid potential issues. Please follow these steps:

  • Backup the Assets/EasyMobile/Resources and Assets/EasyMobile/Generated folders and save them somewhere safe.
  • Remove the whole Assets/EasyMobile folder.
  • Remove the file/folder named com.sglib.easymobile.easy-mobile-1.0.2 in folder Assets/Plugins/Android.
  • Import Easy Mobile Pro 1.2.0.
  • Copy the backed up Resources and Generated folders back to Assets/EasyMobile folders.
  • Go to menu Assets > Play Services Resolver > Android Resolver > Force Resolve.
  • If you're using Game Services module on Android, run Setup Google Play Games once again in the settings UI.
  • Optionally update your scripts to fix warnings due to old classes being deprecated (they still function normally, we're just introducing new classes with different names to make the API more intuitive).

Upgrading to version 1.1.5 or newer

Since version 1.1.5, Easy Mobile incorporates the Google Play Services Resolver for Unity plugin for Android dependencies management, as well as moves all native code into the Assets/EasyMobile/Plugins folder. If you're upgrading from an older version to version 1.1.5 or newer, please remove the following files before importing the new package to avoid potential issues:

  • Assets/Plugins/Android/easy-mobile.aar.
  • Assets/Plugins/Android/libs/armeabi-v7a/libeasymobile.so
  • Assets/Plugins/Android/libs/x86/libeasymobile.so
  • Assets/Plugins/iOS/libEasyMobile.a

Upgrading to version 1.1.4a or newer

Since version 1.14.0, the UnityIAP package has made changes to its API that cause some conflicts with Easy Mobile editor scripts. We addressed this problem in version 1.1.4a. If you're upgrading from an older version to 1.1.4a, and your project uses the In-App Purchasing module, you need to upgrade (re-import) the UnityIAP package to version 1.14.0 or newer to avoid incompatibility issues.


Upgrading to version 1.1.0 or newer

If you're upgrading from an older version to version 1.1.0 or newer, you'll need to:

  • Remove the EasyMobile/Demo folder
  • Remove the EasyMobile/Script folder
  • Import the new version

results matching ""

    No results matching ""