Because it was the only non valid point he could find out and instead ended up saying nothing worthy at all, that's how many discussions end up here.I'm sorry; where in the US constitution does it state where iCloud storage should be located? And if Russia and China want those servers on their soil why is this in breach of "Democratic Rules of Law"?
Because they may not have been able to tell that the apps were doing this, because developers don’t submit their source code when they upload apps for review, and snooping traffic many not work due to location or IP range lockouts, and isn’t that easy in the first place.Why not refuse to publish the Apps in the first place? Why always Apple takes action when something goes viral on the media? Good job Apple I guess?
Then it's Apple's own guidelines and policies fault for them not to have a way to fully know what an App is going to behave or do in their own "protected" OS, before publishing it.Because they may not have been able to tell that the apps were doing this, because developers don’t submit their source code when they upload apps for review, and snooping traffic many not work due to location or IP range lockouts, and isn’t that easy in the first place.
Any reason why Apple waits until the media makes a big deal about it before doing anything about it? Calculator bug, Group FaceTime bug, etc. Come on, Apple. Get it together. I'm starting to feel like everything they do is a PR stunt. Like if this information wasn't released to the public Apple would have just let the apps continue recording all our screens.
The analytics capability is probably a legit part. It’s one way for app developers (especially UX designers) to find out how effective their app design is. The way I see it is that analytics companies like Glassbox utilize it as a tracking service (not necessarily wrong as they do provide ways to mask personal information), with the failure point being the Air Canada app developer failing to take precautions masking their customers’ sensitive data.That's not my point fine Sir, the point if that Apple is supposed to review Apps before publishing them, if a multi billion dollar company can't even do that, then what's their greed to say they care about privacy and user experience? With your example you just showed us all on how Apple never really cared about their own guidelines that they let porn Apps slide into their own wall garden OS.
Their actions are only corrective when it's viral on the media, also if it was a UX design supposed for developers to "find out how effective their app design is" then Apple wouldn't have done anything at all.The analytics capability is probably a legit part. It’s one way for app developers (especially UX designers) to find out how effective their app design is. The way I see it is that analytics companies like Glassbox utilize it as a tracking service (not necessarily wrong as they do provide ways to mask personal information), with the failure point being the Air Canada app developer failing to take precautions masking their customers’ sensitive data.
Like Steve Jobs said, even Apple is run by humans, and humans make mistakes. The way apple responded at least have been positive so far as they took actions. It’s a bit disingenuous to keep bashing Apple despite their corrective actions.
Then it's Apple's own guidelines and policies fault for them not to have a way to fully know what an App is going to behave or do in their own "protected" OS, before publishing it.
Any reason why Apple waits until the media makes a big deal about it before doing anything about it? Calculator bug, Group FaceTime bug, etc. Come on, Apple. Get it together. I'm starting to feel like everything they do is a PR stunt. Like if this information wasn't released to the public Apple would have just let the apps continue recording all our screens.
Then it's Apple's own guidelines and policies fault for them not to have a way to fully know what an App is going to behave or do in their own "protected" OS, before publishing it.
That's their job to know since they created a wall garden in their own OS'es, if they can't know how do you suppose for them to have their own App review policy in order to accept/reject the Apps?
Yeah, I was wondering the same thing. Apple of late is too reactive, when they need to be proactive about things like this. Especially their coveted App Store... like how the hell did these apps even get approved as they are in the first place?Any reason why Apple waits until the media makes a big deal about it before doing anything about it? Calculator bug, Group FaceTime bug, etc. Come on, Apple. Get it together. I'm starting to feel like everything they do is a PR stunt. Like if this information wasn't released to the public Apple would have just let the apps continue recording all our screens.
It's only logical if I defend Apple for you, am I right? You said nothing at all and used nonsense comparatives which don't relate to what I've been saying since the start of this thread. If a company is not capable of having a way to determine if the App's code, then they can't make up false claims such as their non existing privacy concerns. The only "privacy" care they do is when their name is on fire on the media about some malicious App, they remove it, just like every other AppStore does. Nothing different, nothing new, nothing to praise of.That's like saying it's your own fault for being struck by a drunk driver because you didn't make yourself fully aware of all drunk drivers that were out and about.
The average of app has hundreds of thousands, if not millions, of lines of source code, and even with full access to the source code it is impossible (logically, reasonably, and practically) determine what the source code does. And even then, apps rely on a great extent on back end third-party code for functionality (as is the case here).
But kudos, well done, on another baseless lllogical contribution to the cesspool of nonsense that MR has become.
How many Apps are in the App Store doing the same or worse that we don't know? They should hire a staff team to sort them out.Theoretically you are correct, but there is a limited number of things you can audit in a reasonable timeframe. Now that this has been discovered I'm fairly confident it will become part of the go-forward process.
If what you're saying is true then that actually makes my point stronger. So Apple has review guidelines and reviewers for nothing? They need everyone else to find all the problems in their software and the apps running on it? I gave 2 examples of where Apple knew or at least should have known about the problem long before the general public ever knew about it, and there are countless more throughout the company's history.Any reason you comment on articles without any basis in fact for what you are saying?
For example, where does it say anywhere in this article, or in any other article about this issue, that Apple knew of this issue before it was published by a media outlet?
Why not refuse to publish the Apps in the first place? Why always Apple takes action when something goes viral on the media? Good job Apple I guess?
I didn't get your point, you should reformulate your sentences more clearly.Um ok. So they should somehow know that if you type a secret code in an app, only if you aren’t located at apple, then it behaves differently than otherwise? (For example).
Good luck with that.
Apple knowing about a problem or bug.Seriously? That's easy. Before Apple can act on an issue, there must first be awareness of the issue.
It's nice when you have the benefit of hindsight.
That’s what I’d like to know. Why does it take someone else to ‘discover’ this instead of Apple in the first place?Why wasn't this discovered during the review process?
Good! I can’t believe I have 2 of these apps! Expedia and Hotels.com!!
Yesterday, TechCrunch discovered that multiple popular iPhone apps from major companies are using intrusive analytics services that capture data ranging from taps and swipes to full screen recordings, all without customers knowing about it.
![]()
Today, Apple has informed app developers that this kind of screen recording analytics code needs to be clearly disclosed to customers or removed from iOS apps. From an Apple spokesperson's email to TechCrunch:At least one developer has already been told to remove the code that recorded app activities. From an email to the developer:Apple is serious about getting rid of this code and gave the developer in question less than a day to remove it and resubmit the app before it would be pulled from the App Store.
High-profile apps like Abercrombie & Fitch, Hotels.com, Air Canada, Hollister, Expedia, and Singapore Airlines are using Glassbox, a customer experience analytics firm with a "session replay" screen recording feature.
Session replays are designed to let developers screenshot or record or a user's screen and then play back those recordings to see how users interact with their apps. Taps, button pushes, and keyboard entries are all captured and provided to app developers.
None of the apps above disclosed that they were recording a user's screen in their privacy policies, which is apparently in violation of Apple's App Store rules.
Apple also requires apps that record the screen to have a little red icon on the top left corner of the phone to make it clear that the screen is being recorded, and it sounds like Apple is going to enforce this rule for this kind of analytics tracking.
Most likely, apps will need to remove this feature because customers are not going to willingly use an app that's recording everything that they're doing and displaying a persistent red icon while the app is open.
There are many other analytics companies that have similar practices like Appsee and UXCam, so there are undoubtedly many more apps that are using these secret screen recording features without customer knowledge.
Article Link: Apple Forces Developers to Remove Screen Recording Code From iOS Apps
Apple should be having more trust issues with the Apps developers - be more suspicious, to cutoff such behavior preemptively.
Apple knowing about a problem or bug.
The media and the general public making a big deal about a problem or bug.
Let's play Spot the Difference with those two statements.
Point is, why does Apple wait until the media and the general public know about an issue or make a big deal about it before doing anything about it? I didn't say "Why does Apple wait until they find out about a problem before they fix it?"
The headline of this article is misleading ... the article explains that this sort of activity is allowed, as long as it is disclosed. I would prefer this being banned altogether though. The headline says that developers are being forced to remove this code, which is true, but they can add it back in as long as they add a disclosure.Today, Apple has informed app developers that this kind of screen recording analytics code needs to be clearly disclosed to customers or removed from iOS apps.
Well, think about it.Their actions are only corrective when it's viral on the media, also if it was a UX design supposed for developers to "find out how effective their app design is" then Apple wouldn't have done anything at all.
Apple seems to be having to do stuff like this every week lately. Privacy just seems to have gone completely out the window.
Apple knowing about a problem or bug.
The media and the general public making a big deal about a problem or bug.
Let's play Spot the Difference with those two statements.
Point is, why does Apple wait until the media and the general public know about an issue or make a big deal about it before doing anything about it? I didn't say "Why does Apple wait until they find out about a problem before they fix it?"
They must have review guidelines and a team of reviewers for something. If they're not going to know about issues like this until TechCrunch writes an article about it then they need to decide if paying all those reviewers to not catch stuff like this is really worth it.