Code Sign error: No matching provisioning profiles found:

I’ve loved UE4 right untill its come to testing on a device… now i seriously hate it :frowning: hopefully someone can help me with this.

I’ve created my cert and imported on the mac, ive added the game.mobileprovison file to game/build/ios

when i come to launch the game, i get : LogPlayLevel:Display: mono: Code Sign error: No matching provisioning profiles found: No provisioning profiles with a valid signing identity (i.e. certificate and private key pair) were found.

As there is no actual documentation(that i’ve seen) i’g guessing ive done the right things with regards to adding the files.

my question is where SHOULD they be for the game to see them and continue with the launch?

this is with me opening my project from within the game folder, as i dont know how to push a specific project/game within xcode.

thanks.

C

I’m having the same issue =(

Hi,

Sorry for the delay in response. One thing that is missing in 4.2 and 4.3 is a UI to specify the Bundle Identifier for the game (btw, I just rectified that issue and 4.4 will have it). To do that in previous versions, you will need to go to the editor and open the Project Settings, click on the iOS section, and then click Create PList button. Once you have that Plist, click the open Plist folder button and then edit the plist. Find the CFBundleIdentifier key and change it from com.epicgames.{BUNDLE_IDENTIFIER} to com.yourcompany.mygame where your company and my game match the identifier you used to create the mobile provision. That should get you past this problem.

-Pete

Hello,

Thank you for your report. We were not able to investigate this on the engine version you reported, but there have been many version changes to UE4 since this question was first posted. With a new version of the Engine comes new fixes and it is possible that this issue has changed or may no longer occur. Due to timetable of when this issue was first posted, we are marking this post as resolved for tracking purposes. If you are still experiencing the issue you reported in the current engine version, then please respond to this message with additional information and we will investigate as soon as possible. If you are experiencing a similar, but different issue at this time, could you please submit a new report for it.

Thank you.