Jeff Verkoeyen

No workaround at present other than manually cloning the repository and adding it as a dependency via Xcode (similar to what Carthage would do).

> Carthage uses shared schemas and can build them all as separate build targets Ah this is interesting. Is it possible to generate multiple libraries that will be resolved at...

Thanks for the clarifications everyone. I believe then there are a couple levels to delivering support for this: Level 1: Create a single Carthage-compatible .framework for MDC and upload it...

Re-opening this due to community interest.

Current output: ``` > carthage update --use-xcframeworks *** Cloning motion-animator-objc *** Cloning material-text-accessibility-ios *** Cloning motion-interchange-objc *** Cloning material-internationalization-ios *** Checking out material-text-accessibility-ios at "v2.0.1" *** Checking out material-internationalization-ios at...

Agreed.

The internal issue is not yet closed, re-opening this issue. Googler: please check the state of the internal issue and update it accordingly.

I isolated the test target in a `while true` bash loop and could not get it to flake after a half dozen iterations locally, making me believe the flakiness may...

Flakiness has gone down now that I’ve marked ui tests with tags = ["exclusive"], but I am still seeing flakes on a runner that uses a conditional device type. E.g.:...

Am continuing to update this PR: https://github.com/material-components/material-components-ios/pull/4182 You can view the kokoro log outputs on the pr commit statuses.