Apple: Is There A Problem Here?: Apple

Showing posts with label Apple. Show all posts

20131122

Problem ID: 6477333759285144664
Entered by: Ben Simo

The standard extension

Confusing Apple error message of the evening - pic.twitter.com/DBMKhjSRAu
— Matthew Keys (@MatthewKeysLive) September 2, 2013

Edit

20110918

Problem ID: 2043653703508795633
Entered by: Ben Simo

Select a certificate

I didn't ask to use any certificate. Safari offers none. So what am I expected to do here?

Edit

20110904

Problem ID: 1797290292882724663
Entered by: Ben Simo

Hey, there's a syntax error in your syntax error

@sh8kespeare tweets: Apple makes a grammatical error? Can you see it? Lol.

Edit

Problem ID: 8429137782199929319
Entered by: Ben Simo

Tautological Deletion Error

@applenag tweets: I appreciate the error message, Apple. I'd love it if you said WHY!

Edit

20110902

Problem ID: 6129878360291213952
Entered by: Ben Simo

The administrator has set your shell to an illegal value

@xbuzz tweets: Has anyone ever seen this error before?

Edit

20110831

Problem ID: 6607732443019704189
Entered by: Ben Simo

There is an unexpected error communication

@iacas tweets: Nice. Great error message Apple. So how can I install the Xcode 4.1.1 update???

Would you prefer expected errors? ;)

Edit

20110502

Problem ID: 4396542835097931435
Entered by: Ben Simo

Do you really want that ringtone?

@DeMarko: This dialog (and it's variations) has never EVER made sense to me.

Edit

20100212

Problem ID: 2371262077762744868
Entered by: Ben Simo

Hugs and kisses

"Apple have started putting kisses at the end of their error messages, that's nice isn't it." - @bertiestyles

Edit

20100118

Problem ID: 1812826472474482920
Entered by: Ben Simo

@dpie: It wouldn't be a Microsoft installation without a nonsensical error message, now would it?

If might be Microsoft software, but I believe that's an Apple error code.

What to do now? Searching the web for this error code doesn't help. I thought Macs were supposed to be more user friendly than the average PC.

Edit

20100113

Problem ID: 118625889240244994
Entered by: Ben Simo

0x8002006E

@jwilker: i love most things mac, EXCEPT error messages. so what now? sigh

If an error code was assigned for this condition, was is completely unexpected? How about guiding the user in correcting the problem?

Edit

20100110

Problem ID: 1573798098406773444
Entered by: Ben Simo

No error

@ChuckSmith: Best iTunes Connect error message ever! Grrr Apple, let me in!

Thank you for telling me there is no error. Now, why aren't I seeing the desired page?

Edit

20100103

Problem ID: 7519385479533095049
Entered by: Ben Simo

iPhone keyboard keyboard

“#iPhone keyboard problem. #fail” - @ronbeenen

“#iPhone keyboard #fail no.2 ... Seems to become a series.” - @ronbeenen

Edit

20100101

Problem ID: 6380414844235497202
Entered by: Ben Simo

-10810

jwilker: that's never good. Finde locked up. This is the error I got.

What is -10810? This message doesn't seem very useful in helping solve the problem. One could do a Google search and weed through the over 10000 results. They would likely discover that others get this error for a variety of reasons with a variety of applications on a variety of versions of Mac operating systems.

Don't know if it helps anyone, but I did find this article stating Finder.app -10810 errors in Snow Leopard may be related to accessing external drives.

Edit

Problem ID: 8023291270317203848
Entered by: Ben Simo

iPhone crashed Mac

sisutcliffe: I just crashed my mac plugging my iPhone into it:

Edit

20091231

Problem ID: 7075637522229138243
Entered by: Ben Simo

You do not have enough access privileges

“Syncing my iphone i get this error, and no new DL's from my phone transfer to my mac. Any ideas?” - @zombieskull13

So do I need more permission volume or the correct permissions?

Edit

Problem ID: 6155176897493130537
Entered by: Ben Simo

iPod Touch Keyboad Funk

“iPod touch failure is funny” - @cottonserver

“My iPod Touch keyboard does some strange things...” - @ben_v

“Check this iPod touch fail:” - @afroman_mitch

Edit

20090308

Problem ID: 6719224709505015570
Entered by: Ben Simo

Florian's Bug: The hour the iPhone forgot

Tweeted by @florianseroussi. Confirmed by @karlerikson and @maxbeatty.

It is March 8th, 2009. This is the 2nd Sunday in March, the day that Daylight Savings Time starts in the United States and Canada. This evening, Florian Seroussi (@florianseroussi) reported trouble setting his iPhone alarm to 2:30 AM for a conference call. Karl Erikson (@karlerikson) and Max Beatty (@maxbeatty) quickly confirmed they found the same problem on their iPhones.

So what happens when you try to set an alarm for 2:30 the next morning when it is the second Sunday in March? Let's see... (Screen shots courtesy of Karl Erikson.)

Add an alarm for 2:30 AM.

And get an alarm for 1:30 AM.

It appears that the iPhone alarm is coded to adjust times in the 2 o'clock hour back to the 1 o'clock hour on the second Sunday of March. This is correct for actions that apply to the second Sunday of March. However it looks like the fine folks at Apple neglected to consider the case of users needing to set alarms on the day the time changes for the 2 o'clock hour of the next morning.

Max Beatty tested other times and provided the following video. Take a look.

Thank you to Florian Seroussi for finding what Apple missed. Maybe he is the only one that wants to be awakened at 2:30 in the morning after the shortest day of the year. :) In his honor, I dub this bug Florian's Bug.

