Xamarin.forms.googlemaps: iOS build error with v3.3.0

Created on 23 Oct 2019  路  13Comments  路  Source: amay077/Xamarin.Forms.GoogleMaps

VERSIONS

  • Xamarin.Forms.GoogleMaps - 3.3.0
  • Xamarin.Forms - 4.3.0
  • *

PLATFORMS

  • [ ] Android
  • [x] iOS
  • [ ] UWP

ACTUAL BEHAVIOR

Build error:
/Users/stesvis/Documents/projects/levitica/livedispatch/LiveDispatch.Mobile/LiveDispatch.Mobile.iOS/error MT5209: Error: warning: directory not found for option '-FGMps-3.5.0/Maps/Frameworks' (LiveDispatch.Mobile.iOS) Native linking

EXPECTED BEHAVIOR

It should build with no errors

HOW TO REPRODUCE

  1. Install the latest version
  2. Build the iOS project

Most helpful comment

I submitted this issue to Xamarin repo and finally solved by explicit add a NuGet package Xamarin.Build.Download.

https://github.com/xamarin/GoogleApisForiOSComponents/issues/324#issuecomment-545725609

All 13 comments

i have the same issue.

Is this link helps you?

I think it is related with Xcode project setting.

I have the same problem.
I can't compile for ios when I upgrade to 3.3.0.
No problem in 3.2.1.
image

I can not reproduce.
Probably it is not related Xamarin.Forms.GoogleMaps also not related Xamarin.Forms .

I think it is Xamarin.iOS with GoogleApisForiOSComponents issue.

Please try using Xamarin.Google.iOS.Maps 3.5.0 with Xamarin.iOS(NOT Xamarin.Forms) and if you can see same error, report to Xamarin team.

I submitted this issue to Xamarin repo and finally solved by explicit add a NuGet package Xamarin.Build.Download.

https://github.com/xamarin/GoogleApisForiOSComponents/issues/324#issuecomment-545725609

Thanks @hajuuk
That solves it indeed

@hajuuk, you did great work! 馃憤

Awesome! Side note, you have to target at least iOS 10 otherwise you still get build errors.

@hajuuk do we need to install it only on the iOS project or all three?

@hajuuk do we need to install it only on the iOS project or all three?

I tested, install it for the iOS project is sufficient.

I added the Xamarin.Build.Download nuget package to my project and then upgraded it to v.3.3.0. But the problem did not disappear. Anybody have any ideas?

image

@erdugen i had to target minimum iOS 10.0

@erdugen i had to target minimum iOS 10.0

@stesvis Thank you. Problem solved in this way.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

JKennedy24 picture JKennedy24  路  6Comments

woellij picture woellij  路  4Comments

non335 picture non335  路  7Comments

idan-rubin picture idan-rubin  路  6Comments

talhaa91 picture talhaa91  路  4Comments