4 ms·
> If you are using touch bar libraries you MUST have touch bar features and the reviewer can ask you where they are. Ok but there are no touch bar libraries in
by _qulr 6y ago
> If you are using touch bar libraries you MUST have touch bar features and the reviewer can ask you where they are.
Ok but there are no touch bar libraries in this case.
> They will include third party code (ad networks etc) without enough care - the networks then try to device fingerprint etc.
Not the case here. Also, if this issue was triggered by code, then it would come up in every update, instead of just occasionally at random.
- donor20 6y agoMy point is simply there are guidelines around touchbar - despite your claims. Stop trying to claim that there is no guideline - as I have repeatedly pointed out - if you are using touchbar libs to fingerprint devices for ad networks - that is not allowed as one example. If this app wasn't doing any of that, then great! The reviewer was wrong. But to claim no rules around touchbar usage and calls is entirely false.
- _qulr 6y ago> Stop trying to claim that there is no guideline - as I have repeatedly pointed out As I have repeatedly pointed out, I was never trying to claim that. You are arguing against a straw man. You're right. You win. The straw man is defeated.
- dvfjsdhgfv 6y agoI have a hard time following you: it's been clarified that the code in question didn't reference the touchbar, neither directly nor indirectly. That's the whole point.