-
Go to the Build Settings window and make sure your Unity project is set to iOS. Once set, the
AppchargeConfigfile updates to display iOS-specific configuration options.
-
Your configuration settings should look like this:
By default, the configuration file is preconfigured for integration. However, you must set the required Environment and Checkout Public Key fields under Publisher Info.Publisher Info
These settings can also be changed at runtime, but doing so requires re-initializing the SDK.Configuration Settings
Integration Settings
Enables automatic integration of required iOS frameworks, entitlements, and URL schemes during the Xcode build process.Enable iOS Framework Integration
By default, the SDK configures Swift libraries, runpaths, signing, and adds the Appcharge XCFramework during the Xcode build. Use the options below to skip parts of that setup if you manage them yourself.Enable iOS Entitlements Integration
By default, the SDK creates or updates the entitlements file and associated domains during the Xcode build. Use the options below to skip parts of that setup if you manage them yourself.Enable iOS URL Scheme Integration
By default, the SDK adds the Appcharge URL scheme entries toInfo.plistduring the Xcode build. Use the options below to skip parts of that setup if you manage them yourself.
Fix deeplinks on affected Unity versions
Some Unity versions add aUIApplicationSceneManifest key to Info.plist. This prevents Application.deepLinkActivated, which the Payment Links SDK uses to return players to the game after checkout.
Known affected Unity versions:
2022.3.75f16000.0.68f16000.0.69f16000.3.10f16000.4.0b116000.5.0a76000.6.0a1
Info.plist in the generated Xcode project and remove the UIApplicationSceneManifest key and its contents. Unity regenerates Info.plist on each build, so repeat this workaround after every iOS build.
Unity
6000.3.78f1 or later includes the official fix. You can upgrade instead of applying the Info.plist workaround. Test the upgrade thoroughly before releasing.