2019.3 - validation on upload to store gives "UnityFramework.framework contains disallowed file"

App runs on phone normally.
When trying to validate the app before uploading it to the store, this comes out:

Invalid Bundle. The bundle at 'my.app/Frameworks/UnityFramework.framework' contains disallowed file 'Frameworks'

Unity 2019.3 Xcode 10.2

Help?

 

@Firewalker did you have any luck with this? I'm hitting the same issue.

 

I have the same problem with Unity 2019.3.0f3 and Xcode 11.3. When I try to validate the app in the App Store, it gives me this error:

App Store Connect Operation Error
Invalid Bundle. The bundle at 'my_app_name.app/Frameworks/UnityFramework.framework' contains disallowed file 'Frameworks'.

I could not find a solution yet.

 

Can any one of you post a detailed folder structure of that UnityFramework.framework bundle you have issues with?

This error message could mean that there is embedded frameworks inside UnityFramework.framework. This may be an umbrella framework situation which Apple discourages.

 

It only had a .h file and a .plist file. I supose it must be some configuration option the one that gives troubles.

But I managed to send the app using the previous version of Unity (2019.2).

 

The UnityFramework is only added in the 2019.3 builds. It seems to be a framework library that then holds all the usual frameworks have always been added to the main target.

This seems to have been a design decision for 2019.3 - but not one that Apple seems to agree with!

2019.2 build structure


2019.3 build structure

 

I'm hitting this too!

@Dover8 - did you find a solution without downgrading Unity?

 

Manually setting

Code (CSharp):

1. Always Embed Swift Standard Libraries: NO

setting as explained in Max MacLeod answer here got my bundle through validation. I've not run it on device yet to test the app works though:

https://stackoverflow.com/questions...dle-the-bundle-at-contains-disallowed-file-fr

 

'Always Embed Swift Standard Libraries' is defaulted to NO for each target in xcode for me. It was YES for you?

 

This seems to still be a problem with 2019.3.10f. Reverting to 2019.2. was the only solution

Im using Vuforia and Mapbox so maybe one of these libraries cause this in the first place.

 

Hello Thanks to all for info.

Solution: reverting from 2019.3 to 2019.2. worked for me.

 

I can confirm the same issue on 2019.03.12f1.

Unfortunately since I ceated my project in 2019.03 originally downgrading is a real mess....

 

Managed to get it working without downgrade using the solution posted by MultivariousDev01 here: https://forum.unity.com/threads/an-empty-folder-named-frameworks-in-unityframework-framework.751559/

"We go into the UnityFramework target of the main project in XCode, and delete the Build Phase called [CP] Embed Pods Frameworks."

 

Setting

Always Embed Swift Standard Libraries

To 'NO' for the main app, UnityFramework and app extension (in my case keyboard extension) fixed this issue for me. I did this in code via:

Code (CSharp):

1. pbxProject.SetBuildProperty(target, "ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES", "NO");

 

Where did you put this code ? Can it be used with Unity Cloud Build ?
Is the pre/post export method & pre/post build script area a place to look for ? I've never use it before, any guidance will be appreciated

 

See my post here https://forum.unity.com/threads/an-empty-folder-named-frameworks-in-unityframework-framework.751559/

Long story short:
Set "Always Embed Swift Standart Libraries" to YES for the Unity-iPhone target
Delete Framework folder inside your .xcodearchive (see picture)

 

You can use the following script to delete on each compilation the folder mentioned above.

Code (CSharp):

1. cd "${CONFIGURATION_BUILD_DIR}/${UNLOCALIZED_RESOURCES_FOLDER_PATH}/Frameworks/UnityFramework.framework/"
2. if [[ -d "Frameworks" ]]; then
3.     rm -fr Frameworks
4. fi

 

This is correct, it solved my problem.Thank you!

 

In my case it helped to move all dylibs from UnityFramework.framework/Frameworks to Frameworks root in archive after build. And delete UnityFramework.framework/Frameworks also there.

 

I suppose this script works for UCB builds, right?
Trying this one right now.

 

I said "Thank you" in the original thread but I feel like it's not sufficient so I will say "Thank you" here as well!

 

So, we are having this issue on our Unity 2020.1 Cloud Build that automatically tries to upload to the store.

We iterate upon our exported project directories and try to find (and delete) nested "Frameworks" files or directories in "*.framework" directories.

Turns out that there's no "UnityFramework.framework" at this moment on the directory.
Is that directory download or generated during XCode build?

How can we fix this on Unity Cloud Build builds?



This is our current Post-Export Method:

Code (CSharp):

