Anyone have any suggestions on how to implement this workaround within Unity Cloud Build?

@Moriarty83 You have to move BuildProcessors script into the Editor folder

A huge thanks to the people figuring out this workaround. Waldgeist, I'm getting some namespace build errors when I try to implement the workaround:

Assets/Scripts/Classes/iOS_14_2_Workaround.cs(10,36): error CS0246: The type or namespace name 'IPostprocessBuildWithReport' could not be found (are you missing a using directive or an assembly reference?)

Same error for:
using UnityEditor.Build;
using UnityEditor.Build.Reporting;
using UnityEditor.iOS.Xcode;

Are you able to give me a pointer or two on how to successfully implement? Huge thank you to all!

About the info.plist file is the same for 2019.4.5 app and 2019.4.14 app, so the problem don't come from this.

I'm working in google cardboard project and unity videoplayer. Using unity 2019.4.5 the videoplayer crashes randomly, and to solve this we updated to 2019.4.14. The videoplayer crashes it's solved but when we launch the app to the store, they rejected the validation and they asked to us to modify the info.plist file because can not install in Iphone XR/ Ipad 3r Gen.
They finally accept the app but when we download the app from store, in the splash screen show a black screen and the app don't continue.
In the testflight and xcode works, the problem is in the store.
Our problem it can be caused with this?

Reproduced on Unity 2019.4.9f1 / Xcode 12.1 / iOS 13.7
The solution works!

It works. You save my day. Thanks!

The workaround works, thanks Binouze! Fun fact: I mentioned that this is a hotfix for iOS 14.2 when re-submitting the app to the app store. It took less than 5 minutes (!) until they took it under review. I guess you are right, MigrantP!

For all of you who struggle with the script because they are not so familiar with the Unity Build API, here's a version that contains all required Using directives and also the missing callback order:

```cs

using System.IO;
using UnityEngine;
using UnityEditor;
using UnityEditor.Build;
using UnityEditor.Build.Reporting;
using UnityEditor.iOS.Xcode;

public class iOS_14_2_Workaround : IPostprocessBuildWithReport
{

public int callbackOrder => 1;

public void OnPostprocessBuild( BuildReport report ) {
#if UNITY_IOS
if( report.summary.platform == BuildTarget.iOS ) {
Debug.Log("Applying iOS 14.2 workaround. Remove me once Unity has patched this.");
var pathToBuiltProject = report.summary.outputPath;
var projectPath = PBXProject.GetPBXProjectPath(pathToBuiltProject);
var project = new PBXProject();
project.ReadFromString(File.ReadAllText(projectPath));
project.AddFrameworkToProject( project.GetUnityMainTargetGuid(), "UnityFramework.framework", false );
project.WriteToFile( projectPath );
}
#endif
}

}

```

We got our app update rejected by Apple today because of this! We haven't even been aware of this problem, since we didn't upgrade our devices to iOS 14.2 yet. With 14.1, they still worked fine. This is REALLY annoying. I am not even aware of any "3rd party plugins" involved here.

Thanks Binouze, that workaround has helped us get fixes out rapidly for our games that are built on Unity 2019.4.0.

I'm not sure if it's random, or if it's because our update notes mention fixing a crash due to iOS 14.2, but our first game's update was reviewed and approved in a matter of hours!