Whereas privacy experts welcome the future iOS 14 updates, Facebook claims the new features could cause a 50 percent drop in its advertising revenue.
Facebook is deeply concerned about an upcoming privacy update to Apple’s mobile platform, which presupposes that applications will request users’ consent prior to collecting and sharing their information. When the update in question takes effect, iPhone and iPad users will be able to decide whether or not to let apps harvest data via Apple’s Identifier for Advertisers (IDFA). This is a token uniquely assigned to a mobile device. Social networking services in general and Facebook in particular can sell info amassed via IDFA to third-party advertisers that can leverage this data to craft targeted adverts. Continue reading Facebook fears iOS 14 could disrupt its advertising business
At some point in life, you are gonna work with a codebase that you didn’t write from the very beginning. Specially if you are maintaing it, one of the biggest questions often is ‘where to start looking in order to fix bug Y?’.
Most of the times, there will be a strong relationship with what you see in the screen and the code you need to get fixed. For those cases, I’ve wrote three strategies that involve the Xcode’s ‘view hierarchy debug’ and the console. I’ve used them often and they have proved handy, so I hope they can be of help for you.
For this guide I’m using Xcode’s view hierarchy debug, a knock-off of an original app, Reveal. If you haven’t tried it, I really recomend that you download Reveal’s trial and that you ask your company / boss / parents to buy it since it makes debugging so much less painful.
1. Find the delegate and dataSource of a UITableView
- Get the memory address of the
UITableView you want to debug. If you are using the debug view hierarchy tool from Xcode, you will find the address on the top of the Object Inspector: In this example, we observe the address 0x7fc4ddf403c0 for the
- Knowing this address we can simply print its
dataSource in Xcode’s Terminal:
po [0x7fc4ddf403c0 delegate]
Aha! We got the
datasource for this
UITableView and we know where we need to start adding breakpoints!
2. Find the dataSource and delegate of a UICollectionViewCell
If you can get the memory address of a
UICollectionViewCell, you can get its
UICollectionView and then find its
- Start by finding the address of the
UICollectionViewCell by using the debug view hierarcy tool. In this example 0x7f83068767f0.
- Then, look for the
nextResponder of it.
po [0x7f83068767f0 nextResponder]
- With the address of the
UICollectionView now we simply print its
delegate like we did for the
po [[0x7f83068767f0 nextResponder] dataSource]
3. Find the method called by a UIButton (or UIControl)
The ‘Debug View Hierarcy’ in Xcode, can tell us the class name of a button’s target. This is very helpful, but perhaps you really want to nail down the name of the method that is being called when you press that button.
- First, get the memory address of the
UIControl) you want to debug.
- Then, print the targets of the button.
po [0x7fc3277025d0 allTargets]
This will print all the targets of your UIControl with their memory addresses.
- We got the target of this
UIControl, now we can get the selector being called during the control event. Here I’m looking for
UIControlEventTouchUpInside. Enum values are not defined in the console so we will need to use the actual numeric value for UIControlEventTouchUpInside, 64.
po [0x7fc3277025d0 actionsForTarget:0x7fc322e99070 forControlEvent:64]
This command will print an array with selector(s) we are looking for. In this example, the selectors for the event
userDidTouchUpInsideFeedbackButton in the button.
Now we narrowed the event of this control down to the method and class.
I wrote a post on Spotify’s Labs Blog about some learnings I had regarding accessibility. of our iOS Client.
Check it out!.
Back when I was active recording my own music (SoundCloud for the curious) I always used a hardware knob to navigate and control Logic.
It was a very simple device (a knob which is also a big button) but incredibly useful. So I thought: if it was so wonderful with music software, perhaps it can useful on an IDE!
My main problem was the constant switching between clicking the simulator (or taping a real device) and typing the common two-handed shortcuts you need while debugging in Xcode: pause, step over, step into, etc.
I browsed MIDI controllers and video control surfaces, and bought a Contour Shuttle-Xpress after a little research. It’s small, inexpensive and comes with a dial and more than enough buttons.
Other options I considered were:
- an updated version of the Griffin Powermate: It looks really neat but I wanted more than one button. Also, I’m not a big fan of changing batteries.
- Palette Controllers: Nice looking but too expensive. If you don’t know what to do with your money, there is a Wood Edition for only $899.
- MIDI controllers: Bulky and require some third party software converting MIDI to keyboard commands.
Next thing was just to configure my most used shortcuts and tune a little bit that configuration after some use. This is the layout I’m using right now:
|Big Left Button
||De / Activate Breakpoints
||Add Breakpoint at Current Line
||Debug – Pause
||Debug – Continue
|Big Right Button
||Debug – Step Into
||Up Arrow / Down Arrow
||Debug Step Over / Out
Definitively worth it!
It’s probably not as powerful as it is for video or music software, but it makes debugging more comfortable, and at 40-60 USD it’s worth a try.
Of course, you could also set different shortcuts, but the easy ones are already assigned, and if I really wanted to stretch my hands I would instead try to play something from Rachmaninoff.