IOS Certificate Issue - latest version 9.5.3

Hi,
I’m now running 9.5.3

So I’ve had to update my annual .p12 and .mobileprovision for IOS Distribution and I’ve followed the back and forth steps and successfully done that.

I’ve then named the new .p12 and .mobileprovision files and stuck them in the project certificates folder.

I then went into my project and pointed the ios distribution p12 and mobileprovision files to these new files.

I noticed that in the project explorer box the system did not include the certificates\ folder prefix as it used to…

So i tried a variety of things but continually was getting : -

2026-09-14 05:01:33,426 - VoltBuilder run started at 2026-09-14 05:01:33.426729
2026-09-14 05:01:33,427 - Plan: Pro
2026-09-14 05:01:33,427 - Preflight Check
2026-09-14 05:01:33,427 - iOS Distribution .p12 not found. Put it in your certificates folder.
iOS Distribution mobileprovision not found. Put it in your certificates folder.
2026-09-14 05:01:33,427 - Build failed 76abf2cd-9206-4e51-b60c-64d8d43f2d19
2026-09-14 05:01:34,407 - Output:
2026-09-14 05:01:34,410 - Uploading voltbuilder.log…

I tried editing voltbuilder.json, tried copying the certs to various other folders.. but no luck..

In the end, i opened the previous version of AppStudio on my other PC and set that up as above - this time on 9.5.1

When i pointed the 2 project explorer fields to the 2 files above, this time the Project Explorer DID point to cerficates\###filename###

and hey presto… the voltbuilder worked perfectly.

The weird thing is, the new version worked fine for ‘continual use’ from the upgrade until now. It’s only since i added in new certs that this issue arose (this morning).

Let me know what you find!
Thanks,

Neil

As an interesting extra:-

I decided to copy the file form my “9.5.1 backup PC” to my Dev 9.5.3 PC and it then did build fine to an ipa file.

I guess this means that the correct folder is stored somewhere in the project once built and the bug relates to when you try to ‘relink’ to the certs on 9.5.3

N

There’s an inconsistency in the file picker library we use. You did the right thing with your workaround.