getting "The certificate was not created with the Certificate Signing Request" after importing an existing project.

[New_Japan_A_]

Hello to everyone.

ok, this is an odd issue, that i'm surprised is giving problems.

i have a project, and for monhs i've been able to compile and publish successfully without problems, the machine had win7U 64bits, today i had to upgrade the main computer with a new SSD drive, with win10 on it.

installed XDK (2496), imported the project, no problems there, upgraded the project, no problems, but when i was wishing to build a test build, i found a red message saying "The certificate has not been uploaded.", so i browse for the existing certificate, (wich is the original from apple when we used the w7 OS, from april to yesterday) and now i'm getting "The certificate was not created with the Certificate Signing Request.".

this is conflictive, first is the pushwoosh service, since re-doing all the certification process will most likely invalidate the existing one, pushwoosh will get messed up, and that's a problem i cannot face right now.

is there any way to get this same build using the same working certs without having to re-do ALL the exhausting process? (not counting the pushwoosh manual process, ughh, i don't own a physical mac)

i mean, the need to re-do something that already exist is pointless and only bring trouble, is there anything that changes from XDK installation to another XDK installation? even if it's the same machine just a different OS?

thanks in advance.

[John_H_Intel2]

I frequently switch between multiple computers doing iOS builds, so that should not be the issue.

Have you already uploaded a new iOS certificate to the build system? I hope not. If you have, then you will need to continue from the beginning. 

If you have not altered your certificate in the cloud, then you should be able to generate(renew) your provisioning profile, making sure to pick the correct certificate. Then give that to the XDK, upload and build.