Well how should they know? They have a sort of binary parser that searches for unauthorized use of some (non-public) APIs, but I don't see how this use of an authorized API (-canOpenURL) would be problematic.
They won't be able to see what is going on unless the start the app under Instruments and document how many calls to this function are made.
Well, first of all, they probably know by now :) So I'm wondering if that will change anything.
I would also think they are doing run time profiling, if only to catch private API usage via NSSelectorFromString. Maybe they can add a test for excessive canOpenURL calls now.
Or maybe they don't care about this and more apps will do this kind of snooping going forward.
Comments
Well how should they know? They have a sort of binary parser that searches for unauthorized use of some (non-public) APIs, but I don't see how this use of an authorized API (-canOpenURL) would be problematic.
They won't be able to see what is going on unless the start the app under Instruments and document how many calls to this function are made.
Well, first of all, they probably know by now :) So I'm wondering if that will change anything.
I would also think they are doing run time profiling, if only to catch private API usage via NSSelectorFromString. Maybe they can add a test for excessive canOpenURL calls now.
Or maybe they don't care about this and more apps will do this kind of snooping going forward.