Updated scripts/common.sh to set appropriate API server endpoints based on build mode:
- Development: localhost:3000 for Endorser API, production for Image/Partner APIs
- Test: test-api.endorser.ch for Endorser API, production for Image/Partner APIs
- Production: All production endpoints
This ensures mobile builds use correct API endpoints for each environment
while keeping Image and Partner APIs on production servers for dev/test.
- Fix aria-hidden conflict on trash can icon by wrapping in proper button element
- Fix image deletion API endpoint by extracting image ID from full URL
- Improve 404 error handling to clear local image reference when image already deleted
- Resolve accessibility warning and prevent invalid API calls
- Add user-specific settings save to onClickSaveApiServer() method
- Ensures API server changes persist for current user account
- Aligns with pattern used by other server settings (partner, push)
- Resolves issue where claim server changes weren't "sticking"
Fix ClaimView component to use $accountSettings() instead of $settings() to
get the current user's registration status. This resolves the issue where
User #0 appeared unregistered in ClaimView despite having isRegistered: true
in the database.
- Changed created() method to use $accountSettings() for user-specific settings
- Ensures ClaimView reads correct isRegistered value for current user
- Fixes "You posted that. false" display issue for registered users
Add comprehensive breakdown of the --headed test debugging command, explaining each parameter and its purpose for visual test debugging. Resolves "New offers for another user" test debugging workflow.
- Extract test user data (seed phrases, DIDs, usernames) from importUser into separate getTestUserData function
- Refactor importUser to use getTestUserData internally, maintaining backward compatibility
- Update "New offers for another user" test to use new getTestUserData function
- Replace hardcoded seed phrase with programmatic retrieval using getTestUserData('00')
- Add proper TypeScript type annotations to array functions in testUtils
- Improve test maintainability by centralizing test user data management
This allows tests to access user data without executing import flow, providing more flexibility for test scenarios.
Remove duplicate APP_SERVER imports in ContactsView.vue and ClaimView.vue that were causing compilation errors during testing. The duplicate imports occurred when both files had APP_SERVER imported from constants/app and also assigned as class properties.
- ContactsView.vue: Remove duplicate import, keep class property assignment
- ClaimView.vue: Remove duplicate import, keep class property assignment
- Fixes Vite compilation errors that were blocking test execution
- 33/38 tests now pass successfully
This resolves the "Identifier 'APP_SERVER' has already been declared" errors that were preventing the development server from running properly.
- Add capacitor-assets.config.json for cross-platform asset generation
- Create resources/ directory structure for source assets
- Update .gitignore to exclude generated Android assets and resources
- Remove 30+ generated files from source control
- Add comprehensive asset management documentation
- Add Gradle cache exclusions to .gitignore
- Verify asset generation works with new configuration
Assets are now properly managed: source files in version control,
generated files excluded, and build process handles platform-specific
asset generation automatically. Repository size reduced and history
cleaned up.
- Add capacitor-assets.config.json for cross-platform asset generation
- Create resources/ directory structure for source assets
- Update .gitignore to exclude generated Android assets and resources
- Remove 30+ generated files from source control
- Add comprehensive asset management documentation
- Verify asset generation works with new configuration
Assets are now properly managed: source files in version control,
generated files excluded, and build process handles platform-specific
asset generation automatically.
- Add capacitor-assets.config.json for cross-platform asset generation
- Create resources/ directory structure for source assets
- Update .gitignore to exclude generated Android assets and resources
- Remove 30+ generated files from source control
- Add comprehensive asset management documentation
- Verify asset generation works with new configuration
Assets are now properly managed: source files in version control,
generated files excluded, and build process handles platform-specific
asset generation automatically.
- Remove redundant specific file patterns inside android/app/build/
- Fix misleading comment that suggested build artifacts were source configs
- Simplify configuration by relying on broader android/app/build/ rule
- Improve maintainability and reduce confusion in .gitignore
The specific file patterns were unnecessary since android/app/build/ already
covers all build artifacts. This eliminates redundant rules and clarifies
that these are generated build files, not source configuration files.
- Remove redundant specific file patterns inside android/app/build/
- Fix misleading comment that suggested build artifacts were source configs
- Simplify configuration by relying on broader android/app/build/ rule
- Improve maintainability and reduce confusion in .gitignore
The specific file patterns were unnecessary since android/app/build/ already
covers all build artifacts. This eliminates redundant rules and clarifies
that these are generated build files, not source configuration files.
Trent Larson
Jose Olarte III
Matthew Raymer
Matthew Raymer