Hi there! I see you’re experiencing a CORS (Cross-Origin Resource Sharing) policy error when using the web version of Wire Secure Messenger, while the mobile version works fine. To help you better, could you tell me a bit more about when the error occurs? For example:
- Are you trying to log in, send messages, or access certain features?
- Do you see the error in the browser console or as a visible message on the page?
- Which browser are you using on your Mac with OS X 10.15.7?

Understanding these details will help me tailor the solution for you. Meanwhile, I can guide you through some common steps to address CORS issues on web apps:

1. Clear Browser Cache and Cookies
Sometimes outdated cached files can cause CORS conflicts. Clearing cache and cookies can refresh the security tokens used for cross-origin requests.

2. Check Browser Extensions
Some extensions might interfere with requests or headers. Try disabling extensions temporarily to see if the error persists.

3. Try Another Browser
Since you’re on a Mac with OS X Catalina, browsers like Safari, Chrome, or Firefox should work well. Testing on another browser isolates whether it’s a browser-specific issue.

4. Verify Network and Firewall Settings
Some network-level restrictions or firewall settings (especially corporate networks) might block or alter headers in a way that causes CORS errors.

5. Look for Server-Side Issues
Since the mobile app works fine, the backend likely supports your account. However, the web server might need proper CORS headers configured to allow requests from your browser’s origin. This is something Wire’s server admins would handle if it’s a systemic problem.

If you’re developing or self-hosting Wire’s web client or integrating with its API, you might need to ensure the server responds with appropriate headers like:
Access-Control-Allow-Origin: * or your specific domain.

If none of these initial checks help, there are advanced options like using browser CORS extensions to bypass the policy temporarily for testing, but these are not permanent solutions for security reasons.

Please let me know the extra details about your situation, and I’ll help you troubleshoot further! Are you satisfied with this initial guidance?