> Ummmm....those arent private.  They are listed right in the UITouch
> docs:

> http://developer.apple.com/iphone/library/documentation/UIKit/Referen...

> What you may be referring to is the simulateTapAtPoint: method and the
> UITouch/UIEvent categories.  Just remove the simulateTapAtPoint:
> method and everything it references which is just the  UITouch
> (TTCategory) and UIEvent (TTCategory). You can get extra efficient and
> remove the UIEventFake class.

> @implementation UITouch (TTCategory)

> - (id)initInView:(UIView *)view location:(CGPoint)location {
>   if (self = [super init]) {
>     _tapCount = 1; <= BAD
>     _locationInWindow = location; <= BAD
>     _previousLocationInWindow = location; <= BAD

>     UIView *target = [view.window hitTest:_locationInWindow withEvent:nil];
>     _view = [target retain]; <= BAD
>     _window = [view.window retain]; <= BAD
>     _phase = UITouchPhaseBegan; <= BAD
>     _touchFlags._firstTouchForView = 1; <= BAD
>     _touchFlags._isTap = 1; <= BAD
>     _timestamp = [NSDate timeIntervalSinceReferenceDate]; <= BAD
>   }
>   return self;

> }

> - (void)changeToPhase:(UITouchPhase)phase {
>   _phase = phase; <= BAD
>   _timestamp = [NSDate timeIntervalSinceReferenceDate]; <= BAD

> }

> @end

> On Mon, Oct 26, 2009 at 3:38 PM, uprise78 <des...@gmail.com> wrote:

> > Ummmm....those arent private.  They are listed right in the UITouch
> > docs:

> >http://developer.apple.com/iphone/library/documentation/UIKit/Referen...

> > What you may be referring to is the simulateTapAtPoint: method and the
> > UITouch/UIEvent categories.  Just remove the simulateTapAtPoint:
> > method and everything it references which is just the  UITouch
> > (TTCategory) and UIEvent (TTCategory). You can get extra efficient and
> > remove the UIEventFake class.

> On Oct 26, 3:47 pm, Pradeepta Dash <pradee...@gmail.com> wrote:

> > Here is the code :http://github.com/joehewitt/three20/blob/master/src/UIViewAdditions.m

> > @implementation UITouch (TTCategory)

> > - (id)initInView:(UIView *)view location:(CGPoint)location {
> >   if (self = [super init]) {
> >     _tapCount = 1; <= BAD
> >     _locationInWindow = location; <= BAD
> >     _previousLocationInWindow = location; <= BAD

> >     UIView *target = [view.window hitTest:_locationInWindow withEvent:nil];
> >     _view = [target retain]; <= BAD
> >     _window = [view.window retain]; <= BAD
> >     _phase = UITouchPhaseBegan; <= BAD
> >     _touchFlags._firstTouchForView = 1; <= BAD
> >     _touchFlags._isTap = 1; <= BAD
> >     _timestamp = [NSDate timeIntervalSinceReferenceDate]; <= BAD
> >   }
> >   return self;

> > }

> > - (void)changeToPhase:(UITouchPhase)phase {
> >   _phase = phase; <= BAD
> >   _timestamp = [NSDate timeIntervalSinceReferenceDate]; <= BAD

> > }

> > @end

> > On Mon, Oct 26, 2009 at 3:38 PM, uprise78 <des...@gmail.com> wrote:

> > > Ummmm....those arent private.  They are listed right in the UITouch
> > > docs:

> > >http://developer.apple.com/iphone/library/documentation/UIKit/Referen...

> > > What you may be referring to is the simulateTapAtPoint: method and the
> > > UITouch/UIEvent categories.  Just remove the simulateTapAtPoint:
> > > method and everything it references which is just the  UITouch
> > > (TTCategory) and UIEvent (TTCategory). You can get extra efficient and
> > > remove the UIEventFake class.

> An app of mine got rejected because three20 uses private API/ivars.

> - UITouch._locationInWindow
> - UITouch._phase
> - UITouch._previousLocationInWindow
> - UITouch._tapCount
> - UITouch._timestamp
> - UITouch._touchFlags
> - UITouch._view
> - UITouch._window

> --pradeepta

> On Oct 26, 5:32 pm, Matt Vague <mattva...@gmail.com> wrote:

> > So were supposed to remove this from three20??

> > On Oct 26, 3:47 pm, Pradeepta Dash <pradee...@gmail.com> wrote:

> > > Here is the code :http://github.com/joehewitt/three20/blob/master/src/UIViewAdditions.m

> > > @implementation UITouch (TTCategory)

