"Failed to set plugin placeholders" message?
Solution 1
What worked for me, Go to your target Build Phases and on "Embedded App Extensions" check the "Copy only when installing" checkbox.
Solution 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.
Solution 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.
Solution 4
You must have different bundleIds for your project and extension.
Example:
- App bundleId: com.companyName.appName
- Extension bundleId: com.companyName.appName.extensionName
I got this error when I set one configuration file for my project and notification service.
I changed the notification service configuration file to the correct one and this fixed my problem.
Solution 5
This is the solution:
app bundle identifier: com.SohaibSiddique.ShopApp
extension bundle identifier: com.SohaibSiddique.ShopApp.Notification
It may work for you.
![Admin](/assets/logo_square_200-5d0d61d6853298bd2a4fe063103715b4daf2819fc21225efa21dfb93e61952ea.png)
Admin
Updated on October 10, 2021Comments
-
Admin over 2 years
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?
-
Andrew Bennett over 6 yearsThank you - much appreciated
-
Dylan Moore almost 6 yearsThis worked for me. Even though Xcode labeled the correct bundle id in the provisioning profile info modal. I just had to continually add and remove letters from my bundle ID until the certificates were correctly assigned.
-
Manuel over 4 yearsWhat does that flag do?
-
Shadab Mehdi over 3 yearsThank you, James. Much appreciated.
-
Datow King almost 3 yearsSolved it for me too. Thank you!
-
CKT almost 3 yearsthis doesn't work for widgets. please let me know if there is any fix for widgets.
-
Muhammad Shafique about 2 yearsPerfectly explained. Worked for me