Reputation: 6405

Validation Error: Invalid Bundle. The bundle at ... contains disallowed file 'Frameworks'

I'm trying to submit an app with the Xcode 6 GM, and I get this error on validation. The app has an action extension and a dynamic framework that's shared between the extension and the app itself.

I don't have a file called 'Frameworks' anywhere in the project, so I'm really not sure what this is supposed to mean. Has anyone gotten this issue or have any ideas?

here's what the error looks like

Archive validation failed due to the issues listed below.
iTunes Store operation failed.
Invalid Bundle. The bundle at ... contains disallowed file 'Frameworks'.

Upvotes: 205

Answers (22)

Владимир Ефанов

Reputation: 681

For Unity3D

Set "Always Embed Swift Standart Libraries" to YES for the Unity-iPhone target
Delete Framework folder inside your .xcodearchive (see picture) path to archives ~/Library/Developer/Xcode/Archives

from unity forum https://forum.unity.com/threads/2019-3-validation-on-upload-to-store-gives-unityframework-framework-contains-disallowed-file.751112/

Upvotes: 3

Владимир Ефанов

Reputation: 681

You have to add script to the end of Build Phases

cd "${CONFIGURATION_BUILD_DIR}/${UNLOCALIZED_RESOURCES_FOLDER_PATH}/"
if [[ -d "Frameworks" ]]; then 
    rm -fr Frameworks
fi

Upvotes: 1

Moran77

Reputation: 149

You should remove embedded frameworks from all pods and extension like in describe in: https://stackoverflow.com/a/40396491/2559850

Upvotes: 0

Juan Sagasti

Reputation: 344

In my case, Firebase SPM was the culprit. I have a ShareExtension that was failing AppStore validation because of the frameworks folder. I fixed that with a post-archive script in the schema:

Upvotes: 1

Narasimha Nallamsetty

Reputation: 1263

the above answers did not work for me. I have done below things.

copied target settings of extension from other developer from the team
Container App: Embedded Content Contains Swift Code: YES
Extension: Embedded Content Contains Swift Code: NO

Please check every setting of extension from the Target.

Upvotes: 5

Belle B. Cooper

Reputation: 395

I found lots of questions like this and none helped me fix my problem, so hopefully this might help someone.

I'm creating an app that has an Intent extension (for Siri shortcuts) and I'm using a framework for code shared between the extension and my app, as recommended by Apple.

I had added my framework to my extension in the "Frameworks and Libraries" section of the "General" settings for the target. When you add a framework here, there are two columns. One says the name of the framework and the other is titled "Embed". I had nothing showing up in the "Embed" column so I thought that was fine, but I had to explicitly choose a "Do Not Embed" option for that column for my framework. When I did that and archived in Xcode, I could see during validation that the framework wasn't listed in my ipa content under each target anymore, but just once, and validation succeeded finally.

Upvotes: 2

Zatman

Reputation: 274

I was getting the same error, and it is because I was copying the framework into the extension bundle. As it turns out, frameworks that are used by the extension should be copied into the Main App bundle and only linked in the extension build settings (not copied). Be sure to have the search path '@executable_path/../../Frameworks' in the extension build. I think that path was added automatically by XCode 10.

Upvotes: 3

Travis M.

Reputation: 11257

None of the Build Settings listed here resolved this issue for me. However, I did get this to work after moving some frameworks from "Embedded Binaries" to "Linked Frameworks and Libraries".

It appears that my main app and one of my custom frameworks had the same framework dependency in both and that seems to be a No No but moving it in my main app from the Embedded area to the Linked area allowed me to upload the app successfully with no errors.

Upvotes: 3

Frank

Reputation: 409

I was getting this same error, along with a

Disallowed nested bundles error

My problem was with the SquareReaderSDK.framework specifically but I had to add a new run script per their instructions:

FRAMEWORKS="${BUILT_PRODUCTS_DIR}/${FRAMEWORKS_FOLDER_PATH}"
"${FRAMEWORKS}/SquareReaderSDK.framework/setup"

Upvotes: 0

Mike

Reputation: 6405

Turns out the error is related to using Swift (both the app and the extension make use of Swift).

For the app, I had to set:

Embedded Content Contains Swift Code: YES

and for the extension:

Embedded Content Contains Swift Code: NO

Xcode 8 and 9

Looks like this has been renamed to Always Embed Swift Standard Libraries in Xcode 8 and 9. So, for the app:

Always Embed Swift Standard Libraries: YES

and for the extension:

Always Embed Swift Standard Libraries: NO

Upvotes: 374

suztomo

Reputation: 5202

In my case, there was one CocoaPod library "Blockly" that was specifying Yes for "Always Embed Swift Standard Libraries". After making NO for the option, it worked.

Upvotes: 15

Roman

Reputation: 1993

The only solution that worked for me was to add this Run Script to the App Extension target:

cd "${CONFIGURATION_BUILD_DIR}/${UNLOCALIZED_RESOURCES_FOLDER_PATH}/"
if [[ -d "Frameworks" ]]; then 
    rm -fr Frameworks
