Hi @Chester_Jansen,
I want to sincerely apologize for the frustration and inconvenience you’re experiencing. We understand how important this is and deeply appreciate your patience while we work to resolve the issue.
We’ve created a ticket for our development team to investigate your case. While I can’t provide an exact timeline, I assure you that your feedback and details have been forwarded to the right team. We’ll keep you updated and let you know as soon as we have any next steps or progress to share.
Thank you again for bearing with us, and please don’t hesitate to reach out if you have additional details or questions in the meantime. We’re here to help!
Hi @Chester_Jansen,
I wanted to follow up on our earlier message with some additional updates and a request from our developers. We’ve made progress and were able to reproduce the issue on our end, which means we’re one step closer to identifying a solution.
To help us refine our findings and confirm any potential fixes, the team has asked for the RAATServer logs from your Mac remote. These logs will be crucial for cross-verifying what we’ve observed.
Here’s how you can grab them:
Open Finder on your Mac remote and navigate to: ~/Library/RAATServer/Logs/
Your assistance is making a significant difference in resolving this, and we’re grateful for your collaboration. Once we have the logs, we’ll move quickly to analyze them and share the next steps.
Thank you again for sticking with us—we’ll keep you updated as we continue to make progress!