Application Management
An Application is a platform configuration inside a Project. A Project can have at most one active iOS Application and one active Android Application. Creating another active record for the same Project/platform returns a conflict.
Manage Applications
Open Applications in the Project workspace to create, edit, or delete records. In a blocked Organization, the create form is hidden and Edit and Delete are disabled; existing Applications remain readable. An Application that is referenced by an active Link cannot be deleted until the reference is removed.
Use the public Project UUID—not an Organization API credential—when initializing a client SDK. Organization API credentials belong only on trusted servers.
iOS Fields
| Field | Purpose |
|---|---|
| App name | Identifies the Application in LimeLink |
| App Store ID | Identifies the App Store listing |
| App scheme | URI scheme used by app-routing options |
| Bundle ID | Identifies the iOS app |
Android Fields
| Field | Purpose |
|---|---|
| App name | Identifies the Application in LimeLink |
| App scheme | URI scheme used by app-routing options |
| Package name | Identifies the Android app |
| SHA-256 fingerprint | Supports verified Android app configuration |
When an Application is loaded, nullable platform fields appear as empty inputs. On save, LimeLink trims optional text and omits blank values. The non-selected platform object is sent as null, so changing Platform clears the previous platform details. Follow the current platform SDK guide for platform requirements.
Use an Application in a Link
In the Link editor:
- Open app under Apple options selects an iOS Application.
- Open app under Android options selects an Android Application.
- Open browser does not require an Application selection.
Existing Web Application records remain a compatibility type and may be editable, but the current new-Application flow offers iOS and Android.
Verify the Configuration
- For iOS, verify the Bundle ID, app scheme, store ID, and Associated Domains against the iOS SDK guide.
- For Android, verify the package name, SHA-256 fingerprint, app scheme, manifest, and App Links association against the Android SDK guide.
- Create a test Link with Open app and confirm the installed and not-installed paths. A platform association or metadata mismatch can cause the browser/store fallback instead of app routing.