Opened RDM today and when attempting to edit an entry, nothing happens and eventually an app crash window appears. Tried building a new application support folder, re-installing the app, but no change.
Hello,
Thank you for reaching out to us regarding this,
Could you please specify the version of RDM you are currently using?
What type of data source are you using?
Additionally, can you confirm which version of Mac OS you are on?
Let me know,
Best regards,
Samuel Dery
MaOS 15.6.1
Devolutions Personal Hub
RDM Ver: 2025.2.12.2
thank you
Hello,
Thank you for the follow-up.
Unfortunately, the current macOS beta version is causing instability with RDM Mac. This appears to be related to changes introduced in the beta, and our development team is working on a fix to address the issue.
We apologize for the inconvenience and appreciate your understanding.
Best regards,
Jacob Lafrenière
With all due respect, macOS 15.6.1 is official release, not beta.
FYI, I removed RDM 2025.2.12.2 and then installed 2025.2.11.0 and can edit again. I can't confirm 2025.2.12.2 is incompatabile with macOS 15.6.1 but it is not working with my installation 15.6.1
Hello,
Apologies for the confusion, it seems my research was inaccurate.
I’ll verify the details with the development team and get back to you as soon as possible.
Best regards,
Jacob Lafrenière
Hello,
I'm following up sooner than expected.
I've heard back from the development team, they’ve confirmed a known issue in the latest version of RDM that causes crashes when editing or creating Telnet entries.
Could you please confirm whether the crashes you're experiencing are limited to Telnet entries, or if they occur with other entry types as well?
I look forward to your response.
Best regards,
Jacob Lafrenière
It was while attempting to edit/create telnet entries. Since I have a working setup, I will try to pull out non-production or virtualized mac to test and report back
Hello,
Thank you for the follow-up.
This is likely the issue the Development team was referring to. Could you please confirm if you're observing the same behavior?
Please also note that we are actively working on a fix, which will be included in a future version.
Best regards,
Jacob Lafrenière