Missing mapbox.png resource after updating to Mapbox-iOS-SDK 3.1.2 w/ Fabric integration

[stcleezy]

I've updated to Mapbox-iOS-SDK 3.1.2 w/ Fabric according to the instructions here:
https://fabric.io/kits/ios/mapbox/install

However, whenever I try to instantiate MGLMapView, I get the following error:
Terminating app due to uncaught exception 'Resource not found', reason: 'The resource named “mapbox.png” could not be found in the Mapbox resource bundle.'

I see some people had issues w/ earlier version of Mapbox (#3281), but I am using the following:

Cocoapods 0.39.0
Mapbox-iOS-SDK (3.1.2)

This is what my Pods tree looks like:

Any help would be greatly appreciated!

[1ec5]

In the project editor, is Mapbox.framework listed in the “Embedded Binaries” section or the “Linked Frameworks and Libraries” section? It should be listed under both if you used CocoaPods to install the dynamic framework. (On the other hand, if you use Fabric’s Mac application, you’d get the 3.1.3 static framework, which should only be listed under “Linked Frameworks and Libraries”.)

[stcleezy]

I'm using CocoaPods, not the Mac app.

The Mapbox.framework wasn't in either "Embedded Binaries" or "Linked Frameworks and Libraries". I've manually added the dynamic framework to both, but I am still getting the same error.

[stcleezy]

Some more info that is hopefully helpful:

• I upgraded from pre-GL version 1.6.1, also via CocoaPods. Not sure if this left some cruft in the project.
• The Fabric app doesn't recognize that Mapbox is installed. When I go through the steps to install version 3.1.3 (which references adding Fabric and Mapbox-iOS-SDK to my pdodfile and adding my account key) I also get an error:

[1ec5]

I upgraded from pre-GL version 1.6.1, also via CocoaPods. Not sure if this left some cruft in the project.

It may have. The raster SDK was very different in terms of its dependencies.

The Fabric app doesn't recognize that Mapbox is installed.

The Fabric application uses a very different workflow than the CocoaPods-based instructions on the site. In fact, the CocoaPods-based workflow installs a dynamic framework, while the Mac app installs a static framework. Both workflows add a scripted onboarding step that CocoaPods itself doesn’t. The onboarding functionality is a bit opaque to me, but it’s probably not a good idea to combine the CocoaPods and Mac app installation methods.

[stcleezy]

I am at a total loss... I remove all references to Mapbox, reinstall, and I still get the same error. I've tried both the dynamic and static frameworks with the same result.

If I start a new project everything works fine, so I know it's some build / configuration setting.

Any additional guidance here?

[stcleezy]

I essentially started from scratch and removed all linked binaries, pods, etc. Re-installed everything and did a clean build, and now I am up and running. No clue what the actual root cause was here... hope nobody else has this issue!