> > > - (id)initInView:(UIView *)view location:(CGPoint)location {
> > >   if (self = [super init]) {
> > >     _tapCount = 1; <= BAD
> > >     _locationInWindow = location; <= BAD
> > >     _previousLocationInWindow = location; <= BAD

> > >     UIView *target = [view.window hitTest:_locationInWindow withEvent:nil];
> > >     _view = [target retain]; <= BAD
> > >     _window = [view.window retain]; <= BAD
> > >     _phase = UITouchPhaseBegan; <= BAD
> > >     _touchFlags._firstTouchForView = 1; <= BAD
> > >     _touchFlags._isTap = 1; <= BAD
> > >     _timestamp = [NSDate timeIntervalSinceReferenceDate]; <= BAD
> > >   }
> > >   return self;

> > > }

> > > - (void)changeToPhase:(UITouchPhase)phase {
> > >   _phase = phase; <= BAD
> > >   _timestamp = [NSDate timeIntervalSinceReferenceDate]; <= BAD

> > > }

> > > @end

> > > On Mon, Oct 26, 2009 at 3:38 PM, uprise78 <des...@gmail.com> wrote:

> > > > Ummmm....those arent private.  They are listed right in the UITouch
> > > > docs:

> > > >http://developer.apple.com/iphone/library/documentation/UIKit/Referen...

> > > > What you may be referring to is the simulateTapAtPoint: method and the
> > > > UITouch/UIEvent categories.  Just remove the simulateTapAtPoint:
> > > > method and everything it references which is just the  UITouch
> > > > (TTCategory) and UIEvent (TTCategory). You can get extra efficient and
> > > > remove the UIEventFake class.

> Can anyone give a list of "safe" changes that are going to satisfy the
> requirement and not break everything?

> Can anyone give a list of "safe" changes that are going to satisfy the
> requirement and not break everything?

> Notice that three20 is included in the Facebook app.

> On Oct 26, 7:51 pm, uprise78 <des...@gmail.com> wrote:
>> To be safe, you probably should.  That being said, I have a few apps
>> in the app store that have that code in them.  It just depends on your
>> luck with the Apple employee who does your review.

>> On Oct 26, 5:32 pm, Matt Vague <mattva...@gmail.com> wrote:

>> > So were supposed to remove this from three20??

>> > On Oct 26, 3:47 pm, Pradeepta Dash <pradee...@gmail.com> wrote:

>> > > Here is the code :http://github.com/joehewitt/three20/blob/master/src/UIViewAdditions.m

>> > > @implementation UITouch (TTCategory)

>> > > - (id)initInView:(UIView *)view location:(CGPoint)location {
>> > >   if (self = [super init]) {
>> > >     _tapCount = 1; <= BAD
>> > >     _locationInWindow = location; <= BAD
>> > >     _previousLocationInWindow = location; <= BAD

>> > >     UIView *target = [view.window hitTest:_locationInWindow withEvent:nil];
>> > >     _view = [target retain]; <= BAD
>> > >     _window = [view.window retain]; <= BAD
>> > >     _phase = UITouchPhaseBegan; <= BAD
>> > >     _touchFlags._firstTouchForView = 1; <= BAD
>> > >     _touchFlags._isTap = 1; <= BAD
>> > >     _timestamp = [NSDate timeIntervalSinceReferenceDate]; <= BAD
>> > >   }
>> > >   return self;

>> > > }

>> > > - (void)changeToPhase:(UITouchPhase)phase {
>> > >   _phase = phase; <= BAD
>> > >   _timestamp = [NSDate timeIntervalSinceReferenceDate]; <= BAD

>> > > }

>> > > @end

>> > > On Mon, Oct 26, 2009 at 3:38 PM, uprise78 <des...@gmail.com> wrote:

>> > > > Ummmm....those arent private.  They are listed right in the UITouch
>> > > > docs:

>> > > >http://developer.apple.com/iphone/library/documentation/UIKit/Referen...

>> > > > What you may be referring to is the simulateTapAtPoint: method and the
>> > > > UITouch/UIEvent categories.  Just remove the simulateTapAtPoint:
>> > > > method and everything it references which is just the  UITouch
>> > > > (TTCategory) and UIEvent (TTCategory). You can get extra efficient and
>> > > > remove the UIEventFake class.

> http://developer.apple.com/iphone/library/documentation/UIKit/Referen...

> What you may be referring to is the simulateTapAtPoint: method and the
> UITouch/UIEvent categories.  Just remove the simulateTapAtPoint:
> method and everything it references which is just the  UITouch
> (TTCategory) and UIEvent (TTCategory). You can get extra efficient and
> remove the UIEventFake class.

> What about the call to simulateTapAtPoint in UIWebViewAdditions.m ?

> On Tue, Oct 27, 2009 at 10:43 AM, neptune2000 <papa.ma...@gmail.com> wrote:

> > What about the call to simulateTapAtPoint in UIWebViewAdditions.m ?

> I get that, but removing the call is going to pretty much break the
> function that uses it.

