Map plugin iOS example does not build

[duzenko]

Cloned the repo afresh and here's the error
/Users/a/Documents/flutterplugins/packages/google_maps_flutter/example/ios/Pods/Headers/Public/GoogleMaps/GoogleMaps/GMSAddress.h:14:9: Module 'GoogleMapsBase' not found

Seemingly fixed by manually adding this path to framework search paths (target google_maps_flutter):
/Users/a/Documents/flutterplugins/packages/google_maps_flutter/example/ios/Pods/GoogleMaps/Base/Frameworks

But since it does not show up in git it must be an ignored file somewhere.

[iskakaushik]

Should be fixed by flutter/plugins#1734

[mikhail-tokarev]

Hi @duzenko
are you still experiencing this issue with the latest version of Flutter?
If so please reply attaching your flutter doctor -v

[iapicca]

Hi @duzenko
if you could also post
a self contained app on github
it would help to reproduce the issue,
thank you

[jmagman]

https://github.com/flutter/plugins/tree/master/packages/google_maps_flutter/example

I deleted my ModuleCache, and I'm not able to reproduce in the example app. Also not able to reproduce on a new Swift or Obj-C flutter created app.

I'm about to add module support to that plugin, so it may be fixed with that.
You can also try adding use_modular_headers! to your Podfile.

[jmagman]

How do I do that?

Quit Xcode and rm DerivedData/ModuleCache.noindex.

[jmagman]

Consider the fact that not everyone knows what DerivedData or ModuleCache are.

I wasn't suggesting that was a fix. I'm trying to track down the bug, and I thoroughly tried to reproduce and couldn't. I was documenting my steps to point out that https://github.com/flutter/plugins/tree/master/packages/google_maps_flutter/example is not on its own sufficient to reproduce.

[jmagman]

Did you open Runner.xcworkspace and not Runner.xcodeproj?

[jmagman]

So were you opening the xcodeproj before?

[jmagman]

@duzenko Can we close this? I'm not sure there's enough actionable information here.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.