stuartmorgan-g

Even if there's some more generic solution, I still think we should special-case CFString as it's a pretty common type. There shouldn't be any risk of collision, because `CFStringRef` already...

> But maybe it would it be worth adding `CFStringRef` to package:objective_c? I didn't realize I hadn't replied to this; I would definitely suggest we include it in `objective_c` given...

> I think it would be good to start accumulating examples so that we can try to make an informed decision. @stuartmorgan would you mind linking the various examples that...

> and conditionally import them Based on what condition? Last I checked conditional import by platform was impossible. Was there a language change? (Edit: [The public docs](https://dart.dev/guides/libraries/create-packages#conditionally-importing-and-exporting-library-files) still seem to...

> If this sort of conditional import is important for iOS/macOS interop, we should reprioritize that bug. It was P1 for a while. We should probably figure out if there's...

I'm not seeing how either of those approaches would address case 2 at all; could you give an example?

> I would encourage you to use the bytecode `.jar` of exoplayer instead of `.java` sources. How? I'm not intentionally using either, I'm just pointing to my plug-in source and...

> You can add the exoplayer dependency to the `app/build.gradle` of your example Is there an issue tracking the need to duplicate all dependency information from a plugin into the...

It would also be good to mention in the setup/usage section that the project needs to add `jni`. I assumed it would be a transitive dependency, so hit `Fatal: package:jni...

From triage: What's the status of this? Is it still something we plan to deploy? It would definitely be useful for debugging!