> On Oct 27, 10:46 am, Mike D <des...@gmail.com> wrote:
>> you will need to remove that as well or your project wont compile.

>> On Tue, Oct 27, 2009 at 10:43 AM, neptune2000 <papa.ma...@gmail.com> wrote:

>> > What about the call to simulateTapAtPoint in UIWebViewAdditions.m ?

> On Tue, Oct 27, 2009 at 12:56 PM, neptune2000 <papa.ma...@gmail.com> wrote:

> > I get that, but removing the call is going to pretty much break the
> > function that uses it.

> > On Oct 27, 10:46 am, Mike D <des...@gmail.com> wrote:
> >> you will need to remove that as well or your project wont compile.

> >> On Tue, Oct 27, 2009 at 10:43 AM, neptune2000 <papa.ma...@gmail.com> wrote:

> >> > What about the call to simulateTapAtPoint in UIWebViewAdditions.m ?

> - (void) simulateTapAtPoint:(CGPoint_ location

> - (id)initInView:(UIView *)view location:(CGPoint)location {

> - (void)changeToPhase:(UITouchPhase)phase {

> - (void)simulateTopElement:(NSString*) query {

> I should not be getting any compilation errors, right?

> I guess it is time to try.

> On Oct 27, 1:48 pm, Mike D <des...@gmail.com> wrote:

> > Nothing in three20 uses it.  As long as you arent using it then it
> > won't hurt anything.

> > On Tue, Oct 27, 2009 at 12:56 PM, neptune2000 <papa.ma...@gmail.com> wrote:

> > > I get that, but removing the call is going to pretty much break the
> > > function that uses it.

> > > On Oct 27, 10:46 am, Mike D <des...@gmail.com> wrote:
> > >> you will need to remove that as well or your project wont compile.

> > >> On Tue, Oct 27, 2009 at 10:43 AM, neptune2000 <papa.ma...@gmail.com> wrote:

> > >> > What about the call to simulateTapAtPoint in UIWebViewAdditions.m ?

> > The non-public APIs that are included in your applications are the
> > following:
> > - firstResponder
> > - undocumented, Private UITouch instance variables

> I'm going to assume that the UITouch instance variables is the same issue as
> Pradeepta's, however the firstResponder problem is troubling.

> That selector is used whenever Three20 (or otherwise) needs to know if the
> keyboard is visible, or to scroll the first responder into the view. I'll
> have to strip all that functionality out of three20 to use it.

> A greater concern though, is that Three20 is using private APIs without
> flagging it to the consumer of the library. As much as I find three20 to be
> a great productivity to boost to working with cocoa, we're going to be
> phasing it out of our applications.

> -Nick

> Ouch.

> I've just started adopting Three20. Abandon ship?

> However, I took out the all calls to firstResponder as well and re-submitted
> the app just now (just to safe)

> Thanks for the heads up.
> --pradeepta

> On Wed, Oct 28, 2009 at 6:02 PM, Nick Partridge <nkp...@gmail.com> wrote:
> > Related to this rejection, I just had an app rejected with the following
> > feedback:

> > > The non-public APIs that are included in your applications are the
> > > following:
> > > - firstResponder
> > > - undocumented, Private UITouch instance variables

> > I'm going to assume that the UITouch instance variables is the same issue
> > as Pradeepta's, however the firstResponder problem is troubling.

> > That selector is used whenever Three20 (or otherwise) needs to know if the
> > keyboard is visible, or to scroll the first responder into the view. I'll
> > have to strip all that functionality out of three20 to use it.

> > A greater concern though, is that Three20 is using private APIs without
> > flagging it to the consumer of the library. As much as I find three20 to be
> > a great productivity to boost to working with cocoa, we're going to be
> > phasing it out of our applications.

> > -Nick

> However, I took out the all calls to firstResponder as well and re-submitted
> the app just now (just to safe)

> Thanks for the heads up.
> --pradeepta

> On Wed, Oct 28, 2009 at 6:02 PM, Nick Partridge <nkp...@gmail.com> wrote:
> > Related to this rejection, I just had an app rejected with the following
> > feedback:

> > > The non-public APIs that are included in your applications are the
> > > following:
> > > - firstResponder
> > > - undocumented, Private UITouch instance variables

> > I'm going to assume that the UITouch instance variables is the same issue
> > as Pradeepta's, however the firstResponder problem is troubling.

> > That selector is used whenever Three20 (or otherwise) needs to know if the
> > keyboard is visible, or to scroll the first responder into the view. I'll
> > have to strip all that functionality out of three20 to use it.

> > A greater concern though, is that Three20 is using private APIs without
> > flagging it to the consumer of the library. As much as I find three20 to be
> > a great productivity to boost to working with cocoa, we're going to be
> > phasing it out of our applications.

> > -Nick