h14h.com / glide

0

Effortlessly glide through your todos

0

glide / docs /

at main 3 folders 1 file

h14h.com Make sandbox build+submit a one-liner 3d ago

Document why Android widgets are blocked upstream expo-widgets ships no working Android widget in any published version — verified against the pinned 56.0.22 and the latest 57.0.6. The Glance widget renders a hardcoded Text(widgetName), Android's WidgetsModule declares no Widget object or updateTimeline, and the JS side resolves to a no-op stub, so there is no renderer and no JS -> native data path. Records the files and versions checked so this isn't re-investigated, flags which files signal that upstream has landed (the changelog doesn't announce it), and warns off enableAndroid: true, which only makes the placeholder installable. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

4 days ago

Add initial docs

1 month ago

Make sandbox build+submit a one-liner `eas submit --profile sandbox` resolved the production identity: submit profiles have no `env` block and `eas submit` has no --environment flag, so GLIDE_APP_VARIANT never reached app.config.js and EAS looked up credentials for com.h14h.glide. It surfaced as "credentials cannot be set up in --non-interactive mode" — a wrong-app error that reads like a missing- credentials one. scripts/ship-sandbox.sh exports the variant and wraps both halves. It is a shell script rather than a package.json entry on purpose: the `scripts` field of package.json is a fingerprint input, so adding one there would change every runtime version and cut installed builds off from OTAs. The script also repairs a footgun it takes a failed build to diagnose. A local `expo run:android` makes AGP strip the legacy `package=` attribute from masked-view's AndroidManifest.xml in place; bun hardlinks node_modules out of its global cache, so the edit poisons the cache, spreads to every worktree, and survives a clean reinstall. masked-view is autolinked via expo-router and so is a fingerprint input — builds then die in CONFIGURE_EXPO_UPDATES naming no file. The repair writes through the existing inode so the cache is fixed too. Also correct the setup checklist: Play submission is verified working; iOS is blocked only on an App Store Connect API key, which needs one interactive run. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

3 days ago

Make sandbox build+submit a one-liner `eas submit --profile sandbox` resolved the production identity: submit profiles have no `env` block and `eas submit` has no --environment flag, so GLIDE_APP_VARIANT never reached app.config.js and EAS looked up credentials for com.h14h.glide. It surfaced as "credentials cannot be set up in --non-interactive mode" — a wrong-app error that reads like a missing- credentials one. scripts/ship-sandbox.sh exports the variant and wraps both halves. It is a shell script rather than a package.json entry on purpose: the `scripts` field of package.json is a fingerprint input, so adding one there would change every runtime version and cut installed builds off from OTAs. The script also repairs a footgun it takes a failed build to diagnose. A local `expo run:android` makes AGP strip the legacy `package=` attribute from masked-view's AndroidManifest.xml in place; bun hardlinks node_modules out of its global cache, so the edit poisons the cache, spreads to every worktree, and survives a clean reinstall. masked-view is autolinked via expo-router and so is a fingerprint input — builds then die in CONFIGURE_EXPO_UPDATES naming no file. The repair writes through the existing inode so the cache is fixed too. Also correct the setup checklist: Play submission is verified working; iOS is blocked only on an App Store Connect API key, which needs one interactive run. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

3 days ago

README.md

Docs#

Refer to these docs for additional context about Glide.

It is organized by directories, each of which have a root README.md explaining the docs in more detail.

Directories are briefly described below. Use these descriptions to decide whether to read further.

Prior Work#

Original works that served as inspiration for Glide.

Path: docs/prior-work/README.md

Engineering#

Implementation notes for subsystems with non-obvious behaviour — read these before changing the home-screen widget or the Liquid Glass surfaces.

Path: docs/engineering/README.md

Release#

Environment model (development / sandbox / production), CI/CD workflows, and release process — plus dashboard setup and end-to-end submission runbooks.

Path: docs/release/environments.md — start here: environments, accounts, CI/CD, release flow
Path: docs/release/app-store.md — App Store dashboard runbook for the production app