Skip to content

Instantly share code, notes, and snippets.

View jmoody's full-sized avatar
✏️

Joshua Moody jmoody

✏️
172 followers · 11 following
  • GitHub Staff
  • Germany
View GitHub Profile
@jmoody
jmoody / crashdump.md
Created October 9, 2024 06:53
golangci-lint crash report macOS 
Incident Identifier: 713DD27B-41EA-448C-B31A-A04D45A830C3
CrashReporter Key:   FF40DB60-5617-B003-17F4-81E82DED1853
Hardware Model:      MacBookPro18,2
Process:             golangci-lint [88290]
Path:                /Volumes/VOLUME/*/golangci-lint
Identifier:          golangci-lint
Version:             ???
Code Type:           ARM-64 (Native)
Role:                Unspecified
@jmoody
jmoody / tmate-on-macOS.md
Last active August 30, 2024 20:34
tmate on macOS

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
jmoody / README.md
Last active June 24, 2023 10:13
diffing binary plists and mobileprovisions

~/.gitatrributes

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

~/.gitconfig

@jmoody
jmoody / navbar_steps.rb
Created July 27, 2012 19:49
calabash-cucumber steps for dealing with the navigation bar
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
jmoody / .bashrc
Created January 20, 2016 08:25
Jenkins LaunchAgent and scripts for El Capitan
# 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
jmoody / bundle-id.sh
Created October 15, 2015 11:08
Bash script for extracting CFBundleIdentifier from .app or .ipa (MacOS only)
#!/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
jmoody / debug.log
Created January 28, 2020 14:37
vagrant vmware_desktop macOS RubyEncoder .bundles are not signed
```
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
jmoody / Screenshotter.m
Last active December 5, 2019 14:16
Add a step and a screenshot to your Test Cloud report
#import <XCTest/XCTest.h>
#import "Screenshotter.h"
@implementation Screenshotter
+ (void)screenshotWithTitle:(NSString *)format, ... {
NSString *title = nil;
va_list args;
va_start(args, format);
@jmoody
jmoody / contents.md
Created August 10, 2017 13:43
NSLog output can cause apps to become unresponsive during testing

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
jmoody / export-crash-report.md
Last active May 21, 2017 08:57
Export a Crash Report From Xcode 6

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.