jmoody

Tmate is a remote tmux session over ssh.

Intall with Homebrew

$ brew update && brew upgrade
$ brew install tmux
$ brew install reattach-to-user-namespace
$ brew install tmate

jmoody

~/.gitatrributes

*.plist diff=plist
*.mobileprovision diff=mobileprovision

~/.gitconfig

jmoody

def navbar_visible?
  !query('navigationBar').empty?
end

def navbar_has_back_button?
  !query("navigationItemButtonView").empty?
end

def navbar_should_have_back_button
  unless navbar_has_back_button?

jmoody

# Can be more or less complicated depending on your CLI needs.

export HISTCONTROL=erasedups
export HISTSIZE=5000
shopt -s histappend

export VISUAL=less
export EDITOR=vim
export GIT_EDITOR="${EDITOR}"

jmoody

#!/usr/bin/env bash

function error {
  echo "$(tput setaf 1)ERROR: $1$(tput sgr0)"
}

function usage {
  echo "Usage: bundle-id.sh /path/to/App.{ipa | app}"
}

jmoody

```
 INFO manager: Loading plugin `vagrant-vmware-desktop` with default require: `vagrant-vmware-desktop`
could not load /opt/vagrant/embedded/rgloader/rgloader24.darwin: dlopen(/opt/vagrant/embedded/rgloader/rgloader24.darwin.bundle, 9): no suitable image found.  Did find:
        /opt/vagrant/embedded/rgloader/rgloader24.darwin.bundle: code signature in (/opt/vagrant/embedded/rgloader/rgloader24.darwin.bundle) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed. - /opt/vagrant/embedded/rgloader/rgloader24.darwin.bundle
 INFO manager: Loading plugin `vagrant-vmware-desktop` with slash require: `vagrant/vmware/desktop`
ERROR manager: Plugin loading error: LoadError - cannot load such file -- vagrant/vmware/desktop

ERROR vagrant: /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/plugin/manager.rb:342:in `rescue in load_plugins'
/opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/plugin/manager.rb

jmoody

#import <XCTest/XCTest.h>
#import "Screenshotter.h"

@implementation Screenshotter

+ (void)screenshotWithTitle:(NSString *)format, ... {

  NSString *title = nil;
  va_list args;
  va_start(args, format);

jmoody

2. NSLog output can cause apps to become unresponsive during testing.

If your app becomes unresponsive during testing, check your device or simulator logs for an unusual or a high volume of NSLog output.

It has been demonstrated that a spike in NSLog output can cause the UIAutomation API to become unresponsive. This has been reproduced using the Instruments.app with applications that are not linked with the calabash.framework. This is an Apple bug.

Viewing Simulator Logs

jmoody

Xcode 6

1. Plug in the device and open Xcode
2. Choose Window -> Devices from the Xcode menu
3. Under the DEVICES section in the left column, choose the device
4. To see crash logs, select the View Device Logs button under the Device Information section on the right hand panel
5. Find your app in the Process column and select the Crash log to see the contents.
6. IMPORTANT Be sure to symbolicate your crash report.
7. Export the symbolicated crash report.

jmoody

# emacs backup files
(.*/)?\#[^/]*\#$

# binaries
*.ipa
*.app
*.apk

## Mac OS X
.DS_Store