Fixed
Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
sn...@gmail.com
This issue should be closed.
br...@google.com
The Podfile.lock is sufficient to reproduce a Pods directory by installing CocoaPods from the network with:
$ pod install
$ pod install
[Deleted User] <[Deleted User]>
I'm pretty disappointed that this issue was dismissed so quickly.
I feel like there are 2 main points that weren't considered at all:
1) I'm literally only using GMSAutocompleteViewController, it's absurd that I need to link my app to a 100MB+ binary for this one little widget
2) Committing up the Pods directory is actually an extremely common workflow, one that's been in use at every place I've worked. It provides multiple advantages, most notably when it comes to:
- onboarding new devs
- working with a CI server
- switching between branches
- going back in time to past commits
As a matter of fact, the official Cocoapods docs state: "We recommend that you keep the Pods directory under source control, and don't add it to your .gitignore" (http://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control )
As such, I feel like this issue should be re-opened, and that you guys should take a look at the solutions that the Paypal andcard.io teams came up with:
https://github.com/card-io/card.io-iOS-SDK/issues/147
https://github.com/paypal/PayPal-iOS-SDK/issues/339
I feel like there are 2 main points that weren't considered at all:
1) I'm literally only using GMSAutocompleteViewController, it's absurd that I need to link my app to a 100MB+ binary for this one little widget
2) Committing up the Pods directory is actually an extremely common workflow, one that's been in use at every place I've worked. It provides multiple advantages, most notably when it comes to:
- onboarding new devs
- working with a CI server
- switching between branches
- going back in time to past commits
As a matter of fact, the official Cocoapods docs state: "We recommend that you keep the Pods directory under source control, and don't add it to your .gitignore" (
As such, I feel like this issue should be re-opened, and that you guys should take a look at the solutions that the Paypal and
br...@google.com
I'll ask the various teams to look at splitting up the libraries.
I'd also suggest raising a ticket with GitHub about their 100 mb limit.
I'd also suggest raising a ticket with GitHub about their 100 mb limit.
jo...@gmail.com
[Comment deleted]
jo...@gmail.com
Until this is resolved I am staying on 1.10.5
co...@gmail.com
You could try setting up Google maps locally, without cocoapods. linking the framework to your project without adding it to the project.
[Deleted User] <[Deleted User]>
I also will not be able to upgrade from 1.10.5 until this is resolved.
up...@myport.ac.uk
Can someone help!? Ive deleted this pod from my project by changing the Podfile then doing 'pod install' and its removed from my project but when i try to commit its throwing this error and saying that its still there when it isn't!? I'm so confused!
pa...@paulhimes.com
[Deleted User] <[Deleted User]>
Thank god i came across this, I am now using 1.10.5 too, so many git filter commands before seeing this...
[Deleted User] <[Deleted User]>
+ 1 on the max size of Github and the fact that most stuff (mainly resources) are not needed for most developers, resulting in large code repositories & binary files.
ro...@gmail.com
I am now using 1.10.5 too, because of it
br...@google.com
Quick question for the assembled crowd: What architectures do you guys compile your apps with?
A quick and simple way of stripping back the size of the bundle from 119mb to 87mb is to drop armv7s. Run the following command from the Versions/A/ directory in the framework:
$ lipo -remove armv7s GoogleMaps -output GoogleMaps
A quick and simple way of stripping back the size of the bundle from 119mb to 87mb is to drop armv7s. Run the following command from the Versions/A/ directory in the framework:
$ lipo -remove armv7s GoogleMaps -output GoogleMaps
jo...@modeo.co
+1 to this issue. removing armv7s support will not work.
[Deleted User] <[Deleted User]>
I am still experiencing this issue with 1.12.1.
@brettmor Any update on this?
@brettmor Any update on this?
br...@google.com
Per the release notes, 1.12.1 is identical to 1.11.1. We were part way through launching 1.12.0 when we found issues with the build. Due to reasons, we couldn't roll back the 1.12.0 CocoaPod, and thus had to push 1.11.1 as 1.12.1.
Sorry for the confusion.
Sorry for the confusion.
pa...@paulhimes.com
We also cannot drop armv7s support.
jo...@modeo.co
pa...@paulhimes.com
Has anyone gotten Git Large File Storage to work with OS X Server / Xcode Server? That's what stopped us.
el...@gmail.com
+1 I also check in the Pods folder.
I think a decent workaround for now is to add just Pods/GoogleMaps to .gitignore. I still have to run pod install after a clone, but I feel better knowing the only pod I need to reinstall is GoogleMaps and not 20 other random pods that could have changed or disappeared all together.
I think a decent workaround for now is to add just Pods/GoogleMaps to .gitignore. I still have to run pod install after a clone, but I feel better knowing the only pod I need to reinstall is GoogleMaps and not 20 other random pods that could have changed or disappeared all together.
mh...@gmail.com
Are there any updates on this? If I try to update the GoogleMaps cocoapod to a newer version, suddenly I get an error in 2 of my View Controllers:
Cannot convert value of type '(GMSReverseGeocodeResponse!, NSError!) -> Void' to expected argument type 'GMSReverseGeocodeCallback' (aka '(Optional, Optional) -> ()')
The solution to fixing that one is not documented in a single place anywhere other than someone else who asked the same question on SO and the 1 answer someone gave was to downgrade to version 1.11.1. Somehow this all comes full circle...https://stackoverflow.com/questions/35618629/gmsreversegeocodecallback-after-updated-google-map-via-pod
Now I'm back to square 1 trying to solve the original problem of pushing up to my GitHub repo without updating to the newest cocoapod and having to tear apart my code for the GMSReverseGeocodeCallback error.
Where does this issue stand?
Cannot convert value of type '(GMSReverseGeocodeResponse!, NSError!) -> Void' to expected argument type 'GMSReverseGeocodeCallback' (aka '(Optional, Optional) -> ()')
The solution to fixing that one is not documented in a single place anywhere other than someone else who asked the same question on SO and the 1 answer someone gave was to downgrade to version 1.11.1. Somehow this all comes full circle...
Now I'm back to square 1 trying to solve the original problem of pushing up to my GitHub repo without updating to the newest cocoapod and having to tear apart my code for the GMSReverseGeocodeCallback error.
Where does this issue stand?
br...@google.com
MHorn918, you are actually talking about a completely separate issue, which isn't a bug.
In release 1.12.2 we updated the API annotations to make the API better for Swift. See:
https://developers.google.com/maps/documentation/ios-sdk/releases#version_1122_-_february_2016
There were places in the API where we had the default ObjC -> Swift conversions which implied a non-null value which we were actually treating as optional in ObjC. The updated annotations now correctly reflect that the values to the callback are optional.
The fix in this case is to update your code.
In release 1.12.2 we updated the API annotations to make the API better for Swift. See:
There were places in the API where we had the default ObjC -> Swift conversions which implied a non-null value which we were actually treating as optional in ObjC. The updated annotations now correctly reflect that the values to the callback are optional.
The fix in this case is to update your code.
mh...@gmail.com
Thanks Brett. However, What is the solution to the original issue here?
remote: error: File Pods/GoogleMaps/Frameworks/GoogleMaps.framework/Versions/A/GoogleMaps is 113.56 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: File Pods/GoogleMaps/Frameworks/GoogleMaps.framework/Versions/A/GoogleMaps is 113.56 MB; this exceeds GitHub's file size limit of 100.00 MB
br...@google.com
MHorn918, the bug is marked as Accepted, which means we are looking at ways we can reduce the binary size without losing required functionality.
As this requires architectural work, there is no quick and easy fix. We will update this bug if and when we have more information.
As this requires architectural work, there is no quick and easy fix. We will update this bug if and when we have more information.
mi...@detroitlabs.com
Brett,
Any update on this? We are having the same issues. We tried to hide the framework/files in the gitignore and it will not take that. The framework is jumping back into the main files and trying to go to git.
Any update on this? We are having the same issues. We tried to hide the framework/files in the gitignore and it will not take that. The framework is jumping back into the main files and trying to go to git.
br...@google.com
With the Google Maps SDK for iOS v2.0 release we have split the CocoaPod into separate pieces, thus bringing the binary beneath GitHub's 100meg limit. Thanks for the report!
ca...@gmail.com
Woohoo, thanks!
[Deleted User] <[Deleted User]>
Much appreciated!
[Deleted User] <[Deleted User]>
I still have some issues with this problem. When I add the 'GooglePlacePicker' pod I get this message: Unable to find a specification for `GooglePlacePicker`
I also note that some classes documentation are inaccessible now(https://developers.google.com/maps/documentation/ios-sdk/reference/interface_g_m_s_autocomplete_prediction )
At this page(https://developers.google.com/places/ios-api/start?hl=fr ) it's said that we should integrate pod 'GoogleMaps' the opposite of what is said in the migration to v2 guide(https://developers.google.com/places/migrate-to-v2 )
Any explication would be appreciated.
Thanks !
I also note that some classes documentation are inaccessible now(
At this page(
Any explication would be appreciated.
Thanks !
br...@google.com
Hey Amath,
Our understanding is as follows:
For the issue with being unable to find the specification for GooglePlacePicker, we believe the GitHub outage may have impacted you. Please re-try and see if you still can't progress.
For the inaccessible documentation links, as part of splitting the Places API out of the Maps API we have now separate documentation for the two APIs. Please have a look athttps://developers.google.com/places/ios-api/reference/interface_g_m_s_autocomplete_prediction
For the difference between the english and the french documentation, yes, sorry. Our translations have yet to be updated for the pod split. Please look at the english version of our documentation while we get the translations updated.
Thanks!
Our understanding is as follows:
For the issue with being unable to find the specification for GooglePlacePicker, we believe the GitHub outage may have impacted you. Please re-try and see if you still can't progress.
For the inaccessible documentation links, as part of splitting the Places API out of the Maps API we have now separate documentation for the two APIs. Please have a look at
For the difference between the english and the french documentation, yes, sorry. Our translations have yet to be updated for the pod split. Please look at the english version of our documentation while we get the translations updated.
Thanks!
mu...@triffort.com
The only solution i found is to don't push google map library on git. You can ignore it's path from repository and if someone else downloaded your project, he need to run Pods again to install the library.
[Deleted User] <[Deleted User]>
There is still the problem of Unable to find a specification for `GooglePlacePicker` when I try to add this pod.
In other side I'm a little a bit confused, how is it possible to have at the same time 2 GoogleMaps pod. One with just Maps functionalities and another with maps, places and picker functionalities. I suppose that we must specify the git url to make difference between these 2 GoogleMaps pod. But I found anything about this differentiation on the documentation.
Any explication would be appreciated.
Thanks !
In other side I'm a little a bit confused, how is it possible to have at the same time 2 GoogleMaps pod. One with just Maps functionalities and another with maps, places and picker functionalities. I suppose that we must specify the git url to make difference between these 2 GoogleMaps pod. But I found anything about this differentiation on the documentation.
Any explication would be appreciated.
Thanks !
br...@google.com
Hey Amath, please raise a new issue with an attached repro case hosted on github demonstrating your issue. Please see github.com/domesticmouse/MovingMarkerPosition for an example of how to post up a repro that we can work with.
Thanks!
Thanks!
cl...@gmail.com
[Comment deleted]
w....@gmail.com
For anyone having trouble finding the specification for 'GooglePlacePicker' pod you need to specify the version number and it will download correctly
Description
I'm not sure how many people version control their Pods using GitHub, but I thought it would be a good idea to create an issue anyway (feel free to close/delete).
What steps will reproduce the problem?
1. Install Google Maps iOS SDK via CocoaPods
2. Add Pods to git
3. Push to GitHub
Result:
remote: error: GH001: Large files detected. You may want to try Git Large File Storage -
remote: error: Trace: 3509bacf08db7e7c09ceb60d27baaac8
remote: error: See
remote: error: File Pods/GoogleMaps/Frameworks/GoogleMaps.framework/Versions/A/GoogleMaps is 113.56 MB; this exceeds GitHub's file size limit of 100.00 MB
Google Maps SDK for iOS version: 1.11.1
*********************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*********************************************************