Failed to install plugins message?

Question

Xcode 9.1 Simulator 10.0 OSX 10.12.6

I want to upload a new assembly of my sticker to iTunes Connect. But product> Archive is inactive. So, I started Simulator and got "Failed to install plugins for name."

Only one answer anywhere in the world is to delete the Derived Data Folder folder. I did and received the same error message.

BTW In the General section of Xcode, the version is 1. The line is 1.4. Do I need to change the build number elsewhere?

Answer 1

What worked for me. Go to the target assembly steps and in the "Embedded Applications Extensions" check the box "Copy only during installation".

Answer 2

I had the same problem today. In my situation, I had a different identifier in my original application than in the decoding "base". The extension must have the same identifier as the original application, plus something else.

eg:

• Dummy App: com.company.dummy-app
• Dummy App Extension: com.company.dummy-app.extensionName

After Xcode told me about this, I changed my incorrect names to look higher, and then the problem arose: The problem was that I had "automatic signing control" converted to on , but Xcode did not recognize that I changed identifier.

Solution: Just change the identifier again and make sure that "automatic signing management" has created a new provisioning profile. Deleting retrieved data may also help.

Answer 3

It took me a while to find a fix for this. First go to the build steps, click the X next to the built-in and delete it. This should solve the problem, this is what worked for me.

Answer 4

This solution:

 app bundle identifier: com.SohaibSiddique.ShopApp extension bundle identifier: com.SohaibSiddique.ShopApp.Notification 

This might work for you.

Answer 5

A clean and rebuilt system often fixes this problem. If this does not work, try deleting the appeal files, which often cache the elements that xcode had to rebuild:

 find ~/Library/Developer/Xcode/DerivedData -name "*.appex" -exec rm -fr {} \; 

Answer 6

Product-> Clean Build Folder

Decided this for me.

Answer 7

This can also happen if the extension package identifier does not have an application identifier as a prefix.

For instance. this would raise the OP problem:

• com.example.App
• com.example.AppExtension

Instead of this:

• com.example.App
• com.example.App.Extension

will work as expected.