yarn add react-native-config
react-native link react-native-config
- Create
.env
files for each configuration. Ex:.env.dev
,.env.prod
, etc Ex:
API_ENDPOINT=https://api.myresource.com/dev
ENV=dev
yarn add react-native-config
react-native link react-native-config
.env
files for each configuration. Ex: .env.dev
, .env.prod
, etc
Ex:API_ENDPOINT=https://api.myresource.com/dev
ENV=dev
// imports | |
public class ImageRotator { | |
public static Bitmap rotateImage(String path) throws IOException { | |
Bitmap bitmap = BitmapFactory.decodeFile(path); | |
return rotateImage(bitmap); | |
} | |
public static Bitmap rotateImage(Bitmap bitmap) throws IOException { | |
int rotate = 0; |
#!/bin/sh | |
# Make an android app debugabble and reinstall | |
set -ex | |
DNAME="CN=Ross Patterson, OU=me, O=rpatterson.net, L=San Francisco, ST=CA, C=US" | |
PACKAGE_RE='^package:(/data/app/([^-]+)-.+==/(.+.apk))=.+' | |
MANIFEST_RE='(<application [^>]+)>' | |
export PATH=$HOME/Android/Sdk/platform-tools:$PATH |
Download the appropriate Kali Linux .iso
I used a 64 bit .iso
image, downloaded via HTTP. I downloaded the amd64 weekly version, as the pool
linux headers (needed below for installation of wireless drivers) were ahead of the stable release kernel.
Download the SHA256SUMS
and SHA256SUMS.gpg
files from the same location.
#!/bin/bash | |
# This script uses traps to create try/catch/finally functionality in shell scripts. | |
# | |
# OUTPUT: | |
# | |
# Hello! We're reporting live from script | |
# ./try_catch2.sh: line 23: badcommand: command not found | |
# ./try_catch2.sh: line 23: exiting with status 127 | |
# It's the end of the line |
There are several apps I currently have to re-sign. They are apps built by various outside vendors who do not want to share the source code, but we want the apps published from our account and we do not want to give them our certificate or access to publish the apps on our behalf. ¯\_(ツ)_/¯ These are the steps I use to re-sign them. I've decided to keep the steps manual because, frankly, it's an error-prone process, something done infrequently, and a moving target. Some detail always seems to shift with every major Xcode release or App Store change.
These steps are current as of iOS 14 and Xcode 12. They assume you already have your Distribution Certificate installed in Keychain.
I'm going to use an example named "Matt's App.ipa". If you need to provide instructions to a vendor to deliver this file to you properly, I've included what I use below.