Thoughts
I’ve been lucky enough to spend a couple days with several friend in Oahu island. Let me just say this: Hawaii is awesome.
During january, when it’s supposed to be winter, the water temperature is perfect pitch. Wifi is great, and the food is super tasty, not sure why, yet.
Next time… Maui maybe?
You’ll need to create PNG assets with the following sizes and filenames:
[cc]
icon_16x16.png
icon_16x16@2x.png
icon_32x32.png
icon_32x32@2x.png
icon_128x128.png
icon_128x128@2x.png
icon_256x256.png
icon_256x256@2x.png
icon_512x512.png
icon_512x512@2x.png
[/cc]
All of those assets should go into a folder named ‘Icon.iconset’.
Afterwards, just fire Terminal and type the following command:
[cc]
iconutil -c icns
[/cc]
If all went well, you should have a .icns file right there!.
Reference: Apple’s Guidelines.
If you’re reading this, probably… it’s because the Art Designers of your team just sent you a bunch of SD assets, with the @2x substring… and you don’t wanna spend the next 30 minutes cleaning that up… right?
If that’s the case, you’ve come to the right place. Fire Terminal, open the containing folder, and type the following:
[cc]
find . -type f -name “*@2x*” -exec sh -c ‘echo mv “$0” “${0/@2x/}”‘ ‘{}’ \;
[/cc]
Note: you might have just noticed that this will actually echo the replacement. That’s for safety. Validate the output, and proceed removing the ‘echo’ command call.
I’ve been getting “Invalid binary” errors, while trying to upload a binary to the AppStore. The solution can be found in stackoverflow, i’m just pasting it here, for future reference…
1. Re-Codesign the Helper app from terminal:
[cc]codesign -f -s “3rd Party mac Developer Application:” -i “com.bundle.YOUR.HELPER” –entitlements path/to/helper/entitlements YOUR-HELPER.app[/cc]
2. Remove provisioning profile from Helper app, adding a “Run script” into the “Build Phases”:
[cc]rm “${BUILT_PRODUCTS_DIR}/${PRODUCT_NAME}.app/Contents/Library/LoginItems/YOUR-HELPER.app/Contents/embedded.provisionprofile”[/cc]
After this, i managed to upload the binary!
This glitch is pretty annoying. You’re following a log, while connected to a server (through ssh), and after a while, your ssh connection hangs.
The solution?.
Fire up Terminal, and type the following: nano ~/.ssh/config
Once there, fill up the following:
[cc]
ServerAliveInterval 300
ServerAliveCountMax 120
[/cc]
That should keep your connection alive for the next 10 hours, without further issues.