Updating to MBGL iOS SDK 6.3.0 on M1 chipset causes cocoapods linking error

Has anyone had any success upgrading to 6.3.0 on iOS, e.g.

$ReactNativeMapboxGLIOSVersion = '6.3.0'

When I switch this value from 6.2.1, and do a clean cocoapods install, it produces the following compile error:

library not found for -lPods-MyProject

which ultimately I can trace down to the Link Binary With Libraries build phase. The only linked library in the list is titled libPods-MyProject.a, which references a file in Pods/Products/ that doesn’t exist. If I remove that link, or just remove the entire build phase, the project compiles and runs properly.

But this doesn’t seem like the right solution, because doing a clean pod install automatically generates that build phase, so to fix this I would need to override pretty standard default behavior.

The same process, using 6.2.1, actually generates the libPods-MyProject.a file. I’m not sure where the bug actually lies. Does anyone have any ideas?

[naftalibeder]

Thank you so much for testing, and I’m sorry for the delay. I’ve had some colleagues attempt the same install, and sure enough, it fails on devices with an M1, and succeeds on those without.

For the purpose of leaving this issue so that I and people with the same problem can take some action, I am looking for an automated way to remove the libPods-MyProject.a library from the Link Binary With Libraries section, ideally in the Podfile itself. (This will allow development with the new version, before the iOS SDK actually supports the M1.)

Does anybody have any tips on how to achieve this? I’ve looked around and haven’t been able to pin it down.

[ferdicus]

Glad it helped at one front, sad it degraded on the other 😦

We’re not planning to immediately drop Mapbox support, if that’s the fear. At the moment MapLibre and (“old”) Mapbox are fairly similar.

We’d probably rather opt to not pursue v10 of Mapbox and stick with MapLibre instead for future versions.

This all obviously depends on contributors/ time 🤷🏿