# Developing on the mobile version of Discourse **URL:** https://meta.discourse.org/t/developing-on-the-mobile-version-of-discourse/216643 **Category:** Development **Created:** [January 31, 2022, 10:55pm UTC](https://meta.discourse.org/t/developing-on-the-mobile-version-of-discourse/216643 "2022-01-31T22:55:25Z") **Posts on this page:** 1 **Showing post:** 5
### Author: ![tubignaaso](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tubignaaso/32/94674_2.png) [@tubignaaso](https://meta.discourse.org/u/tubignaaso) #### Post date: [February 4, 2022, 6:17pm UTC](https://meta.discourse.org/t/developing-on-the-mobile-version-of-discourse/216643/5 "2022-02-04T18:17:51Z")
After doing some digging through the source, I found two environment variables that help: - `PRINT_EXCEPTIONS` - shows _all_ exceptions, maybe too noisy to be valuable but it helped - `RAILS_LOGS_STDOUT` - logs everything to console which is what I was looking for above These helped confirm that there wasn’t an error occurring within Rails nor my theme’s SCSS. Apparently there was some gzip component stuck between ember and Rails. I’m not sure how this got there, but when the headers `Content-Encoding` exists, [this particular line](https://github.com/discourse/discourse/blob/v2.7.13/app/assets/javascripts/discourse/lib/bootstrap-json/index.js#L205) was copying that over and causing the browser (and curl) to just ignore the entire response body (presumably because it was no longer encoded in gzip). It looks like this has been [fixed in 2.9.0.beta1](https://github.com/discourse/discourse/commit/3172e08b6d17e82c09b4524394ea5e95ee301616) but I am running 2.7.13. Removing the gzip component in development fixed the issue for my particular version, but it looks like it’ll work fine with gzip in the future. Not sure why the desktop version didn’t exhibit the same issue. Hopefully this helps anyone else facing similar issues. --- _[View the full topic](https://meta.discourse.org/t/developing-on-the-mobile-version-of-discourse/216643)._