From time to time, we at Katalon Product Support team often receive questions from our users regarding iOS issues and error code, with each new error code taking us quite a bit of time to research for the appropriate solutions.
Hence, in this thread, we will be compiling some of the most common iOS error codes, what they mean, their root causes, and their corresponding solutions.
Each error code will be presented in a separated post in this thread, which you can navigate to using the link below:
The iOS error codes covered in this thread include:
The Webdriver Agent is not signed correctly because it was not built under a valid Apple Developer Account. It was noted in our document that you have to enroll in the Apple Developer Program. See Enrollment.
The Webdriver Agent or the application file (.ipa for real device and .app for simulator devices) was built with the wrong IOS version of the devices.
For example: The devices chosen were iPhone 13 Promax, IOS 16.1. But the Webdriver Agent was build for IOS 12 → It cannot load the Webdriver Agents on the devices to run the application
We can test to see if the WebDriver Agent (WDA) is built successfully by recording an existing application on the device like ‘com.apple.MobileAddressBook’. If the application is loaded successfully on the device then we are successfully build the WDA
Every Xcode version will have an IOS version supported. For example, Xcode 14.2 will support maximum IOS 16.2 and Xcode 14.3 will support maximum IOS 16.4 (including 16.3),…etc.
You need to make sure to download the correct Xcode version to build the Webdriver Agent that supports the IOS version of the device. Otherwise, you will build the wrong IOS version of the Webdriver Agent.
Unable to start application on this device. An unknown server-side error occurred while processing the command. Error occurred while starting app. Original error ‘com.xxxx.MainActivity’ never started’
Exception usually indicates, that the first application activity is not the same package/activity, as it is set (or auto detected) by appWaitPackage /appWaitActivity . Such error normally happens in applications having multiple activities.
By default, Appium tries to start the appPackage /appActivity combination and then waits until the appWaitPackage /appWaitActivity is focused. But the appWaitDuration got timeout expires.
In your Project → Settings → Execution → Default → Mobile → Android/IOS
Add new entries for appWaitActivity and appWaitDuration.
Identifier com.facebook.IntegrationApp cannot be registered to your development team
Xcode couldn’t find any iOS App Development provisioning profiles matching com.facebook.IntegrationApp.
The Identifier com.facebook.IntegrationApp is not available. because your team is probably not Facebook, you can’t sign an app with a bundle identifier of com.facebook. Change your bundle identifier to a unique string.
The iOS App Development provisioning profiles is not correct. It must be an Apple Developer account instead of personal account.
First make sure to select the correct Apple Developer Account. If you don’t have an Apple Developer signing certificate, you’ll have to sign up for one at developer.apple.com or ask someone in your company to set you up with one.
Change com.facebook.Integration to something with your company’s ID, like com.mycompany.Integration.
/Users/Joshua/Downloads/adiraku.ipa did not have any matching .app or .ipa bundles. Please make sure the provided package is valid and contains at least one matching application bundle which is not nested
The error indicates that Katalon Studio could not find any matching .app or .ipa bundle within the provided ipa package.
Root cause & solution
Incorrect used file:
.app is used for simulators
.ipa is used for real devices
Make sure that the application file installed in the device is the same as in Katalon (one source)
If they want to install it in KS, please uninstall in from the device first.