1. public static void SearchInvalidFrameworksDirectoryAndDelete(string basePath)
2.         {
3.             Debug.LogFormat("[SearchInvalidFrameworksDirectoryAndDelete] Platform: {0}; Base Path: {1}",
4.                 Application.platform, basePath);
5.          
6.             string[] frameworkDirectories = Directory.GetDirectories(basePath, "*.framework", SearchOption.AllDirectories);
7.             for (int i = 0; i < frameworkDirectories.Length; i++)
8.             {
9.                 string unityFrameworkPath = frameworkDirectories[i];
10.              
11.                 Debug.LogFormat("[SearchInvalidFrameworksDirectoryAndDelete] Looking up for invalid \"Frameworks\" directory or file at path: {0}", unityFrameworkPath);
12.              
13.                 string[] nestedFrameworksDirectories = Directory.GetDirectories(unityFrameworkPath, "Frameworks", SearchOption.AllDirectories);
14.                 foreach (string nestedFrameworkDirectory in nestedFrameworksDirectories)
15.                 {
16.                     Debug.LogWarningFormat("[SearchInvalidFrameworksDirectoryAndDelete] Deleting DIRECTORY: {0}", nestedFrameworkDirectory);
17.                     Directory.Delete(nestedFrameworkDirectory, true);
18.                 }
19.  
20.                 string[] nestedFrameworksFiles = Directory.GetFiles(unityFrameworkPath, "Frameworks", SearchOption.AllDirectories);
21.                 foreach (string nestedFrameworksFile in nestedFrameworksFiles)
22.                 {
23.                     Debug.LogWarningFormat("[SearchInvalidFrameworksDirectoryAndDelete] Deleting FILE at path: {0}", nestedFrameworksFile);
24.                     File.Delete(nestedFrameworksFile);
25.                 }
26.             }
27.         }

 

How can I add UnityFramework.framework to Link Binary with Libraries?
Unity crashes because watchdog in iOS and adding it manual there prevents the crash

 

Also just encountered this issue

https://gyazo.com/1037c9c20403f092e4f954123ef8cc3b

 

https://developer.apple.com/forums/thread/654980 seems to work

 

This is still a bug on Unity 2021 beta 8

 

Found solution. Add script below to Editor folder.

Code (CSharp):

1. using System.IO;
2. using UnityEditor;
3. using UnityEditor.Callbacks;
4. using UnityEditor.iOS.Xcode;
5.  
6. namespace Editor
7. {
8.     public static class XcodeSwiftVersionPostProcess
9.     {
10.         [PostProcessBuild(999)]
11.         public static void OnPostProcessBuild(BuildTarget buildTarget, string path)
12.         {
13.             if (buildTarget == BuildTarget.iOS)
14.             {
15.                 ModifyFrameworks(path);
16.             }
17.         }
18.  
19.         private static void ModifyFrameworks(string path)
20.         {
21.             string projPath = PBXProject.GetPBXProjectPath(path);
22.            
23.             var project = new PBXProject();
24.             project.ReadFromFile(projPath);
25.  
26.             string mainTargetGuid = project.GetUnityMainTargetGuid();
27.            
28.             foreach (var targetGuid in new[] { mainTargetGuid, project.GetUnityFrameworkTargetGuid() })
29.             {
30.                 project.SetBuildProperty(targetGuid, "ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES", "NO");
31.             }
32.            
33.             project.SetBuildProperty(mainTargetGuid, "ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES", "YES");
34.  
35.             project.WriteToFile(projPath);
36.         }
37.     }
38. }
39.  

 

yeah but we shouldn´t have to do work arounds, by default we should be able to submit projects to the store

 

Yes, unbelievable that this is still active.

On Unity 2019.4.24f1 ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES is set to No for Unity-iPhone and UnityFramework. If you build like this your app will crash on some devices, just tested on Simulator, iPad Pro 9.7-inch, 10.3.1. and it crashes because it is missing Swift library. If you set ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES to Yes on Unity-iPhone your app will run just fine on any device.

On older Unity versions (2017) ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES was set to Yes and tehere were no problems, this change in 2019.3.0 where they introduced UnityFramework just made one big mess, don't forget https://forum.unity.com/threads/uni...tchdog-transgression-crash-0x8badf00d.878620/

 

This issue is still present, I'm getting it in 2020.2.4f1.

EDIT: Three days later, here's a blog post explaining what we ended up doing, with code for a post-export step that fixed it for us.

http://www.kittehface.com/2021/09/fixing-invalid-frameworks-folder-in-ios.html

 

Thanks a million! That worked! Don't know how, but it did -- can cloud build and it gets submitted to Appstore Connect correctly again!

 

What is the exact method name that you put in `Post-Export Method Name` in the Cloud Build config for iOS?

I'm getting the following error:
```
export method 'Editor.XcodeSwiftVersionPostProcess.OnPostProcessBuild' not found, aborting. Please make sure you are using the correct function signature.
```

 

