Version: Unity 6.1 Alpha (6000.1)
Language : English
UDP SDK data collection
Glossary

UDP troubleshooting

Important
The Unity Distribution Portal (UDP) is shutting down on February 17th, 2025. Access to the UDP Web console and services will be permanently deactivated on this date. To download your keystores and instructions on how to republish your games directly to app stores, visit the UDP overview page. If you have any questions about your account, submit a ticket with Unity Customer Support.

Incorrect UDP implementation

An incorrect implementation of UDP in your game client could prevent users from purchasing IAP products. Typical symptoms of such a problem in your game include:

  • The wallet doesn’t appear when invoked

  • In-app purchases are unresponsive If these symptoms occur in your generic UDP build, resolve them before you repack your game.

No IAPs are displayed in the UDP console

Make sure you push your IAP Catalog information in the Editor.

Error: Packing Failed: No UDP SDK detected

This can happen with an implementation via Unity IAPAbbreviation of Unity In App Purchase
See in Glossary
, if you forget to set UDP as the build target.

It can also happen if you use the Minify option while building your APKThe Android Package format output by Unity. An APK is automatically deployed to your device when you select File > Build & Run. More info
See in Glossary
; UDP may not be able to find files/directories that it needs because of it. Keep UDP-related packages in a customized proguard file (or disable Minify option) and rebuild your game.

UDP Sandbox: login screen doesn’t appear

The login screen in the Sandbox can fail to appear if the Init() method has not been implemented properly. The login screen is displayed when Init() is called. Init() is successful only when the login is successful. Unity recommends to implement Init() when your game launches.

UDP SDK data collection
Glossary