WIP: Fix DB disconnects

Conversation 0 Commits 8 Files Changed 6

trentlarson commented 3 weeks ago

Owner

Remove duplicate settings for User 0
Remove other User-0-specific logic

trentlarson added 1 commit 3 weeks ago

5340c00ae2 fix: remove the duplicate settings for user 0, remove other user-0-specific code, enhance errors

trentlarson added 1 commit 3 weeks ago

530cddfab0 fix: linting

anomalist added 2 commits 2 weeks ago

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

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

anomalist added 1 commit 2 weeks ago

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.

anomalist added 1 commit 2 weeks ago

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.

trentlarson reviewed 2 weeks ago

src/services/platforms/CapacitorPlatformService.ts Outdated

												
					        if (column !== "id") {
				
					          // Exclude the id column

					        if (column !== "id" && column !== "accountDid") {
				
					          // Exclude the id and accountDid columns

trentlarson commented 2 weeks ago

Poster

Owner

Why exclude the accountDid column? That seems useful. (By returning that, callers can use it to set the activeDid and we can potentially eliminate some other outside calls to get the active account DID.)

Same thing in WebPlatformService

anomalist commented 2 weeks ago

Poster

Owner

I was being a little too cautious and holding to the old pattern of how it was done in Dexie and with the MASTER settings.

You are correct and that's a righteous change!

trentlarson added 1 commit 2 weeks ago

97b382451a Merge branch 'master' into clean-db-disconnects

anomalist added 1 commit 1 week ago

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

This pull request has changes conflicting with the target branch.

src/libs/endorserServer.ts

src/views/AccountViewView.vue

Sign in to join this conversation.

No reviewers

No Label

No Milestone

No Assignees

2 Participants

Notifications

Due Date

No due date set.

Dependencies

This pull request currently doesn't have any dependencies.

WIP: Fix DB disconnects #204