Hawken Rives

For instance, events with categories: ```bash curl https://wp.stolaf.edu/calendar/wp-json/tribe/events/v1/events ``` ```http HTTP/1.1 200 OK Access-Control-Allow-Headers: Authorization, Content-Type Access-Control-Expose-Headers: X-WP-Total, X-WP-TotalPages Allow: GET Cache-Control: max-age=0, public Connection: Keep-Alive Content-Encoding: gzip Content-Length: 4711...

I don't necessarily want to apply it above react-navigation; I'm nervous about having two of them in the component tree. And react-navigation applies theirs successfully, as you can see in...

Took a stab at wrapping a view in SafeAreaView… let's just say that it's a little _too_ safe for this spot.

If I put the SafeAreaView _inside_ the ScrollView, it works! I'm on to other views now.

I've pushed to the `safelayoutview` branch, which fixes the homescreen, but I would like to find a better solution than adding SafeAreaView to each spot individually.

I think that we'll need to add `` and `contentInsetAdjustmentBehavior="automatic"` pretty much everywhere. I don't know of a better way to handle it. as to why `contentInsetAdjustmentBehavior` is "never" by...

I need to learn more about how iOS proper handles `contentInsetAdjustmentBehavior` before I can understand how this works, because it doesn't make sense to me. I can get the bottom...

After discussing this with @drewvolz, we've decided that (given that neither of us really has any idea how to fix this right now) 2.5 is in enough of a better...

Yeah… for example, the Dictionary list doesn't respect the safe area at the bottom of the view / bottom of the screen.

I've just updated the OP's checklist with what I know works (two items). A number of others "work", but only because they're in tab views.