fi

Source: https://github.com/CocoaPods/CocoaPods/issues/4203

Upvotes: 128

Kudit

Reputation: 4379

I was unable to find any settings for Embedded Content Contains Swift Code but I was able to find a setting Always Embed Swift Standard Libraries and setting this to NO for my framework did fix this issue.

Upvotes: 7

Yongxiang Ruan

Reputation: 189

Container App: Build Setting -> Embedded Content Contains Swift Code: YES
Extension: Build Setting -> Embedded Content Contains Swift Code: NO
Extension: Build Phase -> added the following Run Script in

cd "${CONFIGURATION_BUILD_DIR}/${UNLOCALIZED_RESOURCES_FOLDER_PATH}/" if [[ -d "Frameworks" ]]; then rm -fr Frameworks fi

(important)Extension: Build Phase -> move the Run Script to the Last (after Embed Pods Frameworks script )

Upvotes: 4

Kurt J

Reputation: 2603

If you're using CocoaPods, I would consider deleting the Embed frameworks build phase on the problematic target (the extension), this fixed the problem for me.

Upvotes: 4

Max MacLeod

Reputation: 26672

None of the above answers worked for me. This was because the error was caused not by the parent app or it's extension. Rather one of the linked libraries was at fault.

To confirm, first archive using Xcode then using Organiser select the entry and locate using Show in Finder. This will show the .xcarchive file.

Select that file and choose "Show Package Contents".

Select the .app in the Products/Applications folder and again choose "Show Package Contents".

Locate the offending module in the Frameworks folder. For example if the error is:

ERROR ITMS-90206: "Invalid Bundle. The bundle at 'MyApp.app/Frameworks/MyLib.framework' contains disallowed file 'Frameworks'."

Then in the Frameworks/MyLib.framework the following will probably be visible:

../Frameworks/libswiftContacts.dylib
../Frameworks/libswiftCore.dylib
../Frameworks/libswiftCoreData.dylib
../Frameworks/libswiftCoreGraphics.dylib
../Frameworks/libswiftCoreImage.dylib
../Frameworks/libswiftCoreLocation.dylib
../Frameworks/libswiftDarwin.dylib
../Frameworks/libswiftDispatch.dylib
../Frameworks/libswiftFoundation.dylib
../Frameworks/libswiftLocalAuthentication.dylib
../Frameworks/libswiftObjectiveC.dylib
../Frameworks/libswiftPassKit.dylib
../Frameworks/libswiftUIKit.dylib
../Frameworks/libswiftWebKit.dylib

These are present because the linked library - or module - that the parent app includes has the EMBEDDED_CONTENT_CONTAINS_SWIFT = YES;

Locate the dependent module in Xcode and update the flag:

Note that having overcome this issue the app may still be rejected with an explanatory email from the iTunes Store:

Invalid Swift Support - The Watch OS application has Swift libraries at both...

Again this comes back to the EMBEDDED_CONTENT_CONTAINS_SWIFT flag. Ensure that only the parent app has this set to YES. Both the WatchKit app and extension must have this flag set to NO. This is as detailed in @Mike's answer above.

Upvotes: 12

Dan Loughney

Reputation: 4677

In my case, I just upgraded to CocoaPods 1.0.1 and this appears to be a new bug.

The Pod update adds a run script to my Extension's target which creates the Frameworks folder. I found it as I was about to add @Roman's run script to remove it.

Solution was to delete this script from my extension's build phase. Here is the one which needed to go...

Upvotes: 16

Reeonce Zeng

Reputation: 392

If Embed Pods Frameworks script and Roman's script both exist in the same target.

Please check if the Embed Pods Frameworks locates before the other one. If not, just move Roman's script to the last.

Upvotes: 7

Bartłomiej Semańczyk

Reputation: 61840

Remove Every Build Phase for your extension that has embed word in its title.

Additionally:

Embedded content contains Swift code must be set to Yes for the extension target.

Upvotes: 14

Vincent Song

Reputation: 642

So 3 steps to fix this from build settings

Container App: Embedded Content Contains Swift Code: YES
Extension: Embedded Content Contains Swift Code: NO
Extension: Runpath Search Path = @executable_path/../../Frameworks

Upvotes: 52

andreacipriani

Reputation: 2591

I had this problem the first time with XCode 7.1.1 for my app that has a Today Extension (there is no Swift in my project). The script (https://github.com/CocoaPods/CocoaPods/issues/4203) didn't work for me.

Downgrading cocoapods to version 0.39.0.beta.3, running pod install, and then re-archiving solved the problem.

Upvotes: 0

Pim

Reputation: 2128

In my case the solution was to remove my framework from my extension's Embedded Binaries and add it to my extension's Linked Frameworks and Libraries. (Both can be found in the extension's General tab.)

Upvotes: 10

Validation Error: Invalid Bundle. The bundle at ... contains disallowed file &#39;Frameworks&#39;

Answers (22)

Related Questions

Validation Error: Invalid Bundle. The bundle at ... contains disallowed file 'Frameworks'