Jenn Magder

> @jmagman oh we use connectivity_plus should I move this issue to connectivity_plus? Yes, you should create a bug report with them. Thanks! Closing.

> Have you run `pod update` in the `ios` directory? Running that explicitly should never be necessary, the `flutter` command will do that for you. If it is ever needed...

As for the actual failure, I bisected to https://github.com/flutter/engine/pull/36854, guessing one of those pub rolls. I will make a minimum repro project and file an issue with pub.

I can't figure out what's going on here, I don't understand why CocoaPods is preferring the version in the Podfile.lock over the updated version symlinked from pub. I see https://github.com/flutter/news_template/blob/379948be38c22324389ae817c398e2770efe3ffe/google_news_project/ios/Podfile#L31...

If this is building on current stable 3.7 then this can be closed.

I'm also reproducing this on my M1. https://github.com/flutter/engine/blob/a04997c81f78746fdd44f8b6b3058bcc13ef39ad/testing/run_tests.py#L600-L601 `xcodebuild -version` is returning bytes `b'Xcode 14.2\nBuild version 14C18\n'` @cbracken I thought we tracked all these cases down during the python3 migration....

Adding `version_output.decode()` on my machine passes, but if it's a string in CI (or it's dropping back to python 2?) then that will fail `'str' object has no attribute 'decode'`...

@yusuf-goog are the necessary signing certs available on non-devicelab machines?

It's not the "waiting for symbols" problem the `ios_debug_symbol_doctor` check would work around. There doesn't seem to be a pending dialog pop up, and it's happening on 3 different devices....

> 3577 is a Dart VM GC crash. The Dart VM GC crash is tracked elsewhere Tracking in https://github.com/flutter/flutter/issues/121705