Adam Gerthel

> I am also facing the same issue. At runtime the env variables are undefined. I suggest that you, if possible, start using env files according to [this](https://github.com/bkeepers/dotenv/blob/c6e583a/README.md#what-other-env-files-can-i-use).

> Would be very practical to allow for custom env files if possible. In our case, we have a **staging** environment for which we'd like to have a `.env.staging` but...

@CalMlynarczyk it seems your example has become outdated. `Tracing.Integrations.Express` is deprecated in `@sentry/tracing`. But even without that, it seems that only my first request to the server works after adding...

@zackdotcomputer wouldn't it be better if @hardydex gave you ([travelerdev](https://github.com/travelerdev)?) ownership or co-ownership of this repository? I wouldn't mind helping out on a specific issue, but I'm also very hesitant...

@rasmuslelumees I ended up using Expo-AV instead (can be used in the "bare" workflow if you have Expo unimodules installed). It hasn't been without issues either but it's been more...

@daffl I've read that too somewhere, but it doesn't! I've tried every possible way/setting/option.

Yep, I totally get that. Will see if I get time to throw together a small repro repo.

This seems a bit excessive: Fig settings all: ``` autocomplete.fuzzySearch = false integrations.hyper.disabled = true integrations.iterm.disabled = true integrations.vscode.disabled = true ``` Fig diagnostics: ``` fig-details: - 2.16.0 hardware-info: -...

As Fig seems abandoned, I've switched to Warp.

> @AdamGerthel I’ve been pretty inactive in these issues because I no longer work for Fig, but I can tell you with 100% certainty that it is not abandoned! Brendan...