And, I hope Florian makes it to his meeting on time.

Edit

Usability Heuristics

• Visibility of system status Visibility of system status: The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.

• Match between system and the real world Match between system and the real world: The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.

• User control and freedom User control and freedom: Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.

• Consistency and standards Consistency and standards: Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.

• Error prevention Error prevention: Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.

• Recognition rather than recall Recognition rather than recall: Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.

• Flexibility and efficiency of use Flexibility and efficiency of use: Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

• Aesthetic and minimalist design Aesthetic and minimalist design: Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.

• Help users recognize, diagnose, and recover from errors Help users recognize, diagnose, and recover from errors: Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.

• Help and documentation Help and documentation: Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.

Consistency Heuristics

-F amiliar Familiar: The product is not consistent with the pattern of any familiar problem.

E xplainable Explainable: The product is explainable.

W orld World: The product is consistent with the real world.

H istory History: The present version of the product is consistent with past versions of it.

I mage Image: The product is consistent with an image that the organization wants to project.

C omparable Products Comparable Products: The product is consistent with comparable systems.

C laims Claims: The product is consistent with what important people say it’s supposed to be.

U ser Expectations User Expectations: The product is consistent with what users want.

P roduct Product: Each element of the product is consistent with comparable elements in the same system.

P urpose Purpose: The product is consistent with its purposes, both explicit and implicit.

S tatutes Statutes: The product is consistent with applicable laws.

FAILURE Heuristics

F unctional Functional: The error detecting, reporting, and handling functions properly.

A ppropriate Appropriate: Errors are reported at the appropriate time in an appropriate manner.

I mpact Impact: The impact of the failure is communicated to those impacted.

L og Log: The error is appropriately logged; or not logged.

U ser Interface User Interface: The error is reported in the user interface in terms that the user understands.

R ecovery Recovery: The user is informed of what they need to do to recover from the error.

E motions Emotions: The error handling and reporting has a positive influence on user emotions.

Security Vulnerabilities

1. Injection Injection: Injection flaws occur when untrusted data is sent to an interpreter as part of a command. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without authorization.

2. Broken authentication and session management Broken authentication and session management: Application functions related to authentication and session management are often not implemented correctly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities.

3. Cross-Site Scripting Cross-Site Scripting (XSS): XSS flaws occur whenever an application takes untrusted data and sends it to a web browser without proper validation or escaping. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites.

4. Insecure Direct Object References Insecure Direct Object References: A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, or database key. Without an access control check or other protection, attackers can manipulate these references to gain unauthorized access to data.

5. Security Misconfiguration Security Misconfiguration: Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and platform. Secure settings should be defined, implemented, and maintained, as defaults are often insecure. Additionally, software should be kept up to date.

6. Sensitive Data Exposure Sensitive Data Exposure: Many web applications do not properly protect sensitive data, such as credit cards, tax IDs, and authentication credentials. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data deserves extra protection such as encryption at rest or in transit, as well as special precautions when exchanged with the browser.

7. Missing Function Level Access Control Missing Function Level Access Control: Most web applications verify function level access rights before making that functionality visible in the UI. However, applications need to perform the same access control checks on the server when each function is accessed. If requests are not verified, attackers will be able to forge requests in order to access functionality without proper authorization.

8. Cross-Site Request Forgery Cross-Site Request Forgery (CSRF): A CSRF attack forces a logged-on victim’s browser to send a forged HTTP request, including the victim’s session cookie and any other automatically included authentication information, to a vulnerable web application. This allows the attacker to force the victim’s browser to generate requests the vulnerable application thinks are legitimate requests from the victim.

9. Using Components with Known Vulnerabilities Using Components with Known Vulnerabilities: Running software components with known vulnerabilities can compromise the vulnerable components and anything those components can access -- undermining defenses.

10. Unvalidated Redirects and Forwards Unvalidated Redirects and Forwards: Using untrusted data, without validation, to determine the destination of redirects and forwards can enable attackers to redirect victims to phisihing or malware sites.

Is There A Problem Here?

20131122

The standard extension

20110918

Select a certificate

20110904

Hey, there's a syntax error in your syntax error

Tautological Deletion Error

20110902

The administrator has set your shell to an illegal value

20110831

There is an unexpected error communication

20110502

Do you really want that ringtone?

20100212

Hugs and kisses

20100118

An Error of Type -10657

20100113

0x8002006E

20100110

No error

20100103

iPhone keyboard keyboard

20100101

-10810

iPhone crashed Mac

20091231

You do not have enough access privileges

iPod Touch Keyboad Funk

20090308

Florian's Bug: The hour the iPhone forgot

Problem or no problem?

Usability Heuristics

Consistency Heuristics

FAILURE Heuristics

Security Vulnerabilities

Popular

Recent Problems

Recent Comments