Troubleshooting

Here are solutions to common issues when using ULDA. These assume you're using the library with a valid API key and the default apiUrl (https://api.0am.ch).

• Issue: "Invalid API Key" error when initializing Ulda
  Solution: Verify your API key from 0 AM Admin Portal. Ensure it's correctly passed to new Ulda(apiKey, apiUrl, dev). Check for typos or expired keys.

• Issue: "Master file name already exists" when calling createMasterFile
  Solution: Master file names must be unique per API key. Use a different name or check existing master files with the master:get WebSocket event.

• Issue: "Content file name already exists" when calling createContentFile
  Solution: Content file names must be unique within a master file. Choose a unique name or delete the existing content file using ulda.data[name].delete().

• Issue: WebSocket events (e.g., content:update) not triggering
  Solution: Ensure a stable internet connection and correct apiUrl. Verify you've set up listeners (e.g., connectToUpdateContentFile). Check server logs in dev mode (dev: true) for errors.

• Issue: "Error updating file" after calling changeMasterFilePassword
  Solution: After changing the password, reconnect using ulda.connect(masterFileName, newPassword). Ensure the new password is valid and meets security requirements.

• Issue: ULDA methods return { status: false, error: 'Invalid Host' }
  Solution: The server checks the request's origin. Ensure your client's origin matches the allowed CORS settings ( default: *). Contact support if the issue persists.

For unresolved issues, see the Contact Information section.