“Failed to set plugin placeholders” message?

Question

Xcode 9.1 Simulator 10.0 OSX 10.12.6

I would like to upload a new build of my sticker pack to iTunes Connect. But Product > Archive is grayed out. So I ran the Simulator and got ""Failed to set plugin placeholders for (name)."

Only one answer anywhere in the whole world -- delete Derived Data Folder. I did and got same error message.

BTW Under General in Xcode the Version is 1. The build is 1.4. Does the build number have to be changed somewhere else as well?

Answer 1

What worked for me, Go to your target Build Phases and on "Embedded App Extensions" check the "Copy only when installing" checkbox.

Answer 2

I had the same problem today. In my situation I had a different identifier in my original app than in the extension identifier "base". The extension has to have the same identifier as the original app plus something else.

E.g:

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

After Xcode told me that, I changed my wrong names to look like above and then the problem occurred: The problem was, that I had "automatic manage signing" turned on but Xcode didn't recognize that I changed the identifier.

Solution: Just change the identifier again and check if "automatic manage signing" has created a new provisioning profile. Deleting derived data may also helps.

Answer 3

It took me a while to find the fix for this. First go to build phases click the X beside the embedded and delete it. This should fix the problem it is what worked for me.

Answer 4

This is the solution:

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

It may work for you.

Answer 5

It may also happen if the bundle identifier of the extension doesn't have the app identifier as a prefix.

E.g. this would raise the OP issue:

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

Instead:

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

will work as expected.

Answer 6

A clean and rebuild will often fix this issue. If that doesn't work, try removing appex files which often cache items which xcode should have rebuilt:

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

Answer 7

Product->Clean Build Folder

Solved it for me.