Rebuilding the XCode projects invalidates signing and provisioning

Every time I regenerate the Xcode project from the UProject (for instance when adding files) Unreal resets the signing, provisioning and bundle identifier to defaults.

Easy to reset but a bit of a gotcha to a nOOb iphone programmer (me last week, this week I’m a grizzled grey beard).

Howdy theonecalledtom,

Thank you for reporting this issue. I am going to need a bit more information before i begin digging into this issue. What version of UE4 are you currently using and would that version be a Binary build of the engine or a source build? Also, Would you be able to provide a couple of steps on how I may be able to reproduce this issue internally?

Any additional information would be greatly appreciated.

Thanks and have a great day!

Hey theonecalledtom,

Just wanted to check in with you and see if this issue has still been occurring with the signing and provisioning being invalidated. Please be sure to let me know so that I may take the proper approach with this report.

Thanks!

Sorry - meant to update.

It does invalidate the xcode signing and certificate settings but that doesn’t seem to matter, so it must be building from xcode using the ones stored in the uproject. Apologies for any confusion - it took some trial and error to get running on iphone and I’d ended up thinking the xcode settings actually mattered.

Also the last time I rebuilt xcode it didn’t seem to invalidate the Bundle name and ID as I feel like it did before - though now I can believe these don’t matter either.

I’m a bit confused about sharing the uproject with other developers. If my developer signature and signing certificate is baked into the project file how to they setup their own without invalidating my settings?

One small side issue is that when I add a new file though xcode it adds a copyright header with epicgames as the holder. I couldn’t see where the setting to control this is.

I guess this issue can be closed!

Thanks for checking back in :slight_smile:

Hey theonecalledtom,

Thank you for the update. If you happen to see this issue cause any problems for you in the future, please feel free to reopen this issue so I can further investigate.

Have a great day!