[dabbelju]

Hi all,

as every year, my iOS certificates have been about to expire and I did generate new ones and did that with the same request.csr as allways. Afterwards I did update my development profile in order to use the new certificate. When I change in Mobieone build process to the new certificate and the new profisioning profle it tells me: Could not parse certificate: java.io.IOException: Unsupported encoding. When I switch back to the old pair of certificate and profile, it is fine.

MobiOne Version 2.6.2.

Am I doing something wrong?

Thanks and best regards
Dabbelju

UPDATE:
I did the whole process again, as described here. Still the same result.

[support-michael]

@dabbelju

Thx for this report. Yesterday I ran into the exact same problem after I regenerated my certs & profiles. I opened a bug and our dev team tracked the problem down to minor format change. A fix was checked in and we will make a hot-fix update available later today once we have completed QA’ing the fix. We will update this thread and make an ANN as soon as the update is available.

[dabbelju]

Hi michael,

Good news. Thanks a lot in advance.

Dabbelju

[support-michael]

@dabbelju

Would you please try this pre-release of the next MobiOne version 2.6.3?
https://drive.google.com/file/d/0B2UbQ9Htq1UWT2czbnlDQVUxdzQ/edit?usp=sharing

If you give it a try please let me know how it works when building ios apps. A key set of changes were made to the digital signing page of the iOS build wizard. Some format changes were recently introduced by Apple to the provision profile that resulted in the build wizard erroring out.

[dabbelju]

Hi micahel,

thanks a lot – works for me. I did test it with the new pair of certification and profile as well as with the old pair. Both works.

Thanks a lot for the fast and perfect support!

Dabbelju

[Author]

Posts