ExitCode 128 on IOS Install package
- This topic has 27 replies, 3 voices, and was last updated 5 years, 9 months ago by
MICHEL BELANGER.
- You must be logged in to reply to this topic.
Home › Forums › Ask Expert › ExitCode 128 on IOS Install package
I followed the instructions to install my application on an iOS, but it does not work … here is the error:
Cannot perform operation: Process ideviceinstaller.exe return ExitCode 128
It work with same setup with other automation tools
Can tell me what’s wrong ?
Hello Michel.
Have you finally got the provision/certificate for iOS device? So you are trying to install initial application there and getting this error?
Thanks.
Kirill,
ZAPTEST Team.
yess exacly 🙂
I fight hard to have the IOS certificate and I have it now 😉
But unfortunately its not working with Zaptest. On the other hand I can see the Zapbrowser (not usyfull for our testing ;))
Any advices!?
Hello Michel!
What’s the current version of ZAPTEST do you use? And do you have a developer certificate?
As I understood you can install ZAP browser and use it with this cert, right?
Could you then provide the package which you are installing on the device? If not – I need the structure of the package to understand which extensions do you use (in the application). iPhone could block installation for different reasons. Let me know what is the best option for you.
Thank you,
ZAPTEST Team
version 19.3.20
yes I have the certificate and I know it work, but not with Zaptest
ios 12.3, iphone 8plus
Hello Michel!
Let’s do step by step. Could you try to install ZAPTEST Browser (browser icon in “Device Manager”) with your certificate? Does it work?
Thank you,
ZAPTEST Team
nop 🙁 not working
Hello Michel!
Ok, let’s check your provision (it should belong to a developer certificate):
Could you open your “[NAME].mobileprovision” file, in any editor (ASCII code) and try to find the following string: “get-task-allow”. After this string you should have “
What’s your result?
Thank you,
ZAPTEST Team
here the result…
Hello Michel!
It seems, your configuration is correct. We are working on adding support for iOS 12.3 and let you know next instructions on how to automate your device!
Thank you,
ZAPTEST Team
Hello Michel!
To add support for iOS 12.3 you should open the ZAPTEST installation path: “C:Program Files (x86)ZAP-fiXStandaloneimages” and copy the folder “12.2” -> “12.3”. This update will be avaiable in the next public build.
Then, could you restart your device and try again.
Installation path could be different. In this post, we use default paths.
Thank you,
ZAPTEST Team
copy the folder “12.2” -> “12.3”… done !
but still not work
Hello Michel!
Somehow this certificate is invalid (or doesn’t belong to this device). Could you generate a new dev certificate for your device (on apple website)? (you should use a provision file which contains your device UDID).
Thank you,
ZAPTEST Team
but I can take a screenshot 🙂 we are closer
Already have an account? Login
Check you SPAM folder if you do not see the email.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |