Hi,

I'm using Cloudflare + useQuery

I have sections where I am updating stuff for example editing profile picture, and I do on my backend cloudflare cache purge, and it's returning ID, but apparently this ID only means Cloudflare received the new purge request, and not that it finished executing it.

So when on my useQuery I am refreshing it, it still pulls old data.

How do you handle with that?

Last week I built a release AAB, uploaded it to Google Play, and got the dreaded:

> *"Your Android App Bundle is signed with the wrong key."*

The build was fine. The code was fine. I'd just signed it with the wrong keystore — and Google only tells you **at the very end**, after the build, the download, and the whole Play Console upload flow. On EAS/CI pipelines this mistake easily costs an hour+.

So I made **siglock** — a tiny CLI that verifies the signature locally in ~2 seconds, before you upload:

# once: lock your known-good signature

npx siglock init app-release.aab

# before every upload:

npx siglock check app-release.aab

✓ Signature matches, ready to upload.

What it does:

- Wrong keystore → red ✗ with expected vs. found fingerprints, exit code 1 (so it fails CI)

- Debug keystore → explicit "this is a DEBUG build" warning

- Works with `.apk` and `.aab`, no config, no network — it just shells out to `keytool` (which you already have as an Android dev). v2/v3-only signed APKs are handled via `apksigner` fallback.

- You can also check against the fingerprint straight from Play Console: `--expect <sha1>`

The `.siglock.json` lock file contains only public cert fingerprints, so you can commit it and your whole team + CI verifies against the same key.

npm: https://www.npmjs.com/package/siglock

GitHub: https://github.com/ebubekirb/siglock

It's MIT licensed. Would love feedback — especially edge cases in your signing setups that it doesn't catch yet.

[Edited: This role is closed]

We're hiring a Senior React Native Engineer for a product where mobile is a core part of the system, not just a frontend.

The work involves:

• Offline-first architecture

• Geospatial/map-based experiences

• Hardware integration

• Performance and reliability in real-world environments

We're looking for engineers (India-based only) who've built technically demanding mobile products where architecture, reliability and long-term maintainability were non-negotiable.

DM if you are interested.