[chrisbo]

I updated to MacOS Catalina last night and now this morning my Runemate can no longer find any OSRS clients. When I click the button to start the clients it succesfully launches a new client, but clicking refresh doesn't do anything.
I uninstalled the normal installer, OSRS client and deleted the standalone client.
I deleted the caches of both.
I reinstalled the installer to see if it would update Java automatically and I also manually updated Java.
I did the trick on the OSRS application again after reinstalling to remove the line of code from the info.plist file.

Not sure what else to try.

 

[ketske]

Here same problem.
 
Same problem still exists. Any idea guys?

 

[hpang]

think its due to the new privacy settings need prior authorisation

 

[changedusername]

Same issue here. I’ll do some tests on a test machine in the morning and let people know.
 
Tested all ways I could think of and nothing works. Could the client developer shed some light on this, please?
 
Bump. I reached out to RM via email. No response.

 

[mallan]

think its due to the new privacy settings need prior authorisation

Could you please clarify which a) which privacy settings b) how they can be changed

 

[mirus]

I just updated to macOS Catalina too. Legacy client opens fine but the bot doesn't detect that it's up. No error message.

Any updates?

 

[changedusername]

No updates as of yet, unfortunately.
 

think its due to the new privacy settings need prior authorisation

Could you please clarify which a) which privacy settings b) how they can be changed

This isn't the case, disregard Hpang's comment.
 
No updates as of yet, unfortunately.

 

[vallemarie]

I got the same problem here.

I asked about the problem in the discord group but nobody could help me

 

[korte smee]

Any updates lads?

 

[arbiter]

We are looking into it now. Can you post your logs? Help > View Logs. @Korte Smee

 

[cloud]

We believe this issue has been resolved based on the testing we did.

 

[korte smee]

We believe this issue has been resolved based on the testing we did.

It runs perfectly again! Thanks!

 

[joe anderson]

I am experiencing this issue, please help.