MapboxMobileEvents takes a long time to link

[arbitur]

My setup

Machine: MacBook Pro 13", Mid 2014, 16GB RAM, i5 CPU
macOS version: 10.15.3
Mapbox version: 5.7.0, installed with cocoapods
XCode version: 11.3.1, using New build system
Cocoapods version: 1.9.0

Mapbox takes a tremendous amount of time during the "Embed Pods Frameworks" build process. On my machine (MacBook Pro 13", Mid 2014) it takes about 7 minutes to compile and it stays on mapbox related frameworks solely for ~6 minutes.

It didn't use to take this long like a year or so ago. I would guess this problem might have several causes, cocoapods version update, xcode version update, os update etc but I would like your input on this.

Do you have any tips on how to speed up this process? Thanks.

[1ec5]

The only thing I can think of is that, beginning with version v5.6.0, the map SDK dynamically links MapboxMobileEvents when installed using CocoaPods or Carthage, and MapboxMobileEvents is built from source. Previously, it was statically linked into the map SDK, which is distributed as a binary. One workaround would be to install the SDK manually without a dependency manager.

/cc @rclee @julianrex

[arbitur]

The fault wasnt with MapBox 👍

[julianrex]

Thanks for letting us know @arbitur!

[1ec5]

We’ve been encountering long MapboxMobileEvents link times on CircleCI that we suspect might be related to this issue. We aren’t sure if it always happens on CI, but it at least happens with the ios-release-tag builds that normally only run when releasing (the worst possible time for linking to stall).

@julianrex found that reducing the number of concurrent jobs in #221 seemed to reduce the link time, but we’d need to have the ios-release-tag workflow run to be sure. (#199 did temporarily enable the ios-release-tag workflow unconditionally, but I rewrote that out of history because we don’t want fake releases lying around.)

[1ec5]

This nightly build also timed out due to long link times.

[1ec5]

This release build from tagging v5.8.0-beta.1 got killed after over 20 minutes linking. That was with the change in #221.

[knov]

May also resolve #71