Skip to main content
Playtolia ships as a Unity Package Manager (UPM) package named com.playtolia.sdk. It wraps a cross-platform native library (Android + iOS) and exposes C# APIs. Once the package resolves, it manages its native dependencies and platform configuration for you. There are three supported ways to install it — pick whichever fits your workflow:
  • Scoped registry — the recommended path. Add Playtolia’s registry once and the package behaves like any built-in one: browse it in the Package Manager, install by name, and get a one-click Update button when new versions ship.
  • Git URL — pull a tagged version straight from the distribution repository. No registry setup, but updates are a manual tag bump (no Update button).
  • Tarball (.tgz) — a self-contained archive you download once. Good for offline or air-gapped machines, or when you want the exact bytes checked into your own storage.
All three install the same package into your project’s Packages/ folder, so you can switch between them later without touching your game code.

Requirements

  • Unity 6000.0 or later (developed and tested against 6000.0.32f1)
  • iOS builds: Xcode and CocoaPods; deployment target 13.0+
  • Android builds: Android SDK; min SDK 24 (Android 7.0)
Firebase is not required for the core SDK — auth, billing, social, and the rest work without it. You only need the Firebase Unity SDK (with Cloud Messaging) if you enable Push Notifications, which is off by default. See Push Notifications for that setup.

Install with the Package Manager

Open the Package Manager from Window ▸ Package Manager. Use the + button in the top-left corner to add a package by Git URL or from a tarball. For a tour of the window itself, see Unity’s Package Manager window and Install a package guides.

Native dependencies

The package pulls in its own platform dependencies — you don’t add them by hand:
  • Android — resolved from Maven Central by the External Dependency Manager for Unity (EDM4U). The package ships an Editor/SharedAndroidDependencies.xml pinned to the matching com.playtolia.sdk:core-android version, and EDM4U downloads it at build time. EDM4U is a transitive requirement; if your project doesn’t already have it, install com.google.external-dependency-manager alongside Playtolia.
  • iOS — the core.framework binary ships inside the package and is embedded into your Xcode project automatically by the included build post-processor.

Verify the install

The package ships a Smoke Test sample that runs a minimal initialization and native round-trip. In the Package Manager, select Playtolia SDK ▸ Samples ▸ Smoke Test ▸ Import, then open the imported scene/script to confirm the SDK loads and responds. This is the same check CI runs, so if it passes, your install is wired correctly.

Updating

  • Scoped registry — the smooth path: the Package Manager shows a version list and a one-click Update button whenever a newer version is published. Nothing to edit by hand.
Git-URL and tarball packages, by contrast, don’t show an Update button — that UI is only for packages from a registry. Unity pins the exact version you installed (in Packages/packages-lock.json), so you move to a new release yourself:
  • Git URL — bump the tag in Packages/manifest.json (e.g. #v1.4.0#v1.5.0). Since the URL changes, Unity re-resolves on the next window focus and updates the lock file. You can also just re-run + ▸ Add package from git URL… with the new tag. (No manual lock editing needed — that’s only required if you track a moving branch instead of a tag.)
  • Tarball — download the newer .tgz, remove the existing package from the Package Manager, and add the new archive.
The package version always matches the com.playtolia.sdk:core library version, so package X.Y.Z always pairs with core X.Y.Z.

Next step

Getting Started

Add the Playtolia GameObject, configure your Game ID, and build for iOS and Android.