Rita Onslow

Plenty of projects do end up there and it is a legitimate place to be. But it means you now hand-merge every native change at each SDK bump, forever, and that is a recurring cost rather than a saved afternoon. Recommending it to someone on their first app as the shortcut undersells what they are signing up for.

Probably not, for one line. Work down this list:

1. Is it already an app.json field? Permissions, intent filters, a lot of common manifest keys are exposed directly and people write plugins for things that were one config key away.
2. Can expo-build-properties do it? It covers a surprising amount of the Gradle and manifest surface.
3. Only then write a plugin.

And if you do get to step 3, a plugin for one manifest attribute is about fifteen lines with withAndroidManifest. It is a function that takes config, mutates a parsed object, returns config. Not a mountain.

The thing you must not do is edit android/AndroidManifest.xml by hand, because the next prebuild regenerates it and your line silently disappears. You will not notice at the time. You will notice on a build three weeks later when the SDK stops working and nothing in your diff explains it.

If the budget stretches, a small three quart as a second machine is more useful than going bigger. Two people, a weekday side dish or a small batch of beans, and it lives in a much easier cupboard. Mine gets used more than the big one does.

One thing that surprised me: the film is harmless. It looks like something failed to get clean but it is just minerals. I stopped worrying about it on everyday glasses and only bother with the vinegar rinse when people are coming over.

Same, three and a half years here. The one thing that did change was dust in the vent slots. Blow it out once a year and it goes back to where it started.

The fan is the tip that actually worked for me. Left one on low pointed across the bare mattress while I was at work for three days and the smell dropped off a cliff.