We are currently setting up dedicated iOS devices for our warehouse staff to test an internal inventory workflow with JTL-WMS, but we are running into recurrent certificate and deployment issues. Every time we try to push our modified staging build to unmanaged iPads, the operating system flags an untrusted enterprise developer alert and refuses to install the payload.
To work around local Xcode configuration limits, we attempted packaging the test IPA through a third-party signing tool, but the modified provisioning profile keeps failing signature verification after a few hours of warehouse use. This either results in an immediate crash upon opening the inventory scanner or an error stating the application integrity could not be verified.
Has anyone encountered similar profile rejection issues when distributing custom iOS builds for JTL integrations, and what is the recommended way to keep these test builds active without them getting revoked mid-shift?
To work around local Xcode configuration limits, we attempted packaging the test IPA through a third-party signing tool, but the modified provisioning profile keeps failing signature verification after a few hours of warehouse use. This either results in an immediate crash upon opening the inventory scanner or an error stating the application integrity could not be verified.
Has anyone encountered similar profile rejection issues when distributing custom iOS builds for JTL integrations, and what is the recommended way to keep these test builds active without them getting revoked mid-shift?