Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

13.5 – Location privacy broken

luckman212 said:
2-3 years is nothing. How about this annoying Contacts bug that's 5 years old and counting, with no sign of a fix in sight.
Click to expand...
As said I'd far rather Apple focused on stability & fixing issues, however more tricks and bells are seemingly the order of the day. At the current pace it's clear many issues will be ignored and has been for some time :(

Same with Location Services if not wide reaching or publicly shamed Apple is unlikely to react in a timely manner if at all. I've tried all options I can think of short of wiping the drive and starting from scratch, even then who knows...

TBH user feedback is pointless without Apple reacting beyond canned responses...

Q-6
 
  • Like
Reactions: Pinkyyy 💜🍎
Queen6 said:
As said I'd far rather Apple focused on stability & fixing issues, however more tricks and bells are seemingly the order of the day. At the current pace it's clear many issues will be ignored and has been for some time :(

Same with Location Services if not wide reaching or publicly shamed Apple is unlikely to react in a timely manner if at all. I've tried all options I can think of short of wiping the drive and starting from scratch, even then who knows...

TBH user feedback is pointless without Apple reacting beyond canned responses...

Q-6
Click to expand...

When I contacted support they had me add a new user and boot into safe mode. It made no difference.

I honestly believe everyone should call in to support. This makes them spend the time on the issue. I just picked the chat option. The whole interaction was done in 10 minutes.

You can even say you already tried whatever they recommend. Or just do something else, pretending to try it. Whatever it takes to make them pay attention. The feedback website is probably useless; they can just ignore things.

The more I think about it, the more I'm annoyed that MacRumors doesn't help with the Apple shaming more by posting articles about obvious, critical bugs.
 
  • Like
Reactions: Queen6, katbel and Pinkyyy 💜🍎
svenmany said:
When I contacted support they had me add a new user and boot into safe mode. It made no difference.

I honestly believe everyone should call in to support. This makes them spend the time on the issue. I just picked the chat option. The whole interaction was done in 10 minutes.

You can even say you already tried whatever they recommend. Or just do something else, pretending to try it. Whatever it takes to make them pay attention. The feedback website is probably useless; they can just ignore things.

The more I think about it, the more I'm annoyed that MacRumors doesn't help with the Apple shaming more by posting articles about obvious, critical bugs.
Click to expand...
I've already reported the issue, rest is down to Apple. Just waiting to see. If no fix on Ventura either rollback to Monterey or advance to Sonoma. Apple is flogging to death it's stance on privacy & security so I would like to think this is a priority fix. As ever time will tell...

Q-6
 
svenmany said:
I'm kind of surprised that this website hasn't done a front-page article on this issue.

I do check System Settings, looking for updates in the Software Update section. All mine says is "Your mac is up to date and horribly broken".
Click to expand...
Exactly what I was thinking ! It’s very strange how MacRumors didn’t post any articles reporting this bug, when it’s clearly not a small one.
But I’m still hoping Apple is working on it and will be fixing this issue as soon as possible. It doesn’t seem to be an issue in Sonoma, so I have a feeling Apple will eventually fix it. Though it does need to be fixed in a Ventura release because clearly there are older Macs that will not be getting the Sonoma update.
 
  • Like
Reactions: katbel, TheYayAreaLiving 🎗️, SFjohn and 3 others
svenmany said:
When I contacted support they had me add a new user and boot into safe mode. It made no difference.

I honestly believe everyone should call in to support. This makes them spend the time on the issue. I just picked the chat option. The whole interaction was done in 10 minutes.

You can even say you already tried whatever they recommend. Or just do something else, pretending to try it. Whatever it takes to make them pay attention. The feedback website is probably useless; they can just ignore things.

The more I think about it, the more I'm annoyed that MacRumors doesn't help with the Apple shaming more by posting articles about obvious, critical bugs.
Click to expand...
Not even sure why they tried. They are aware of this being an issue. Unless the rep you spoke to doesn't bother to check reported / existing issues, sounds like they were just appearing to troubleshoot a known software bug with no workaround or fix at the moment.
 
dannyzx said:
Not even sure why they tried. They are aware of this being an issue. Unless the rep you spoke to doesn't bother to check reported / existing issues, sounds like they were just appearing to troubleshoot a known software bug with no workaround or fix at the moment.
Click to expand...

He immediately said that Apple was aware of the problem. I guess he was hoping to help me, since we know that not everyone is affected by it. It was only after he saw that safe booting didn't help, that he escalated my case to add to the list of people reporting the problem. They really have to make sure that third-party software is not the cause of problem.

I would love to hear from some MacRumors moderator regarding why this serious issue hasn't received a front-page article. Apple will never get better without more widespread visibility of their failures. Certainly it would be a significant service to this community.
 
  • Like
Reactions: katbel, pmcjr, gilby101 and 3 others
svenmany said:
He immediately said that Apple was aware of the problem. I guess he was hoping to help me, since we know that not everyone is affected by it. It was only after he saw that safe booting didn't help, that he escalated my case to add to the list of people reporting the problem. They really have to make sure that third-party software is not the cause of problem.

I would love to hear from some MacRumors moderator regarding why this serious issue hasn't received a front-page article. Apple will never get better without more widespread visibility of their failures. Certainly it would be a significant service to this community.
Click to expand...
I'm personally surprised as well that this wasn't an article. Still not fixed by Apple.
 
  • Like
Reactions: Pinkyyy 💜🍎, katbel, TheGeneralist and 1 other person
Are the apps you had given location permissions to saved somewhere in Mac settings? If this is fixed either in an OS13.5.1 or Sonoma, will they be put back into Privacy and Security>Location Services?
 
pmcjr said:
Are the apps you had given location permissions to saved somewhere in Mac settings? If this is fixed either in an OS13.5.1 or Sonoma, will they be put back into Privacy and Security>Location Services?
Click to expand...
Yes, there's a configuration file where the information written. An update should be able to restore access to the previous settings. Sonoma betas don't show the problem so it can be inferred that this isn't intended behavior.
 
  • Like
Reactions: Pinkyyy 💜🍎, katbel, Queen6 and 1 other person
I understand it's unrelated. Developer/customer seed and now public received the latest Sonoma build, will macOS 13.5.1 update drops tomorrow or Friday?
 
minik said:
I understand it's unrelated. Developer/customer seed and now public received the latest Sonoma build, will macOS 13.5.1 update drops tomorrow or Friday?
Click to expand...
Nobody knows. I'd have expected this to be fixed no later than last week. The Sonoma beta release schedule likely has no bearing on a bug fix update for Ventura.
 
chrfr said:
Nobody knows. I'd have expected this to be fixed no later than last week. The Sonoma beta release schedule likely has no bearing on a bug fix update for Ventura.
Click to expand...
So, the problem could continue into Ventura if not fixed first in 13.5.1? It makes sense, though, that this fix would come first.
 
  • Like
Reactions: Pinkyyy 💜🍎
pmcjr said:
So, the problem could continue into Ventura if not fixed first in 13.5.1? It makes sense, though, that this fix would come first.
Click to expand...
The problem doesn't occur in any of the Sonoma betas.
 
chrfr said:
The problem doesn't occur in any of the Sonoma betas.
Click to expand...
So, like you said yesterday, in the absence of a 13.5.1, Sonoma will pick up the Ventura Location Services configuration file and repopulate a "new" Location Services setting?
 
pmcjr said:
So, like you said yesterday, in the absence of a 13.5.1, Sonoma will pick up the Ventura Location Services configuration file and repopulate a "new" Location Services setting?
Click to expand...
I would assume so. The data is still there, it just can't be accessed through the UI. I have not tested a Ventura to Sonoma upgrade, but in clean Sonoma installs you can still access the Location Services settings.
 
  • Like
Reactions: Pinkyyy 💜🍎 and pmcjr
Calling Apple was useless, a complete waste of time... I gave up waiting on them, so tried to find a workaround scouring the internet. If you are desperate like me (needing it for work) and need Location permissions to be enabled for an app, here's what I did...

https://discussions.apple.com/thread/255021792?answerId=259403149022#259403149022

It is a pain and takes time but if you need it, you need it!!! Hope this helps or saves you some time! :)
  1. Disable System Integrity Protection
    1. Restart your computer in Recovery mode.
    2. Launch Terminal from the Utilities menu.
    3. Run the command csrutil disable.
    4. Restart your computer.
  2. Location permissions stored in /private/var/db/locationd/clients.plist
    1. Enable hidden files in Finder or view through terminal commands.
  3. Copy file to your user directory: sudo cp /private/var/db/locationd/clients.plist clients.plist
  4. Give Write Permission for clients.plist. Get Info > Sharing & Permission > Everyone: Read/Write, Staff: Read/Write
  5. Open clients.plist using Xcode, and find the app you need to give permission (ie. Google Chrome)
    1. Add new parameter "Authorized" (Boolean/YES), save file.
    2. Note: Can be done without xcode but editing plist files in a text editor is a nightmare.
  6. Copy updated file back to locationd: sudo cp clients.plist /private/var/db/locationd/clients.plist
  7. Restart your computer (I didnt see the changes until I did this)
  8. Remember to Re-Enable System Integrity Protection
    1. Restart your computer in Recovery mode.
    2. Launch Terminal from the Utilities menu.
    3. Run the command csrutil enable.
    4. Restart your computer.
 
  • Like
Reactions: Pinkyyy 💜🍎, katbel, TheGeneralist and 1 other person
  • Haha
Reactions: Pinkyyy 💜🍎 and katbel
frenchcamp49er said:
They have like 80,000 points, ya I’m not sure if he’s an actual moderator, I’ll have to reread the thread, I thought they were though
Click to expand...
Forum should unmod that person. A mod, of course, may participate in any forum discussion. But when a mod, with a strange level of stubbornness, gaslights and misleads users with a blatant lack of expertise and common sense, they should unmod him or disallow him from participating and stick to modding instead. A mod should reduce problems and confusion, not cause them. He pushed a few users on there to a state of frustration and despair by his hammering on "not bug, feature change" nonsense. Like, a guy missing an arm or a car missing a steering wheel is not a "feature change."
 
Last edited:
  • Like
Reactions: TheYayAreaLiving 🎗️ and Pinkyyy 💜🍎
  • Like
Reactions: Pinkyyy 💜🍎, katbel and TheYayAreaLiving 🎗️
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back