[BUG] Selecting "For Distribution" in Packaging Settings doesn't change BuildConfiguration flag in DefaultGame.ini

This issue occurs In the 4.18 binary version of the Editor on macOS. I was able to replicate it in a Blank project.

Steps to replicate:

  1. Create Blank project
  2. Open Project Settings
  3. Open the DefaultGame.ini file (to verify values being added and changed in file)
  4. In Packaging section of Project Settings, select Development as Build Configuration (this will write the “BuildConfiguration” value to the DefaultGame.ini file)
  5. Check the “For Distribution” check box (this will add the “ForDistribution” value to the DefaultGame.ini file, and change the Build Configuration Dropdown menu in Project Settings; however, it does not change the “BuildConfiguation” value in DefaultGame.ini

Expected outcome:

Checking “For Distribution” will change the Build Configuration dropdown in Project Settings to Shipping, and will also change the “ForDistribution” value in DefaultGame.ini.

Actual outcome:

DefaultGame.ini file’s “BuildConfiguration” value is not updated properly, and gets out of sync with what is displayed in Packaging section of Project Settings. This causes problems such as an iOS binary being rejected from the App Store for missing an Asset Catalog.

Workaround:

In Project settings, with the “For Distribution” checkbox unchecked, select “Shipping” as the Build Configuration (which will write the appropriate value to DefaultGame.ini). Then check the “For Distribution” checkbox. Alternately, you can manually adjust the “BuildConfiguration” value in DefaultGame.ini to “PPBC_Shipping”.

I use remote build, and the distribution is set to true, but still select the developer certification and ios provisioning file.

I look at the iPhnePackage code, there’s some bug on build distribution,
the source:Engine/Source/Programs/IOS/iPhonePackager/MobileProvisionUtilities.cs 192 line,
the distribution flag not set!!!, I can rebuild iPhonePackage to make it work.

but this is a really serious bug!!!
it should be fix quickly, I guess only few people use 4.18 for ios develop, so almost no body report this.

Two separate issues here.

First feiwu - the IPP problem is a known issue getting looked at for 4.19. It uses the developer certificate during the remote compile and then the distribution during the final IPA sign on the PC.

Second - this is first time i have heard of this one. I’ll see if we can reproduce it and get a jira put in.

-Pete

Hello JonathanADaley,

A member of our Engine QA staff has reproduced the issue you reported and has entered a bug report for the problem. You can find that report here: UE-52845

As the issue is now reported (and the issue feiwu mentioned is known), I’ll be marking this as resolved, however Ravlek may have some further questions to assist with looking into these issues.

Have a nice day!

Thanks for the update!

Ah, I forgot to add. For future bug reports such as this, despite the subject matter (such as this being related to Packaging), please post them in the Bug Reports section of Answerhub.

Will do. Thanks for the clarification.