Hey there Jens, and thanks for the help! It was my very, very silly mistake. I originally emitted said key, but in a desperate attempt to get it to to work, I tried emitting different values. It turns out I wasn't really do the right type of bounding box. The geoJSON I created from geojson.io has the lat/long swapped from the normal order. So, since I trying to set the lat/long from that data, my tap was looking for some strange place in Antarctica that, of course, has no objects drawn there.. oh my. Swapping the bounding box coordinates was the fix.
-- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/e01cb8ae-eeee-4ec7-a448-4ea184d50eae%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
