Kyle Kurz

I was also able to reproduce this today as well on my production repo. I believe my instructions from https://github.com/bazelbuild/bazel/issues/14278 will still reproduce it with minimal effort.

@tjgq I will give this a shot. Might not get to it until tomorrow though.

@tjgq sorry for the delay, been fighting migraines for a week. It doesn't look like that branch fixes this: ``` at com.google.devtools.build.skyframe.AbstractParallelEvaluator$Evaluate.run(AbstractParallelEvaluator.java:646) at com.google.devtools.build.lib.concurrent.AbstractQueueVisitor$WrappedRunnable.run(AbstractQueueVisitor.java:382) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)...

@tjgq does that mean my build of your branch was wrong? I definitely didn't get a successful WIF run using that, but I can try again if you'd like.

I have a GHA runner I manage in GCP so I can have local cache for some runs, so I just built the binary (on that machine) and called it...

@tjgq so I'm still not entirely sure what I did wrong building your branch, but I think I agree that your fix works. I took the binary in your test...

+1 EDIT: Here's the output of my attempt to run objcgen against my current C# .dll ```kkurz@HacBook-Pro:~/Git/softphones/Platform.ios.fsharp (development)*$ objcgen bin/Debug/Platform.ios.csharp.dll --target=framework --platform=iOS --outdir=output -c --debug Parsing assemblies... Parsed 'bin/Debug/Platform.ios.csharp.dll' Processing...

@tidwall you merged that in and made a tag for v2.8.0, but never pushed that up to the cocoapod spec repo. Can you get that update pushed so we can...

Logs are here: https://gist.github.com/kylekurz/45d872721ed58e2b6d4ff70f76b26e0c The configuration provided above is all that is needed to trigger this, if you're on provider version `4.5.0`. If I back the provider down to `4.3.0`,...

I just tested `4.4.0` too, that has the same error case. So something in the upgrade from `4.3.0` -> `4.4.0` breaks this, it's not new in `4.5.0`.