Material-components-ios: MDCCatalog Build Failed

Created on 14 Nov 2018  ·  6Comments  ·  Source: material-components/material-components-ios

Hello,

A quick question — In Xcode, MDCCatalog was failed to build on my iPhone 7.
Anyone also has issues installing the build?

Reproduction steps

Steps to reproduce the behavior:

  1. Download Zip of https://github.com/material-components/material-components-ios
  2. In terminal,
cd material-components-ios-develop/catalog/
pod update
open MDCCatalog.xcworkspace
  1. In Xcode, select my Team ID. And select my iPhone device. And click run.
  2. Xcode shows "Build Failed" and Code Signing Errors:
Code Signing Error: No account for team "EQHXZ8M8AV". Add a new account in the Accounts preference pane or verify that your accounts have valid credentials.
Code Signing Error: No profiles for 'com.google.mdc-catalog.MDCActionExtension' were found:  Xcode couldn't find any iOS App Development provisioning profiles matching 'com.google.mdc-catalog.MDCActionExtension'.
Code Signing Error: Code signing is required for product type 'App Extension' in SDK 'iOS 12.1'

Platform

  • Device: iPhone 7 (iOS 12) and iPhone XS Max (iOS 12)
  • Xcode Version: v10.0

Internal data

Catalog Question

Most helpful comment

I always have to disable "automatic management" of the provisioning Provisioning Profile and select my developer profile manually. I do it for the Catalog (Debug and Release configs) and the ActionExtension (Debug and Release configs).

  1. Click on MDCCatalog in the Project Explorer
  2. In the "General" tab, find "Signing" section
  3. Uncheck "Automatically manage signing"
  4. Choose your provisioning profile under "Signing (Debug)" and "Signing (Release)"
  5. Switch to the "MDCActionExtension" target and repeat steps 2-4

All 6 comments

The title doesn't have a [Component] prefix.

I always have to disable "automatic management" of the provisioning Provisioning Profile and select my developer profile manually. I do it for the Catalog (Debug and Release configs) and the ActionExtension (Debug and Release configs).

  1. Click on MDCCatalog in the Project Explorer
  2. In the "General" tab, find "Signing" section
  3. Uncheck "Automatically manage signing"
  4. Choose your provisioning profile under "Signing (Debug)" and "Signing (Release)"
  5. Switch to the "MDCActionExtension" target and repeat steps 2-4

I always have to disable "automatic management" of the provisioning Provisioning Profile and select my developer profile manually. I do it for the Catalog (Debug and Release configs) and the ActionExtension (Debug and Release configs).

  1. Click on MDCCatalog in the Project Explorer
  2. In the "General" tab, find "Signing" section
  3. Uncheck "Automatically manage signing"
  4. Choose your provisioning profile under "Signing (Debug)" and "Signing (Release)"
  5. Switch to the "MDCActionExtension" target and repeat steps 2-4

Thanks @romoore for the quick reply! I tried your suggestion. However, Xcode showed two status messages (In the sections of "Signing (Debug)" and "Signing (Release)"), saying:

❗️Provisioning profile "[myProfileName]" has app ID "[com.myIDName.appName]", which does not match the bundle ID "com.google.mdc-catalog".

❗️Provisioning profile "[myProfileName]" doesn't match the entitlements file's value for the application-identifier entitlement.

Just thought about this — Is the MDCCatalog Build available to install on devices? Or, is this available but only for Google's internal developers?

Thanks,
Linne

Ah, sorry about that. I'm not sure what you could do when the bundle identifier and provisioning profiles don't match. Someone else on the team might have advice, though.

Hi Linne—to install on your device you'll need to change the bundle ID to match your provisioning profile setup. The com.google.mdc-catalog.* bundle IDs are associated with those in the Google developer account and you won't be able to generate those profiles. Hopefully this documentation from Apple covers your use case from what I understand of it: https://help.apple.com/xcode/mac/current/#/dev60b6fbbc7

Ahh okay, I see. Thanks a lot, @ajsecord and @romoore !

Was this page helpful?
0 / 5 - 0 ratings