Skip to content

fix(fuzeclock): HTTPS load + spinner-first loader UX - #42

Merged
izzywdev merged 1 commit into
masterfrom
fix/fuzeclock-load
Jun 18, 2026
Merged

fix(fuzeclock): HTTPS load + spinner-first loader UX#42
izzywdev merged 1 commit into
masterfrom
fix/fuzeclock-load

Conversation

@izzywdev

Copy link
Copy Markdown
Owner

FuzeClock failed→spinner→failed. Fixed the loader to show the spinner first (no premature 'not found' before the app list loads), and fixed the actual load failure (mixed content): clock served over trusted TLS, clock-app built with an https base, remote_url registered as https. Verified remoteEntry returns 200 over https with the local-CA cert.

🤖 Generated with Claude Code

Clicking FuzeClock failed, briefly showed a spinner, then failed again. Two bugs:

- FederatedAppLoader flashed a "not found" error before the app list had loaded
  (deep-link/refresh: state.apps empty), then re-ran and hit the real failure.
  Now it stays on the spinner while the app list is loading and only errors once
  the list is loaded and the app is genuinely missing.
- The federated remote was mixed-content: registered as http://clock.dev.local
  on the https FuzeFront page, and clock-app was built with an http public base.
  Serve clock over trusted TLS (cert-manager local CA on the clock ingress),
  build clock-app with an https base, and register remote_url as
  https://clock.dev.local/assets. (clock.dev.local added to hosts.)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@izzywdev
izzywdev merged commit 6b300bd into master Jun 18, 2026
@izzywdev
izzywdev deleted the fix/fuzeclock-load branch June 18, 2026 06:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant