Jason Wray

I can confirm that Japanese characters won't input — OS X 10.8.2 (Kotoeri) using Chrome 25.0.1364.99 beta. As you said, yairEO, pasting works just fine, but typing fails to display...

It seems this bug has to do with the IME not reporting a real character code, so there's nothing to convert and add to the display element. When you're typing...

Ditto—new fork still doesn't handle Japanese character conversion (roman-kanji or kana-kanji) on iOS 6, Safari or Chrome. Thanks for the effort, though!

@Navideck-fotis Are you using the static library or CocoaPods?

Ah, my old nemesis: CocoaPods. (Why doesn't anyone post what version of CocoaPods they are using? :crying_cat_face:)

Not entirely dead. ;) I can't replicate this performance issue, though. Testing on [1.6.1 in mapbox-ios-example](https://github.com/mapbox/mapbox-ios-example/commit/0a0a744351fadd095611817fd63ee7b9d3b04397) with a 20MB `.mbtiles`, tile loading seems reasonably performant — better than [1.4.1](https://github.com/mapbox/mapbox-ios-example/commit/173354dfabe83f1f9034231ee63fb5b35dd9e08e), I...

You might try dropping your `.mbtiles` file into the [demo app](https://github.com/mapbox/mapbox-ios-example) and seeing if performance is still poor.

You might try [`RMTileSource.latitudeLongitudeBoundingBox`](https://www.mapbox.com/mapbox-ios-sdk/api/Protocols/RMTileSource.html#//api/name/latitudeLongitudeBoundingBox) and then set the map constraints based on the result.

Going to punt on this for v3.2.0 in favor of linking to the raw ios-app code from the simple offline pack example.

This seems to manifest in a few different ways, but always with the UI test application dying: https://app.bitrise.io/build/2d5a7b9eb9084967 from #352 ``` t = 110.00s Add a line style layer from...