I did not configure it at all in Cloud config/Advanced options, it's just in my project's "Editor" folder and named "XcodeSwiftVersionPostProcess.cs".

This is unrelated to this issue, but seeing your screenshot: you can configure a post build .bash script to push the build directly to AppStore connect.

 

So crazy this is still not fixed two years later... Thanks everyone for the workarounds.

 

Thank you , script is solved my problem.
Unity 2020.3.18f1 , Xcode :13.0

 

working thanks
unity 202.2.7f1
xcode 13

 

It very simple to fix. For some reason Unity switches "Always Embed Swift Standard Libraries".
No need to run any scripts or delete anything.

1. Set yes on Always Embed Swift Standard Libraries in target Unity-iPhone in Build Settings.
   
2. Set no on Always Embed Swift Standard Libraries in target UnityFramework in Build Settings.
   
3. Done

 

can you submit this bug please?

 

@PavelLU Why hasn't Unity fixed this issue? Why isn't this a priority?

I'd love to make a game without wasting so much time finding solutions to issues that shouldn't exist. Imagine how much better our games would be!

When Unity's core functionality fails and goes unfixed for so long it makes Unreal 5 look so inviting!

 

Oh, you haven't seen anything. I'm stuck in 2021.1.27 because after that version they introduced bugs that make most shaders look bad. Then in 2021.2 they introduced a bug that doesn't allow you to compile projects in Android Arm32. And in 2022.1 beta I can't even migrate projects.

All these are reported for months, even during alpha. And they went through beta and full release and still no fixes. Wonderful QA. The list of "known issues" will be larger than the release fixes notes soon. In fact they are for many releases. Awesome.

 

Trying to build and upload my game from cloud to appstore. ipa builds fine but if i try to upload it with altool i got that old error with
I tried this solutions first
https://forum.unity.com/threads/201...contains-disallowed-file.751112/#post-6959378
got a bunch of errors error: Invalid SWIFT_VERSION
I've added this script too
https://forum.unity.com/threads/201...contains-disallowed-file.751112/#post-7466480
But i keep getting error

Code (CSharp):

1. 18524: ▸ error: Invalid SWIFT_VERSION: Could not parse version component from: '1 5' (in target 'SwiftyXMLParser' from project 'Pods')

Any idea what to do next ?

 

I used the attached script and it solved my issues and successfully uploaded to TestFlight/AppStore.

I created it based on the solutions proposed in this post and this post.

It should also fix the issues mentioned by @astanid in this previous post.

It's also worth to mention that I set "Cocoapods Integration" on ExternalDependencyManager plugin to "Xcode Workspace", which might have influenced the solution to the problem or even fixed it. Either way, now that it's working I won't verify if that really makes any difference.

 

This works for me. Thanks so much!
I do something like this in my post process script:

Code (CSharp):

1.         private static void UpdateBuildSettings(string projectPath)
2.         {
3.             #if UNITY_IOS
4.                 util.log.Info(CLASS_TAG + "--> UpdateBuildSettings");
5.                 PBXProject project = new PBXProject();
6.                 project.ReadFromFile(projectPath);
7.                 string mainTargetId = project.GetUnityMainTargetGuid();
8.                 project.AddBuildProperty(mainTargetId, "OTHER_LDFLAGS", "-ObjC");
9.                 project.SetBuildProperty(mainTargetId, "CLANG_ENABLE_MODULES", "YES");
10.                 project.SetBuildProperty(mainTargetId, "GCC_ENABLE_OBJC_EXCEPTIONS", "YES");
11.                 project.SetBuildProperty(mainTargetId, "ENABLE_BITCODE", "NO");
12.                 project.SetBuildProperty(mainTargetId, "ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES", "YES");
13.                 string frameworkId = project.GetUnityFrameworkTargetGuid();
14.                 project.SetBuildProperty(frameworkId, "ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES", "NO");
15.                 File.WriteAllText(projectPath, project.WriteToString());
16.             #endif
17.         }

 

This fixed it for me. Thanks!

 

It worked for me months ago, now with Unity 2022.2.19, I saw the build was set like that by default, but the same issue appear when I upload the archive. Have any idea?

 

Thank you, @Melnikovv! That did it for me!

 

Thank you a lot, @Melnikovv! This fixed it for me!!!

 

@Melnikovv does your script only set the correct values in xCode for "Always embed switch standard libraries" or is anything else happening? Because I get complier errors when adding the script to Editor folder (screenshot).

I get so annoyed when we pay for Unity but still have to fix these errors ourselves...

 

I finally managed to get succes on my build. My solution was that I needed to do update some plug-ins that used an older "unity-iPhone" string (it was Native Alerts, Native Share and Agora). After that I set build target to iOS 12.0 (was 11.0) and then it finally managed to build and get accepted in App Store Connect.

I also set "Always embed switch standard libraries" to NO.