This article is an English translation of the original Japanese article.
When a user taps a push notification, the entry point differs depending on whether the app is running. If you only use one listener with Expo Router to navigate to the notification target screen, you may miss launches from the terminated state.
In my app, I handle both cases with two separate mechanisms:
Key takeaways
Source: https://github.com/carlosge492/app-generation-microservice (MIT)
Building a pipeline that generates Flutter apps from a spec, with an automated repair loop for whatever flutter analyze catches. The bug that actually cost money: a ConsumerState class with build(BuildContext context,...
WordPress's plugin and theme update screens both have a "select all" checkbox. Calling check() on it with Playwright succeeds — no error, no exception. But look at the individual checkboxes afterward, and sometimes none of them are actually checked.
Note: Playwright's
check()ticks a checkbox. The click itself can succeed even if the page's JavaScr...
Use a durable idempotency receipt when feature flag retries can reach a rollout toggle endpoint, otherwise reach for a read-only flag evaluation that cannot create duplicate writes. Short answer: the backend must bind one caller-generated key to one operation and commit the receipt beside the state change; a retry should recover that recorded result, not perform the write again.
The fla...
Every developer knows the drill for production systems: define your RTO and RPO, replicate your data, script your failover, test it before you need it. It's second nature by now.
But most of us never apply that same thinking to the one system we depend on every single day to do that work — our home office. A power outage, a dead router, or a cut internet line can take you offli...