• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Regarding UIAlertView validation
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Regarding UIAlertView validation


  • Subject: Re: Regarding UIAlertView validation
  • From: Luke the Hiesterman <email@hidden>
  • Date: Thu, 22 Apr 2010 12:05:36 -0700

Just because you think you should be able to use our classes in a way that isn't supported doesn't make it a "bug in the OS" that needs to be worked around. File an enhancement request for the thing you want and in the mean time design your application in a way that IS supported, especially when you have Apple engineers specifically telling you not to do something.

Please understand that your pledge to test your application on new OSes is not a justification for abusing our API.

1. We spend a great deal of engineering effort trying to ensure all your applications work before we ever send out a seed
2. If you don't live up to your pledge to thoroughly test your app before new OS releases, people blame Apple when the new OS "breaks" your app
3. In some cases, applications are denied acceptance to the App store for API abuse (adding subviews to the camera view prior to OS 3.1 comes to mind)

The camera case is actually instructive for this scenario. We told people that adding subviews was NOT supported and some people did it anyway and were denied approval to the store. Some people asked us to please provide API so that they could legitimately do this....and in time we did! Again, the answer is not to abuse our API, but to file requests for things you want or need and always remember......

DO NOT USE PRIVATE METHODS, OR ABUSE OUR API IN ANY WAY. PLEASE!

Luke

On Apr 22, 2010, at 11:53 AM, Hamish Allan wrote:

> On Thu, Apr 22, 2010 at 5:47 PM, Michael Weller <email@hidden> wrote:
>
>> It's not supported, meaning it could easily break in a future OS/API version. What if the alert view is redesigned so the view hierarchy changes? Your apps are going to break.
>
> When we work around other bugs in the OS, sometimes we have to rely on
> implementation details; so we test against each OS version well before
> the public gets it. This is really no different.
>
> H

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Regarding UIAlertView validation
      • From: Hamish Allan <email@hidden>
References: 
 >Regarding UIAlertView validation (From: Praveen Kumar <email@hidden>)
 >Re: Regarding UIAlertView validation (From: Luke Hiesterman <email@hidden>)
 >Re: Regarding UIAlertView validation (From: Hamish Allan <email@hidden>)
 >Re: Regarding UIAlertView validation (From: Michael Weller <email@hidden>)
 >Re: Regarding UIAlertView validation (From: Hamish Allan <email@hidden>)

  • Prev by Date: Re: Regarding UIAlertView validation
  • Next by Date: Re: Trouble debugging unit tests of framework
  • Previous by thread: Re: Regarding UIAlertView validation
  • Next by thread: Re: Regarding UIAlertView validation
  • Index(es):
    • Date
    • Thread