WIP: Fix DB disconnects

Conversation 0 Commits 8 Files Changed 6

Author	SHA1	Message	Date
Matthew Raymer	fface30123	fix(platforms): include accountDid in settings retrieval for both platforms - Remove accountDid exclusion from settings object construction in CapacitorPlatformService - Remove accountDid exclusion from settings object construction in WebPlatformService - Ensure accountDid is included in retrieved settings for proper DID-specific configuration handling This change ensures that the accountDid field is properly included when retrieving settings for the active account, allowing for proper DID-specific configuration management across both Capacitor (mobile) and Web platforms. Files modified: - src/services/platforms/CapacitorPlatformService.ts - src/services/platforms/WebPlatformService.ts Timestamp: Wed Oct 8 03:05:45 PM UTC 2025	1 week ago
trentlarson	97b382451a	Merge branch 'master' into clean-db-disconnects	2 weeks ago
Matthew Raymer	7fd2c4e0c7	fix(AccountView): resolve stale registration status cache after identity creation - Add live registration verification to AccountView.initializeState() - When settings show unregistered but user has activeDid, verify with server - Use fetchEndorserRateLimits() matching HomeView's successful pattern - Update database and UI state immediately upon server confirmation - Eliminate need to navigate away/back to refresh registration status Technical details: - Condition: if (!this.isRegistered && this.activeDid) - Server check: fetchEndorserRateLimits(this.apiServer, this.axios, this.activeDid) - On success: $saveUserSettings({isRegistered: true}) + this.isRegistered = true - Graceful handling for actually unregistered users (expected behavior) Fixes issue where AccountView showed "Before you can publicly announce..." message immediately after User Zero identity creation, despite server confirming user was registered. Problem was Vue component state caching stale settings while database contained updated registration status. Resolves behavior reported in iOS testing: User had to navigate to HomeView and back to AccountView for registration status to update properly.	2 weeks ago
Matthew Raymer	20322789a2	fix(AccountView): resolve stale registration status cache after identity creation - Add live registration verification to AccountView.initializeState() - When settings show unregistered but user has activeDid, verify with server - Use fetchEndorserRateLimits() matching HomeView's successful pattern - Update database and UI state immediately upon server confirmation - Eliminate need to navigate away/back to refresh registration status Technical details: - Condition: if (!this.isRegistered && this.activeDid) - Server check: fetchEndorserRateLimits(this.apiServer, this.axios, this.activeDid) - On success: $saveUserSettings({isRegistered: true}) + this.isRegistered = true - Graceful handling for actually unregistered users (expected behavior) Fixes issue where AccountView showed "Before you can publicly announce..." message immediately after User Zero identity creation, despite server confirming user was registered. Problem was Vue component state caching stale settings while database contained updated registration status. Resolves behavior reported in iOS testing: User had to navigate to HomeView and back to AccountView for registration status to update properly.	2 weeks ago
Matthew Raymer	666bed0efd	refactor(services): align Capacitor and Web platform services with active_identity architecture - Update CapacitorPlatformService.updateDefaultSettings() to use active_identity table instead of hard-coded id=1 - Update CapacitorPlatformService.retrieveSettingsForActiveAccount() to query by accountDid from active_identity - Add getActiveIdentity() method to CapacitorPlatformService for consistency with WebPlatformService - Update WebPlatformService.retrieveSettingsForActiveAccount() to match CapacitorPlatformService pattern - Both services now consistently use active_identity table instead of legacy MASTER_SETTINGS_KEY approach - Maintains backward compatibility with databaseUtil.ts for PWA migration support Technical details: - CapacitorPlatformService: Fixed hard-coded WHERE id = 1 → WHERE accountDid = ? - WebPlatformService: Fixed retrieval pattern to match new architecture - Platform services now aligned with migration 004 active_identity table schema - databaseUtil.ts remains unchanged for PWA-to-SQLite migration bridge	2 weeks ago
Matthew Raymer	7432525f4c	refactor(services): align Capacitor and Web platform services with active_identity architecture - Update CapacitorPlatformService.updateDefaultSettings() to use active_identity table instead of hard-coded id=1 - Update CapacitorPlatformService.retrieveSettingsForActiveAccount() to query by accountDid from active_identity - Add getActiveIdentity() method to CapacitorPlatformService for consistency with WebPlatformService - Update WebPlatformService.retrieveSettingsForActiveAccount() to match CapacitorPlatformService pattern - Both services now consistently use active_identity table instead of legacy MASTER_SETTINGS_KEY approach - Maintains backward compatibility with databaseUtil.ts for PWA migration support Technical details: - CapacitorPlatformService: Fixed hard-coded WHERE id = 1 → WHERE accountDid = ? - WebPlatformService: Fixed retrieval pattern to match new architecture - Platform services now aligned with migration 004 active_identity table schema - databaseUtil.ts remains unchanged for PWA-to-SQLite migration bridge	2 weeks ago
Trent Larson	530cddfab0	fix: linting	3 weeks ago
Trent Larson	5340c00ae2	fix: remove the duplicate settings for user 0, remove other user-0-specific code, enhance errors	3 weeks ago

WIP: Fix DB disconnects #204

8 Commits