type MobileApplicationError (v202411)
Stay organized with collections
Save and categorize content based on your preferences.
AI-generated Key Takeaways
The Mobile Application Service page lists various errors related to Mobile Application objects.
Errors are inherited from ApiError and include fields such as fieldPath, trigger, and errorString.
The MobileApplicationError includes a reason field with various enumeration values explaining specific issues like invalid app IDs, internal errors, or invalid store settings.
This page details different types of errors that can occur when interacting with MobileApplication objects within the API.
A parsed copy of the field path. For example, the field path "operations[1].operand"
corresponds to this list: {FieldPathElement(field = "operations", index = 1),
FieldPathElement(field = "operand", index = null)}.
trigger
xsd:string
The data that caused the error.
errorString
xsd:string
A simple string representation of the error and reason.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-06 UTC."],[],["The `MobileApplicationService` details errors that can occur with `MobileApplication` objects. These errors, extending from `ApiError`, include issues like invalid app IDs, exchange partner settings, and exceeding active app limits. It defines various reasons for `MobileApplicationError`, such as `INVALID_APP_ID`, `NAME_OR_STORE_ID_MUST_BE_SET`, or `PUBLISHER_HAS_TOO_MANY_ACTIVE_APPS`. Additionally, there are specific errors related to app store IDs, such as invalid formats, missing entries, and non-unique IDs within the same platform.\n"]]