READ THIS BEFORE POSTING (Re: Three20 app rejections)
William Lachance
over and over again. I'm suspecting that much of this has to do with
the extreme noisiness in the previous thread. For reference, the
actual informative messages in the previous thread (Heads up: Apple
store rejection for apps using three20) were the following:
http://groups.google.com/group/three20/msg/0081e93dca4e5402
(describing a rejection notice with other undocumented API)
http://groups.google.com/group/three20/msg/257238be68152bb2
(describing why apps are being rejected: Apple running a static
analysis tool which checks for the presence of code which calls the
private API, not necessarily their use)
http://groups.google.com/group/three20/msg/b27c83bf56ecf4ba
(description of the changes required to the library to remove the use
of undocumented API)
http://groups.google.com/group/three20/msg/678834205e3e5b06
(announcement of app-store safe fork of three20, which removes the use
of undocumented API as described above)
Summary:
1. Three20 uses undocumented API's in a number of places. Apple's
review process is catching all of them.
2. Joe Hewitt committed a fix a week ago which removes some, but not
all, of the use of the undocumented API.
3. A user named uprise78 ('Mike D') has graciously provided a fork of
three20 with these symbols removed:
http://github.com/uprise78/three20-P31
No, no one knows when an "official" version of three20 will come out
with the problems resolved. However, you can look at uprise78's fork
yourself to see what's changed. While I haven't done an exhaustive
analysis, it looks like he's done the right thing based on what others
have been saying. See for yourself here:
http://github.com/uprise78/three20-P31/commits/master
Please do not reply to this message unless you have something
genuinely new to add to the above. Most especially, please do not ask
the following questions, as they will just sow further confusion:
1. Is Joe's version safe? He committed something to remove the use of
the private APIs! (see above, no he didn't)
2. Will my app get rejected if I use uprise78's fork? (we don't know,
but the best information we have says it will be ok)
3. When will these fixes be applied to the "official version"? (given
the fact that Joe's basically stepped down from doing further work on
the library, it's probably best to just consider uprise78's fork to be
the official version until someone else steps forward to move the
library forward)
--
William Lachance
wrl...@gmail.com
uprise78
plans for it here is what will happen. If you just want the fixes to
get your apps in the app store, use the commit with the following
info:
commit 3a1f0a9bea92aed27f12a513e1e70c5412ba0f91
tree 0da7dba956f71ca57a029dc3a7c88448e76f9942
parent 2c03d2b98ddb287ba68ddb628c4a72588bbee79e
Starting in a few days I am going to start pushing fixes to some
outstanding Three20 bugs and some additions to the repo. If you dont
want the changes stick with the commit listed above. If you do want
the changes keep pulling and they will keep coming.
rodmaz, if you see this I wanted to know if I could include your
TTLauncherViewController in the new repo. I think it would be a good
addition to the library.
