Wrong iPhone model in Analytical data

austin0000 wrote:

It used to say “iPhone 12” (my actual hardware model) and now it says “iPhone 13,2” (not my actual hardware model)…

Apple differentiates the names on the boxes and in the marketing from the names that Apple uses internally for the products.

Much like you are using the austin0000 nickname here, you probably use a different name or nickname elsewhere.

Much like you using two different names for yourself, Apple uses iPhone13,2 (no space!) as the internal product name for an iPhone 12. Two names, same thing.

Log files are not intended for reading by folks not working on products, often filled with cryptic and confusing and ominous (and often entirely benign!) messages, and more generally Apple is increasingly obfuscating the names and locations and other details used in various displays to make tracking individual people more difficult; for reasons of user privacy.

iPhone 12 model, as mentioned above. See the (free) MacTracker app for this and other data.

For logs… Apple goes to some length to anonymize the client data available to web servers and other sources, including geolocation data and device-specific identity; agent strings, etc.

In general terms, finding exploits or issues in log files is akin to searching unlimited and cryptically- and scarily-worded number of haystacks for an unknown number of needles possibly none, and without knowing what the needles look like. Not all that great for finding issues, though logs can be useful after an exploit has been identified.

That is the internal Apple identifier for an iPhone 12.

Yes, an iPhone identifier 13,2 is an iPhone 12.

An iPhone SE 2nd generation has an Apple identifier of iPhone 12,8.

austin0000 wrote:

Thank you that’s interesting information to know. I forgot to mention this issue is recent.. And without straying away from the topic too much, you say logs are useful when an exploit has been identified, but aside from the typical and conventional surface level indicators that an exploit is being used - wouldn’t the logs be the next step up to identifying said exploit?

Searching voluminous and never-ending streams of text data looking for an unknown match for a problem which may not or does not exist is not often a fruitful endeavor.

That’s what log files are.

Once you know there is an issue and once you have targets to search for, then logs might get interesting.

Otherwise, you’re evaluating all of the passing cars on a freeway, looking for a crook. Without knowing the car. Which car contains a crook? Which car containing a crook is your crook?

Crooks also prefer to avoid logging messages. Calling attention to themselves tends to be considered undesirable.

Endpoint security might be useful, but that’s not something thpically all that useful for end-users.

Exploits against currently-patched iPhones are expensive, rare, and targeted.

Most folks getting in trouble get phished, or get their passwords exploited. Easier to hack the humans than to hack their devices.

austin0000 wrote:

This issue is recent.. sorry forgot to mention that.

Might want to provide a little more detail on “this issue”, as that’s a fairly open-ended description of your concerns and experiences here; with whatever is (or is not) happening…