GitHub Objective-C Daily Trending Repositories

opa334/TrollStore

Jailed iOS app that can install IPAs permanently with arbitary entitlements and root helpers because it trolls Apple

TrollStore

TrollStore is a permasigned jailed app that can permanently install any IPA you open in it.

It works because of an AMFI/CoreTrust bug where iOS does not correctly verify code signatures of binaries in which there are multiple signers.

Supported versions: 14.0 beta 2 - 16.6.1, 16.7 RC (20H18), 17.0

Installing TrollStore

For installing TrollStore, refer to the guides at ios.cfw.guide

16.7.x (excluding 16.7 RC) and 17.0.1+ will NEVER be supported (unless a third CoreTrust bug is discovered, which is unlikely).

Updating TrollStore

When a new TrollStore update is available, a button to install it will appear at the top in the TrollStore settings. After tapping the button, TrollStore will automatically download the update, install it, and respring.

Alternatively (if anything goes wrong), you can download the TrollStore.tar file under Releases and open it in TrollStore, TrollStore will install the update and respring.

Uninstalling an app

Apps installed from TrollStore can only be uninstalled from TrollStore itself, tap an app or swipe it to the left in the 'Apps' tab to delete it.

Persistence Helper

The CoreTrust bug used in TrollStore is only enough to install "System" apps, this is because FrontBoard has an additional security check (it calls libmis) every time before a user app is launched. Unfortunately it is not possible to install new "System" apps that stay through an icon cache reload. Therefore, when iOS reloads the icon cache, all TrollStore installed apps including TrollStore itself will revert back to "User" state and will no longer launch.

The only way to work around this is to install a persistence helper into a system app, this helper can then be used to reregister TrollStore and its installed apps as "System" so that they become launchable again, an option for this is available in TrollStore settings.

On jailbroken iOS 14 when TrollHelper is used for installation, it is located in /Applications and will persist as a "System" app through icon cache reloads, therefore TrollHelper is used as the persistence helper on iOS 14.

URL Scheme

As of version 1.3, TrollStore replaces the system URL scheme "apple-magnifier" (this is done so "jailbreak" detections can't detect TrollStore like they could if TrollStore had a unique URL scheme). This URL scheme can be used to install applications right from the browser, or to enable JIT from the app itself (only 2.0.12 and above), the format goes as follows:

apple-magnifier://install?url=<URL_to_IPA>
apple-magnifier://enable-jit?bundle-id=<Bundle_ID>

On devices that don't have TrollStore (1.3+) installed, this will just open the magnifier app.

Features

The binaries inside an IPA can have arbitrary entitlements, fakesign them with ldid and the entitlements you want (ldid -S<path/to/entitlements.plist> <path/to/binary>) and TrollStore will preserve the entitlements when resigning them with the fake root certificate on installation. This gives you a lot of possibilities, some of which are explained below.

Banned entitlements

iOS 15 on A12+ has banned the following three entitlements related to running unsigned code, these are impossible to get without a PPL bypass, apps signed with them will crash on launch.

com.apple.private.cs.debugger

dynamic-codesigning

com.apple.private.skip-library-validation

Unsandboxing

Your app can run unsandboxed using one of the following entitlements:

<key>com.apple.private.security.container-required</key>
<false/>

<key>com.apple.private.security.no-container</key>
<true/>

<key>com.apple.private.security.no-sandbox</key>
<true/>

The third one is recommended if you still want a sandbox container for your application.

You might also need the platform-application entitlement in order for these to work properly:

<key>platform-application</key>
<true/>

Please note that the platform-application entitlement causes side effects such as some parts of the sandbox becoming tighter, so you may need additional private entitlements to circumvent that. (For example afterwards you need an exception entitlement for every single IOKit user client class you want to access).

In order for an app with com.apple.private.security.no-sandbox and platform-application to be able to access it's own data container, you might need the additional entitlement:

<key>com.apple.private.security.storage.AppDataContainers</key>
<true/>

Root Helpers

When your app is not sandboxed, you can spawn other binaries using posix_spawn, you can also spawn binaries as root with the following entitlement:

<key>com.apple.private.persona-mgmt</key>
<true/>

You can also add your own binaries into your app bundle.

Afterwards you can use the spawnRoot function in TSUtil.m to spawn the binary as root.

Things that are not possible using TrollStore

Getting proper platformization (TF_PLATFORM / CS_PLATFORMIZED)
Spawning a launch daemon (Would need CS_PLATFORMIZED)
Injecting a tweak into a system process (Would need TF_PLATFORM, a userland PAC bypass and a PMAP trust level bypass)

Compilation

To compile TrollStore, ensure theos is installed. Additionaly ensure brew is installed and install libarchive from brew.

Credits and Further Reading

@alfiecg_dev - Found the CoreTrust bug that allows TrollStore to work through patchdiffing and worked on automating the bypass.

Google Threat Analysis Group - Found the CoreTrust bug as part of an in-the-wild spyware chain and reported it to Apple.

@LinusHenze - Found the installd bypass used to install TrollStore on iOS 14-15.6.1 via TrollHelperOTA, as well as the original CoreTrust bug used in TrollStore 1.0.

Fugu15 Presentation

Write-Up on the first CoreTrust bug with more information.

PojavLauncherTeam/PojavLauncher_iOS

A Minecraft: Java Edition Launcher for Android and iOS based on Boardwalk. Succeeded by https://github.com/AngelAuraMC/Amethyst-iOS

PojavLauncher for iOS

Important note

PojavLauncher has been discontinued and is no longer supported. Its successor is available here.

Introduction

PojavLauncher is a Minecraft: Java Edition launcher for Android, iOS, and iPadOS, based off of zhuowei's Boardwalk project.

Supports most versions of Minecraft: Java Edition, from the very first beta to the newest snapshots.
Supports Forge, Fabric, OptiFine, and Quilt for you to customize the experience with supported mods.
Includes customizable on-screen controls, keyboard and mouse support, and game controller support.
Optimized for jailbroken and TrollStore devices to enable better capabilities.
Microsoft account and demo mode support for logging into Minecraft.
...and much more!

This repository contains the code for our iOS and iPadOS port of PojavLauncher. Looking for Android?

Getting started with PojavLauncher

The PojavLauncher Website has extensive documentation on how to install, set up, and play! For those who wish to install quickly, here's the basics:

Requirements

At the minimum, you'll need one of the following devices on iOS 14.0 and later:

iPhone 6s and later
iPad (5th generation) and later
iPad Air (2nd generation) and later
iPad mini (4th generation) and later
iPad Pro (all models)
iPod touch (7th generation)

However, we recommend one of the following devices on iOS 14.0 and later:

iPhone XS and later, excluding iPhone XR and iPhone SE (2nd generation)
iPad (10th generation) and later
iPad Air (4th generation) and later
iPad mini (6th generation) and later
iPad Pro (all models, except for 9.7-inch)

Recommended devices provide a smoother and more enjoyable gameplay experience compared to other supported devices.

tvOS support is in development.
iOS 17.x and iOS 18.x is supported. However, a computer is required. These methods will ultilized usage of pymobiledevice3. Python 3.11.(x) must be properly set up on your computer. For more information, please check out the official Wiki: https://pojavlauncherteam.github.io/JIT.html#what-are-the-methods-to-enable-jit

Setting up to sideload

PojavLauncher can be sideloaded in many ways. Our recommended solution is to install TrollStore if your iOS version supports it. Installing with TrollStore allows you to permenantly sign the application, automatically enable JIT, and increase memory limits.

For iOS/iPadOS 17.0: Unfortunately,the above process will not work. It is required that you must use TrollRestore. Any versions above iOS/iPadOS 17.0 will NOT be supported (as of December 23, 2024).

If you cannot, AltStore and SideStore are your next best options.

Signing services that do not use your UDID (and use distribution certificates) are not supported, as PojavLauncher requires capabilities they do not allow. However, if you do managed to gain access to a Development certificate, due to it having the necessary entitlement (being com.apple.security.get-task-allow) to attach a debugger to the running process (enabling JIT), you may use a Development certificate.
Only install sideloading software and PojavLauncher from trusted sources. We are not responsible for any harm caused by using unofficial software.
Jailbreaks also benefit from permenant signing, autoJIT, and increased memory limits, however we do not recommend them for regular use.

Installing PojavLauncher

Release build (TrollStore)

Download an IPA of PojavLauncher in Releases.
Open the package in TrollStore using the share menu.

Release build (AltStore/SideStore trusted source)

Add PojavLauncher Repository from the Trusted Sources menu.
Tap FREE to begin installing.

Nightly builds

These builds can contain game-breaking bugs. Use with caution.

Download an IPA build of PojavLauncher in the Actions tab.
Open the downloaded IPA in your sideloading app to install.

Enabling JIT

PojavLauncher makes use of just-in-time compilation, or JIT, to provide usable speeds for the end user. JIT is not supported on iOS without the application being debugged, so workarounds are required to enable it. You can use this chart to determine the best solution for you and your setup.

Application	AltStore	SideStore	TrollStore	Jitterbug	Jailbroken
Requires ext-device	Yes	No	No	If VPN unavailable	No
Requires Wi-Fi	Yes	Yes	No	Yes	No
Auto enabled	Yes(*)	No	Yes	No	Yes

(*) AltServer running on the local network is required.

Contributors

PojavLauncher is amazing, and surprisingly stable, and it wouldn't be this way without the commmunity that helped and contribute to the project! Some notable names:

@khanhduytran0 - Lead iOS port developer
@crystall1nedev - Lead iOS port developer
@artdeell
@Mathius-Boulay
@zhuowei
@jkcoxson
@Diatrus

Third party components and their licenses

Caciocavallo: GNU GPLv2 License.
jsr305: 3-Clause BSD License.
Boardwalk: Apache 2.0 License
GL4ES by @lunixbochs @ptitSeb: MIT License.
Mesa 3D Graphics Library: MIT License.
MetalANGLE by @kakashidinho and ANGLE team: BSD 2.0 License.
MoltenVK: Apache 2.0 License.
openal-soft: LGPLv2 License.
Azul Zulu JDK: GNU GPLv2 License.
LWJGL3: BSD-3 License.
LWJGLX (LWJGL2 API compatibility layer for LWJGL3): unknown license.
DBNumberedSlider: Apache 2.0 License
fishhook: BSD-3 License.
shaderc (used by Vulkan rendering mods): Apache 2.0 License.
NRFileManager: MPL-2.0 License
AltKit
UnzipKit: BSD-2 License.
DyldDeNeuralyzer: bypasses Library Validation for loading external runtime
Thanks to MCHeads for providing Minecraft avatars.

Special thanks to MacStadium!

This project is listed under the MacStadium Open Source Program, which allows all of us developers to keep on moving forward even without physical access to a Mac.

Mininglamp-OSS/octo-ios

OCTO iOS Client — Open-source enterprise IM

OCTO — the open workplace built for humans × AI agents.
_{Let Lobsters (OpenClaw-powered digital doubles) do the thinking and doing. You focus on taste.}

🏠 OCTO Home · 🚀 Quickstart · 📦 Ecosystem · 🤝 Contributing

🌐 Read in: English · 简体中文

OCTO iOS

Native iOS client for the OCTO messaging platform — Swift / Objective-C, talking to octo-server over REST + WebSocket.

octo-ios is the official iOS front-end for OCTO. It is a native Swift / Objective-C app (not a webview wrapper) that talks to octo-server over REST + WebSocket, and drives the same Lobster-agent conversation surface as octo-web and octo-android.

🌟 Why OCTO iOS

Native, not a webview. UIKit + SwiftUI hybrid, uses platform features (APNS push, Share / Notification / Widget extensions, Universal Links, Shortcuts) rather than shipping a browser shell. First-class mobile UX for Lobster conversations.
Ships without secrets. No GoogleService-Info.plist, no signing certificates, no provisioning profiles bound to the upstream team. You bring your own Apple Developer team, your own Bundle Identifier (com.example.octo placeholder → com.yourcompany.octo), your own Firebase project, your own certificates. All stripped by the octo-release pipeline before this repo is published.
Mirrors the web surface. Same REST + WebSocket protocol as octo-web / octo-android, same i18n resource keys (English · 简体中文), same Lobster identity / streaming / typing indicators — so feature work can land on three clients without a protocol fork.

🚀 Quickstart

⚠️ Mandatory pre-flight — this fork will not build a signed or distributable .ipa until you swap four placeholder artefacts:

Bundle Identifier — see README-BUNDLE-ID.md for the full rename checklist across the .pbxproj, entitlements, and every extension target (com.example.octo → your reverse-DNS).
Firebase configuration — see firebase-template.md for how to obtain and drop in your own GoogleService-Info.plist.
Provisioning / certificates — use your Apple Developer team's own signing certificate and provisioning profile; the upstream fork references none.
Universal Links — see universal-link-setup.md for the apple-app-site-association file that your domain must host before deep-links resolve to your build.

Once those are done, open in Xcode:

git clone https://github.com/Mininglamp-OSS/octo-ios.git
cd octo-ios

# CocoaPods (if used):
pod install

# Or Swift Package Manager — handled by Xcode on open.

open OCTO.xcworkspace   # or OCTO.xcodeproj

From CLI, a development build after signing is configured:

xcodebuild -workspace OCTO.xcworkspace \
    -scheme OCTO \
    -configuration Debug \
    -destination 'generic/platform=iOS Simulator' \
    build

By default the app points at http://localhost:8080 for octo-server. Edit OCTO/Config/Config.plist (or the flavour-specific equivalent) to aim at your own deployment.

📦 Modules / Architecture

Top-level layout (typical OCTO iOS tree):

Path	Purpose
`OCTO/`	Main app target — view controllers, SwiftUI views, app delegate
`OCTO/UI/`	Screen surfaces: chat, channels, org, settings
`OCTO/Data/`	REST + WebSocket client, local cache, Core Data / Realm models
`OCTO/Agent/`	Lobster-aware UI components (streaming, tool-call previews, agent identity)
`OCTO/Push/`	APNS registration + push routing + notification-service extension
`OCTO/Resources/`	Assets, localisations (`en.lproj`, `zh-Hans.lproj`), launch storyboards
`ShareExtension/`	Share-sheet target for forwarding content into OCTO
`NotificationExtension/`	Rich-notification + encryption-aware decryption target
`WuKongSDK/`	WuKongIM iOS client wrapper (real-time messaging transport)
`Pods/` or `Packages/`	CocoaPods / SPM dependencies

Runtime pillars:

Auth — token / refresh-token stored in Keychain.
Transport — URLSession for REST; WuKongIM iOS SDK for the persistent WebSocket.
Persistence — Core Data (or Realm, depending on flavour) for message cache and offline drafts; file attachments under the app container.
Push — APNS device token → octo-server → Firebase fan-out (optional) → Notification-Service extension decrypts the payload before display.
UI — UIKit navigation skeleton + SwiftUI screens where it pays off; Dynamic Type + Dark Mode supported by default.

🔗 OCTO Ecosystem

graph TD
  subgraph Clients[Clients]
    Web[octo-web<br/>Web / PC]
    Android[octo-android<br/>Android]
    iOS[octo-ios<br/>iOS]
  end

  subgraph Core[Core Services]
    Server[octo-server<br/>Backend API]
    Matter[octo-matter<br/>Task / Todo]
    Summary[octo-smart-summary<br/>AI Summary]
    Admin[octo-admin<br/>Admin Console]
  end

  subgraph Shared[Shared Libraries & Integrations]
    Lib[octo-lib<br/>Core Go Library]
    Adapters[octo-adapters<br/>Third-party Adapters]
  end

  Web --> Server
  Android --> Server
  iOS --> Server
  Admin --> Server
  Server --> Matter
  Server --> Summary
  Server --> Adapters
  Server -.uses.-> Lib
  Matter -.uses.-> Lib
  Adapters -.uses.-> Lib

Repository	Language	Role
`octo-server`	Go	Backend API · business orchestration · Lobster agent scheduling
`octo-matter`	Go	Task / Todo / Matter micro-service
`octo-smart-summary`	Go	LLM-powered conversation summarisation
`octo-web`	TypeScript / React	Web & PC (Electron) client
`octo-android`	Kotlin / Java	Native Android client
`octo-ios`	Swift / Objective-C	Native iOS client
`octo-admin`	TypeScript / React	Admin console (tenant / org / user / channel management)
`octo-lib`	Go	Shared core library (protocol, crypto, storage, HTTP)
`octo-adapters`	TypeScript / Python	Third-party integrations (IM bridges, AI channels)

🧭 Philosophy

OCTO ships under three shared principles that apply to every repository in this matrix:

Local-first. Anything that can run on the user's own box — chats, embeddings, agents — should. Your data stays yours; cloud is a choice, not a requirement.
Humans judge, AI thinks and acts. Humans focus on taste (what matters, what's right, what to ship). Lobster agents — OpenClaw-powered digital doubles — carry the thinking and execution load.
Release-as-product. Every open-source cut is shipped as a self-contained product, not a code dump: one squash per release, Apache 2.0, no internal baggage, reproducible from this repo alone.

🤝 Contributing

We love pull requests! Before you open one, please read:

CONTRIBUTING.md — workflow, branch model, commit style
CODE_OF_CONDUCT.md — community expectations

For security issues please follow SECURITY.md instead of the public tracker.

📄 License

Apache License 2.0 — see LICENSE for the full text and NOTICE for third-party attributions.

🙏 Acknowledgments

octo-ios owes its original scaffolding to:

TangSengDaoDaoiOS — our upstream, by the TangSengDaoDao team.
WuKongIM — the real-time messaging core that octo-server drives behind this client.

See NOTICE for the full attribution list and third-party component licenses.

_{Made with 🐙 by OCTO Contributors · Mininglamp-OSS}

geode-sdk/ios-launcher

Manages installing and launching Geometry Dash for iOS

Geode iOS Launcher

Manages installing and launching Geometry Dash with Geode for iOS.

Requirements

iOS/iPadOS 14.0 or later
Full version of Geometry Dash installed
An internet connection

Quick Start

Navigate to https://github.com/geode-sdk/ios-launcher/releases/latest, if you are not jailbroken, download the latest ipa file. If you wish to use the tweak and have TrollStore, download the latest tipa file.
Install the launcher by following the Installation Guide. You can also access this guide by going in to the INSTALL.md file in this repository.
Enjoy using Geode!

Support

If you have any further questions, or need help, be sure to join our Discord server!

Building / Development

To build this project, you must have the following prerequisites installed:

Theos [WSL for Windows and GNU/Linux]
make [Mac OS only]

After installing these, you can compile the project by running:

git clone --recurse-submodules https://github.com/geode-sdk/ios-launcher
cd ios-launcher
make package FINALPACKAGE=1 STRIP=0

Libraries

LiveContainer - Made the launcher possible!
Feather's Zsign fork - For signing the app and mods for allowing the launcher to load JIT-less! (Originally made by zhlynn, but forked for Feather)
MSColorPicker - Helper for Color Picking
GCDWebServer - For the web debug panel!

License

This project is licensed under the Boost Software License 1.0. Additionally, this project also uses code from LiveContainer. View the NOTICE.md for more details.

roothide/Bootstrap

A full featured bootstrap for iOS 15.0-17.0 A8-A17Pro & M1+M2 using roothide

roothide Bootstrap

A full featured bootstrap for iOS 15.0-17.0 A8-A17Pro & M1+M2 using roothide.

WARNING: By using this software, you take full responsibility for what you do with it. Any unofficial modifications to your device may cause irreparable damage. Refer to the FAQ linked in the `Usage` section for safe usage of this software.

roothide Bootstrap is available to download on this repositories Releases.

Building

If you do not have access to MacOS, refer to the FAQ in the Usage section to build with GitHub Actions instead.

You'll need MacOS to build, as you require Xcode from the App Store. Simply having Xcode Command Line Tools is insufficient. Here's how to build the Bootstrap:

Update/Install Theos with roothide support
```
bash -c "$(curl -fsSL https://raw.githubusercontent.com/roothide/theos/master/bin/install-theos)"
```
If you encounter errors from a previous Theos installation, remove Theos in its entirety before continuing.

Clone the GitHub repository and enter directory

git clone https://github.com/roothide/Bootstrap/ && cd Bootstrap

Build Bootstrap.tipa
```
make package
```
Transfer Bootstrap.tipa from ./packages/ to your device and install it with TrollStore

Usage

The roothide Bootstrap application must be installed with TrollStore. Use version 2.0.9 or later for enabling developer mode on-device.

By design, roothide does not inject tweaks into any 3rd applications by default. To enable tweak injection into an application, press App List in the Bootstrap app, and enable the toggle of the application you want to inject into.

For installing Bootstrap, refer to the guides at https://onejailbreak.com/blog/bootstrap-roothide/

Develop tweaks

You can refer to the developer documentation here.

Discord server

You can join the roothide Discord server for support or general discussion here.

The "Our Table" Icon

The ProcursusTeam logo was originally made by @TheAlphaStream, and later edited by @sourcelocation.

Credits

Huge thanks to these people, we couldn't have completed this project without their help!

absidue: https://github.com/absidue
akusio: https://twitter.com/akusio_rr
Alfie: https://alfiecg.uk
Amy While: http://github.com/elihwyma
Barron: https://tweaksdev22.github.io
BomberFish: https://twitter.com/bomberfish77
bswbw: https://twitter.com/bswbw
Capt Inc: http://github.com/captinc
CKatri: https://procursus.social/@cameron
Clarity: http://github.com/TheRealClarity
Cryptic: http://github.com/Cryptiiiic
dxcool223x: https://twitter.com/dxcool223x
Dhinakg: http://github.com/dhinakg
DuyKhanhTran: https://twitter.com/TranKha50277352
dleovl: https://github.com/dleovl
Elias Sfeir: https://twitter.com/eliassfeir1
Ellie: https://twitter.com/elliessurviving
EquationGroups: https://twitter.com/equationgroups
Évelyne: http://github.com/evelyneee
GeoSnOw: https://twitter.com/fce365
G3n3sis: https://twitter.com/G3nNuk_e
hayden: https://procursus.social/@hayden
Huy Nguyen: https://twitter.com/little_34306
iAdam1n: https://twitter.com/iAdam1n
iarrays: https://iarrays.com
iDownloadBlog: https://twitter.com/idownloadblog
iExmo: https://twitter.com/iexmojailbreak
iRaMzi: https://twitter.com/iramzi7
Jonathan: https://twitter.com/jontelang
Kevin: https://github.com/iodes
kirb: http://github.com/kirb
laileld: https://twitter.com/h_h_x_t
Leptos: https://github.com/leptos-null
limneos: https://twitter.com/limneos
Lightmann: https://github.com/L1ghtmann
Linus Henze: http://github.com/LinusHenze
MasterMike: https://ios.cfw.guide
Misty: https://twitter.com/miscmisty
Muirey03: https://twitter.com/Muirey03
Nathan: https://github.com/verygenericname
Nebula: https://itsnebula.net
niceios: https://twitter.com/niceios
Nightwind: https://twitter.com/NightwindDev
Nick Chan: https://nickchan.lol
nzhaonan: https://twitter.com/nzhaonan
Oliver Tzeng: https://github.com/olivertzeng
omrkujman: https://twitter.com/omrkujman
opa334: http://github.com/opa334
onejailbreak: https://twitter.com/onejailbreak_
Phuc Do: https://twitter.com/dobabaophuc
PoomSmart: https://twitter.com/poomsmart
ProcursusTeam: https://procursus.social/@team
roothide: http://github.com/roothide
Sam Bingner: http://github.com/sbingner
Shadow-: http://iosjb.top/
Snail: https://twitter.com/somnusix
SquidGesture: https://twitter.com/lclrc
sourcelocation: http://github.com/sourcelocation
SeanIsTethered: http://github.com/jailbreakmerebooted
TheosTeam: https://theos.dev
tigisoftware: https://twitter.com/tigisoftware
tihmstar: https://twitter.com/tihmstar
xina520: https://twitter.com/xina520
xybp888: https://twitter.com/xybp888
xsf1re: https://twitter.com/xsf1re
yandevelop: https://twitter.com/yandevelop
YourRepo: https://twitter.com/yourepo
And you, the community, for giving insightful feedback and support.

roothide/Developer

document for tweak Developers

update jailbreak apps/tweaks for roothide

install roothide/theos

bash -c "$(curl -fsSL https://raw.githubusercontent.com/roothide/theos/master/bin/install-theos)"

and it's always automatically synchronized and maintains 100% compatibility with the original theos.
Build package for roothide

for those simple tweaks that don't use the file api to access jailbreak files, just

make package with THEOS_PACKAGE_SCHEME=roothide
Using roothide APIs if you need to use the file apis to access jailbreak files in source code
```
#include <roothide.h>

//then using roothide api to access jailbreak files

const char* c_path = jbroot("/path/to/jb/file");

NSString* objc_path = jbroot(@"/path/to/jb/file");

std::string cpp_path = jbroot(std::string("/path/to/jb/file"));
```
the jbroot API can be used in C/C++/Objective-C/Swift and its fully compatible with building rootful/rootless package

In Swift project, it's better to use a swift bridging header file for #include <roothide.h> instead of using import roothide in swift source files. this will ensure your project is compatible with building rootful/rootless, ref to https://theos.dev/docs/swift#:~:text=Objective-C to Swift

Add these entitlements to your executable/app to make them work correctly with roothide:

<key>platform-application</key>
<true/>
<key>com.apple.private.security.no-sandbox</key>
<true/>
<key>com.apple.private.security.storage.AppBundles</key>
<true/>
<key>com.apple.private.security.storage.AppDataContainers</key>
<true/>

If you want to build your project with Xcode instead of theos,
here is the roothide sdk: devkit.zip
roothide/theos is now compatible with building roothide packages from existing tweak projects that use rootless path macros, there is a warning message to ensure you have read this document and you can define the DISABLE_ROOTLESS_COMPAT_WARNING macro to silence the message.
For more details about roothide, please refer to

support

roothideDev: https://twitter.com/roothideDev
roothide/theos-dev: https://discord.gg/qaCFxr33CV

more info

roothide discord server: https://discord.gg/ZvY2Yjw8GA
theos dev discord server: https://discord.gg/z4RTnrcbKW

mixpanel/mixpanel-iphone

Official iOS (Objective-C) Tracking Library for Mixpanel Analytics

Overview

The Mixpanel library for iOS is an open source project, and we'd love to see your contributions! We'd also love for you to come and work with us! Check out https://mixpanel.com/jobs/#openings for details. If you are using Swift, we recommend our Swift Library.

Check out our Advanced iOS - Objective-C Guide for additional advanced configurations and use cases, like setting up your project with European Union data storage.

Skip to a complete code example.

Quick Start Guide

Caution: From v4.0.0.beta.3 to v4.1.0, we have a bug that events with ampersand(&) will be rejected by the server. We recommend you update to v4.1.1 or above.

1. Install Mixpanel

You can install the Mixpanel iOS - Objective-C library by using CocoaPods or Carthage. You will need your project token for initializing your library. You can get your project token from project settings.

Installation Option 1: CocoaPods

If this is your first time using CocoaPods, Install CocoaPods using gem install cocoapods. Otherwise, continue to Step 3.
Run pod setup to create a local CocoaPods spec mirror.
Create a Podfile in your Xcode project directory by running pod init in your terminal, edit the Podfile generated, and add the following line: pod 'Mixpanel'.
Run pod install in your Xcode project directory. CocoaPods should download and install the Mixpanel library, and create a new Xcode workspace. Open up this workspace in Xcode or typing open *.xcworkspace in your terminal.

Installation Option 2: Carthage

Mixpanel supports Carthage to package your dependencies as a framework. Include the following dependency in your Cartfile:

github "mixpanel/mixpanel-iphone"

Check out the Carthage docs for more info.

Installation Option 3: Swift Package Manager

In Xcode, select File > Add Packages...
Enter the package URL for this repository and must select a version greater than or equal to v4.0.0

2. Initialize Mixpanel

To initialize the library, add `#Import "Mixpanel/Mixpanel.h" into "AppDelegate.m" and call sharedInstanceWithToken: with your project token as its argument in application:didFinishLaunchingWithOptions:.

#import "Mixpanel/Mixpanel.h"

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
...
  [Mixpanel sharedInstanceWithToken:@"YOUR_API_TOKEN" trackAutomaticEvents:NO];
...
}

See all configuration options

3. Send Data

Let's get started by sending event data. You can send an event from anywhere in your application. Better understand user behavior by storing details that are specific to the event (properties). After initializing the library, Mixpanel will automatically collect common mobile events. You can enable/disable automatic collection through your project settings. Also, Mixpanel automatically tracks some properties by default. learn more

Mixpanel *mixpanel = [Mixpanel sharedInstance];
[mixpanel track:@"Sign Up" properties:@{
  @"source": @"Pat's affiliate site",
  @"Opted out of email": @YES
}];

4. Check for Success

Open up Events in Mixpanel to view incoming events.

Once data hits our API, it generally takes ~60 seconds for it to be processed, stored, and queryable in your project.

Complete Code Example

Here's a runnable code example that covers everything in this quickstart guide.

#import "Mixpanel/Mixpanel.h"

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
...
  Mixpanel *mixpanel = [Mixpanel sharedInstanceWithToken:@"YOUR_API_TOKEN" trackAutomaticEvents:NO];
  [mixpanel track:@"Sign Up" properties:@{
    @"source": @"Pat's affiliate site",
    @"Opted out of email": @YES
  }];
...
}

FAQ

I want to stop tracking an event/event property in Mixpanel. Is that possible?

Yes, in Lexicon, you can intercept and drop incoming events or properties. Mixpanel won’t store any new data for the event or property you select to drop. See this article for more information.

I have a test user I would like to opt out of tracking. How do I do that?

Mixpanel’s client-side tracking library contains the optOutTracking() method, which will set the user’s local opt-out state to “true” and will prevent data from being sent from a user’s device. More detailed instructions can be found in the section, Opting users out of tracking.

Why aren't my events showing up?

To preserve battery life and customer bandwidth, the Mixpanel library doesn't send the events you record immediately. Instead, it sends batches to the Mixpanel servers every 60 seconds while your application is running, as well as when the application transitions to the background. You can call flush() manually if you want to force a flush at a particular moment.

[mixpanel flush];

If your events are still not showing up after 60 seconds, check if you have opted out of tracking. You can also enable Mixpanel debugging and logging, it allows you to see the debug output from the Mixpanel library. To enable it, set enableLogging to true.

mixpanel.enableLogging = YES;

Starting with iOS 14.5, do I need to request the user’s permission through the AppTrackingTransparency framework to use Mixpanel?

No, Mixpanel does not use IDFA so it does not require user permission through the AppTrackingTransparency(ATT) framework.

If I use Mixpanel, how do I answer app privacy questions for the App Store?

Please refer to our Apple App Developer Privacy Guidance

I want to know more!

No worries, here are some links that you will find useful:

Have any questions? Reach out to Mixpanel Support to speak to someone smart, quickly.

34306/FilzaJailedDS

Filza Jailed Darksword, support iOS 17.0-26.0.1. This repo open source the tweak inject into the Filza iPA (4.0.0 and back, 4.0.2 seems crash something)

FilzaJailedDS

Filza Jailed Darksword, support iOS 17.0-26.0.1 (except 18.7.2-18.7.7). This repo open source the tweak inject into the Filza iPA (4.0.0 and back, 4.0.2 seems crash something)

About iPhone 17 series and iPad M5: SUPPORT ETA SOON!👌

Note: I just change the name due to requested. But i think jailed is okay then

Credit

Thanks to Duy Tran for the sandbox hook token
Thanks to wh1te4ever for the super details darksword-kfun with offset/XPF
Thanks to opa334 for the XPF/krw
Thanks to CrazyMind90 for idea how to get sbx token with krw only
Thanks to roootdev for sandbox elevate in lara
And me 😄

rollbar/rollbar-apple

Objective-C & Swift library for remote crash, exception, error reporting, and logging with Rollbar. It works on all Apple *OS platforms (macOS, iOS, tvOS, watchOS, etc).

Rollbar Apple MonoRepo

Proactively discover, predict, and resolve errors in real-time with Rollbar’s error monitoring platform. Start tracking errors today!

Objective-C & Swift SDK for remote crash, exception, error reporting, and logging with Rollbar.

It works on all Apple *OS platforms (macOS, iOS, tvOS, watchOS, etc).

NOTE: This SDK is essentially a reincarnation of our Rollbar-iOS SDK that will be available for awhile in its current v1 version and will only maintained with fixes to bug or security issues if any. All the active development will be done within this SDK repository.

Key benefits of using Rollbar for Apple software platforms are:

Platforms: Rollbar supports all Apple OS platforms such as iOS, macOS, tvOS, watchOS, etc.
Automatic error grouping: Rollbar aggregates Occurrences caused by the same error into Items that represent application issues. Learn more about reducing log noise.
Advanced search: Filter items by many different properties. Learn more about search.
Customizable notifications: Rollbar supports several messaging and incident management tools where your team can get notified about errors and important events by real-time alerts. Learn more about Rollbar notifications.

The Apple SDK is GA. Learn more: https://docs.rollbar.com/docs/apple

Codebase status (code quality and CI build)

Package Distribution Systems Status

Setup Instructions

Sign up for a Rollbar account
Follow the Installation instructions in our Rollbar-Apple SDK docs to install the SDK modules.

Usage and Reference

For complete usage instructions and configuration reference, see our Rollbar-Apple SDK docs.

Release History & Changelog

See our Releases page for a list of all releases, including changes.

Contributing

Fork it
Create your feature branch (git checkout -b my-new-feature)
Commit your changes (git commit -am 'Added some feature')
Push to the branch (git push origin my-new-feature)
Create new Pull Request

Help / Support

git-up/GitUp

The Git interface you've been missing all your life has finally arrived.

GitUp

Work quickly, safely, and without headaches. The Git interface you've been missing all your life has finally arrived.

Git recently celebrated its 10 years anniversary, but most engineers are still confused by its intricacy (3 of the top 5 questions of all time on Stack Overflow are Git related). Since Git turns even simple actions into mystifying commands (“git add” to stage versus “git reset HEAD” to unstage anyone?), it’s no surprise users waste time, get frustrated, distract the rest of their team for help, or worse, screw up their repo!

GitUp is a bet to invent a new Git interaction model that lets engineers of all levels work quickly, safely, and without headaches. It's unlike any other Git client out there from the way it’s built (it interacts directly with the Git database on disk), to the way it works (you manipulate the repository graph instead of manipulating commits).

With GitUp, you get a truly efficient Git client for Mac:

A live and interactive repo graph (edit, reorder, fixup, merge commits…),
Unlimited undo / redo of almost all operations (even rebases and merges),
Time Machine like snapshots for 1-click rollbacks to previous repo states,
Features that don’t even exist natively in Git like a visual commit splitter or a unified reflog browser,
Instant search across the entire repo including diff contents,
A ridiculously fast UI, often faster than the command line.

In addition, GitUp’s core and main UI elements are available as an open-source framework, GitUpKit. You can use it to build your very own Git GUI! GitUpKit has already enabled the creation of some unique apps:

Retcon, a Git client that makes rewriting history fast and flexible

GitUp was created by @swisspol in late 2014 as a bet to reinvent the way developers interact with Git. After several months of work, it was made available in pre-release early 2015 and reached the top of Hacker News along with being featured by Product Hunt and Daring Fireball. 30,000 lines of code later, GitUp reached 1.0 mid-August 2015 and was released open source as a gift to the developer community.

Getting Started

Official website: https://gitup.co

Download:

Latest release on GitHub: https://github.com/git-up/GitUp/releases
Homebrew (Not maintained by GitUp developers): brew install gitup-app

Read the docs and use GitHub Issues for support & feedback.

Releases notes are available at https://github.com/git-up/GitUp/releases. Builds tagged with a v (e.g. v1.2.3) are released on the "Stable" channel, while builds tagged with a b (e.g. b1234) are only released on the "Continuous" channel. You can change the update channel used by GitUp in the app preferences.

Build

To build GitUp yourself, simply run the command git clone --recursive https://github.com/git-up/GitUp.git in Terminal, then open the GitUp/GitUp.xcodeproj Xcode project and hit Run.

IMPORTANT: If you do not have an Apple ID with a developer account for code signing Mac apps, the build will fail with a code signing error. Simply delete the "Code Signing Identity" build setting of the "Application" target to work around the issue:

Alternatively, if you do have a developer account, you can create the file "Xcode-Configurations/DEVELOPMENT_TEAM.xcconfig" with the following build setting as its content:

DEVELOPMENT_TEAM = [Your TeamID]

For a more detailed description of this, you can have a look at the comments at the end of the file "Xcode-Configurations/Base.xcconfig".

GitUpKit

GitUp is built as a thin layer on top of a reusable generic Git toolkit called "GitUpKit". This means that you can use that same GitUpKit framework to build your very own Git UI!

GitUpKit has a very different goal than ObjectiveGit. Instead of offering extensive raw bindings to libgit2, GitUpKit only uses a minimal subset of libgit2 and reimplements everything else on top of it (it has its own "rebase engine" for instance). This allows it to expose a very tight and consistent API, that completely follows Obj-C conventions and hides away the libgit2 complexity and sometimes inconsistencies. GitUpKit adds on top of that a number of exclusive and powerful features, from undo/redo and Time Machine like snapshots, to entire drop-in UI components.

Architecture

The GitUpKit source code is organized as 2 independent layers communicating only through the use of public APIs:

Base Layer (depends on Foundation only and is compatible with OS X and iOS)

Core/: wrapper around the required minimal functionality of libgit2, on top of which is then implemented all the Git functionality required by GitUp (note that GitUp uses a slightly customized fork of libgit2)
Extensions/: categories on the Core classes to add convenience features implemented only using the public APIs

UI Layer (depends on AppKit and is compatible with OS X only)

Interface/: low-level view classes e.g. GIGraphView to render the GitUp Map view
Utilities/: interface utility classes e.g. the base view controller class GIViewController
Components/: reusable single-view view controllers e.g. GIDiffContentsViewController to render a diff
Views/: high-level reusable multi-views view controllers e.g. GIAdvancedCommitViewController to implement the entire GitUp Advanced Commit view

IMPORTANT: If the preprocessor constant DEBUG is defined to a non-zero value when building GitUpKit (this is the default when building in "Debug" configuration), a number of extra consistency checks are enabled at run time as well as extra logging. Be aware that this overhead can significantly affect performance.

GitUpKit API

Using the GitUpKit API should be pretty straightforward since it is organized by functionality (e.g. repository, branches, commits, interface components, etc...) and a best effort has been made to name functions clearly.

Regarding the "Core" APIs, the best way to learn them is to peruse the associated unit tests - for instance see the branch tests for the branch API.

Here is some sample code to get you started (error handling is left as an exercise to the reader):

Opening and browsing a repository:

// Open repo
GCRepository* repo = [[GCRepository alloc] initWithExistingLocalRepository:<PATH> error:NULL];

// Make sure repo is clean
assert([repo checkClean:kGCCleanCheckOption_IgnoreUntrackedFiles error:NULL]);

// List all branches
NSArray* branches = [repo listAllBranches:NULL];
NSLog(@"%@", branches);

// Lookup HEAD
GCLocalBranch* headBranch;  // This would be nil if the HEAD is detached
GCCommit* headCommit;
[repo lookupHEADCurrentCommit:&headCommit branch:&headBranch error:NULL];
NSLog(@"%@ = %@", headBranch, headCommit);

// Load the *entire* repo history in memory for fast access, including all commits, branches and tags
GCHistory* history = [repo loadHistoryUsingSorting:kGCHistorySorting_ReverseChronological error:NULL];
assert(history);
NSLog(@"%lu commits total", history.allCommits.count);
NSLog(@"%@\n%@", history.rootCommits, history.leafCommits);

Modifying a repository:

// Take a snapshot of the repo
GCSnapshot* snapshot = [repo takeSnapshot:NULL];

// Create a new branch and check it out
GCLocalBranch* newBranch = [repo createLocalBranchFromCommit:headCommit withName:@"temp" force:NO error:NULL];
NSLog(@"%@", newBranch);
assert([repo checkoutLocalBranch:newBranch options:0 error:NULL]);

// Add a file to the index
[[NSData data] writeToFile:[repo.workingDirectoryPath stringByAppendingPathComponent:@"empty.data"] atomically:YES];
assert([repo addFileToIndex:@"empty.data" error:NULL]);

// Check index status
GCDiff* diff = [repo diffRepositoryIndexWithHEAD:nil options:0 maxInterHunkLines:0 maxContextLines:0 error:NULL];
assert(diff.deltas.count == 1);
NSLog(@"%@", diff);

// Create a commit
GCCommit* newCommit = [repo createCommitFromHEADWithMessage:@"Added file" error:NULL];
assert(newCommit);
NSLog(@"%@", newCommit);

// Restore repo to saved snapshot before topic branch and commit were created
BOOL success = [repo restoreSnapshot:snapshot withOptions:kGCSnapshotOption_IncludeAll reflogMessage:@"Rolled back" didUpdateReferences:NULL error:NULL];
assert(success);
  
// Make sure topic branch is gone
assert([repo findLocalBranchWithName:@"temp" error:NULL] == nil);
  
// Update workdir and index to match HEAD
assert([repo resetToHEAD:kGCResetMode_Hard error:NULL]);

Complete Example #1: GitDown

GitDown is a very basic app that prompts the user for a repo and displays an interactive and live-updating list of its stashes (all with ~20 lines of code in -[AppDelegate applicationDidFinishLaunching:]):

Through GitUpKit, this basic app also gets for free unlimited undo/redo, unified and side-by-side diffs, text selection and copy, keyboard shortcuts, etc...

This source code also demonstrates how to use some other GitUpKit view controllers as well as building a customized one.

Complete Example #2: GitDiff

GitDiff demonstrates how to create a view controller that displays a live updating diff between HEAD and the workdir à la git diff HEAD:

Complete Example #3: GitY

GitY is a GitX clone built using GitUpKit and less than 200 lines of code:

Complete Example #4: iGit

iGit is a test iOS app that simply uses GitUpKit to clone a GitHub repo and perform a commit.

Contributing

See CONTRIBUTING.md.

Credits

@swisspol: concept and code
@wwayneee: UI design
@jayeb: website

Also a big thanks to the fine libgit2 contributors without whom GitUp would have never existed!

License

IMPORTANT: GitUp includes some other open-source projects and such projects remain under their own license.

kif-framework/KIF

Keep It Functional - An iOS Functional Testing Framework

IMPORTANT! Even though KIF is used to test your UI, you need to add it to your Unit Test target, not your UI Test target. The magic of KIF is that it allows you to drive your UI from your unit tests and reap all the advantages of testing in-process.

KIF iOS Integration Testing Framework

KIF, which stands for Keep It Functional, is an iOS integration test framework. It allows for easy automation of iOS apps by leveraging the accessibility attributes that the OS makes available for those with visual disabilities.

KIF builds and performs the tests using a standard XCTest testing target. Testing is conducted synchronously in the main thread (running the run loop to force the passage of time) allowing for more complex logic and composition. This also allows KIF to take advantage of the Xcode Test Navigator, command line build tools, and Bot test reports.

KIF uses undocumented Apple APIs. This is true of most iOS testing frameworks, and is safe for testing purposes, but it's important that KIF does not make it into production code, as it will get your app submission denied by Apple. Follow the instructions below to ensure that KIF is configured correctly for your project.

Actively supports Xcode 16 and iOS 15 if you need support for an earlier version please use an earlier release.

Features

Minimizes Indirection

All of the tests for KIF are written in Objective-C. This allows for maximum integration with your code while minimizing the number of layers you have to build.

Easy Configuration

KIF integrates directly into your Xcode project, so there's no need to run an additional web server or install any additional packages.

Wide OS and Xcode coverage

KIF's test suite is being run against iOS 8+ and Xcode 7+. Lower versions will likely still work, but your mileage may vary. We do our best to retain backwards compatibility as much as possible.

Test Like a User

KIF attempts to imitate actual user input. Automation is done using tap events wherever possible.

Automatic Integration with Xcode Testing Tools

You can easily run a single KIF test with the Test Navigator or kick off nightly acceptance tests with Bots.

See KIF in Action

KIF uses techniques described below to validate its internal functionality. You can see a test suite that exercises its entire functionality by simply building and testing the KIF scheme with ⌘U. Look at the tests in the "Tests" group for ideas on how to build your own tests.

Installation (with Swift Package Manager)

Add the KIF package as a dependency:

.package(url: "https://github.com/kif-framework/KIF", from: {VERSION})

Installation (with CocoaPods)

⚠️ CocoaPods is no longer supported and will not be receiving new updates

CocoaPods are the easiest way to get set up with KIF.

The first thing you will want to do is set up a test target you will be using for KIF. You may already have one named MyApplication_Tests if you selected to automatically create unit tests. If you did, you can keep using it if you aren't using it for unit tests. Otherwise, follow these directions to create a new one.

Select your project in Xcode and click on "Add Target" in the bottom left corner of the editor. Select iOS -> Test -> iOS Unit Testing Bundle. Give it a product name like "Acceptance Tests", "UI Tests", or something that indicates the intent of your testing process.

The testing target will add a header and implementation file, likely "Acceptance_Tests.m/h" to match your target name. Delete those.

Once your test target set up, add the following to your Podfile file. Use your target's name as appropriate.

target 'Your Apps' do
  ...
end

target 'Acceptance Tests' do
  pod 'KIF', :configurations => ['Debug']
end

After running pod install complete the tasks in Final Test Target Configurations below for the final details on getting your tests to run.

Create a Testing Target

You'll need to create a test target for your app. You may already have one named MyApplicationTests if you selected to automatically create unit tests when you created the project. If you did, you can keep using it if you aren't using it for unit tests. Otherwise, follow these directions to create a new one.

The testing target will add a header and implementation file, likely "Acceptance_Tests.m/h" to match your target name. Delete those.

Configure the Testing Target

Now that you have a target for your tests, add the tests to that target. With the project settings still selected in the Project Navigator, and the new integration tests target selected in the project settings, select the "Build Phases" tab. Under the "Link Binary With Libraries" section, hit the "+" button. In the sheet that appears, select "libKIF.a" and click "Add". Repeat the process for CoreGraphics.framework and QuartzCore.framework.

KIF requires the IOKit.framework, but it is not located with the other system frameworks. To link to it, add "-framework IOKit" to the "Other Linker Flags" build setting.

KIF takes advantage of Objective C's ability to add categories on an object, but this isn't enabled for static libraries by default. To enable this, add the -ObjC flag to the "Other Linker Flags" build setting on your test bundle target as shown below.

Read Final Test Target Configurations below for the final details on getting your tests to run.

Final Test Target Configurations

You need your tests to run hosted in your application. Xcode does this for you by default when creating a new testing bundle target, but if you're migrating an older bundle, follow the steps below.

First add your application by selecting "Build Phases", expanding the "Target Dependencies" section, clicking on the "+" button, and in the new sheet that appears selecting your application target and clicking "Add".

Next, configure your bundle loader. In "Build Settings", expand "Linking" and edit "Bundle Loader" to be $(TEST_HOST). Expand the "Testing" section and edit "Test Host" to be $(BUILT_PRODUCTS_DIR)/MyApplication.app/MyApplication where MyApplication is the name of your app. Also make sure that "Wrapper Extension" is set to xctest.

The last step is to configure your unit tests to run when you trigger a test (⌘U). Click on your scheme name and select "Edit Scheme…". Click on "Test" in the sidebar followed by the "+" in the bottom left corner. Select your testing target and click "OK".

Example test cases

With your project configured to use KIF, it's time to start writing tests. There are two main classes used in KIF testing: the test case (KIFTestCase, subclass of XCTestCase) and the UI test actor (KIFUITestActor). The XCTest test runner loads the test case classes and executes their test. Inside these tests, the tester performs the UI operations which generally imitate a user interaction. Three of the most common tester actions are "tap this view," "enter text into this view," and "wait for this view." These steps are included as factory methods on KIFUITestActor in the base KIF implementation.

KIF relies on the built-in accessibility of iOS to perform its test steps. As such, it's important that your app is fully accessible. This is also a great way to ensure that your app is usable by everyone. Giving your views reasonable labels is usually a good place to start when making your application accessible. More details are available in Apple's Documentation.

The first step is to create a test class to test some functionality. In our case, we will create a login test (LoginTests). Create a new class that inherits from KIFTestCase. You may have to update the import to point to <KIF/KIF.h>. The test method name provides a unique identifier. Your KIFTestCase subclass should look something like this:

LoginTestCase.h

#import <KIF/KIF.h>

@interface LoginTests : KIFTestCase
@end

LoginTestCase.m

#import "LoginTests.h"
#import "KIFUITestActor+EXAdditions.h"

@implementation LoginTests

- (void)beforeEach
{
    [tester navigateToLoginPage];
}

- (void)afterEach
{
    [tester returnToLoggedOutHomeScreen];
}

- (void)testSuccessfulLogin
{
    [tester enterText:@"user@example.com" intoViewWithAccessibilityLabel:@"Login User Name"];
    [tester enterText:@"thisismypassword" intoViewWithAccessibilityLabel:@"Login Password"];
    [tester tapViewWithAccessibilityLabel:@"Log In"];

    // Verify that the login succeeded
    [tester waitForTappableViewWithAccessibilityLabel:@"Welcome"];
}

@end

Most of the tester actions in the test are already defined by the KIF framework, but -navigateToLoginPage and -returnToLoggedOutHomeScreen are not. These are examples of custom actions which are specific to your application. Adding such steps is easy, and is done using a factory method in a category of KIFUITestActor, similar to how we added the scenario.

KIFUITestActor+EXAdditions.h

#import <KIF/KIF.h>

@interface KIFUITestActor (EXAdditions)

- (void)navigateToLoginPage;
- (void)returnToLoggedOutHomeScreen;

@end

KIFUITestActor+EXAdditions.m

#import "KIFUITestActor+EXAdditions.h"

@implementation KIFUITestActor (EXAdditions)

- (void)navigateToLoginPage
{
    [self tapViewWithAccessibilityLabel:@"Login/Sign Up"];
    [self tapViewWithAccessibilityLabel:@"Skip this ad"];
}

- (void)returnToLoggedOutHomeScreen
{
    [self tapViewWithAccessibilityLabel:@"Logout"];
    [self tapViewWithAccessibilityLabel:@"Logout"]; // Dismiss alert.
}

@end

Everything should now be configured. When you run the integration tests using the test button, ⌘U, or the Xcode Test Navigator (⌘5).

Use with other testing frameworks

KIFTestCase is not necessary for running Tests. Tests can run directly in XCTestCase or any subclass. The basic requirement is that when you call tester or system, self must be an instance of XCTestCase and you must call KIFEnableAccessibility in setUp.

For example, the following Specta test works without any changes to KIF or Specta:

#import <Specta.h>
#import <KIF.h>

SpecBegin(App)

describe(@"Tab controller", ^{

  it(@"should show second view when I tap on the second tab", ^{
    [tester tapViewWithAccessibilityLabel:@"Second" traits:UIAccessibilityTraitButton];
    [tester waitForViewWithAccessibilityLabel:@"Second View"];
  });

});

SpecEnd

If you want to use KIF with a test runner that does not subclass XCTestCase, your runner class just needs to implement the KIFTestActorDelegate protocol which contains two required methods.

(void)failWithException:(NSException *)exception stopTest:(BOOL)stop;
(void)failWithExceptions:(NSArray *)exceptions stopTest:(BOOL)stop;

In the first case, the test runner should log the exception and halt the test execution if stop is YES. In the second, the runner should log all the exceptions and halt the test execution if stop is YES. The exceptions take advantage of KIF's extensions to NSException that include the lineNumber and filename in the exception's userData to record the error's origin.

Use with Swift

Since it's easy to combine Swift and Objective-C code in a single project, KIF is fully capable of testing apps written in both Objective-C and Swift.

If you want to write your test cases in Swift, you'll need to keep two things in mind.

Your test bundle's bridging header will need to #import <KIF/KIF.h>, since KIF is a static library and not a header.
The tester and system keywords are C preprocessor macros which aren't available in Swift. You can easily write a small extension to XCTestCase or any other class to access them:

extension XCTestCase {
    func tester(file : String = #file, _ line : Int = #line) -> KIFUITestActor {
        return KIFUITestActor(inFile: file, atLine: line, delegate: self)
    }

    func system(file : String = #file, _ line : Int = #line) -> KIFSystemTestActor {
        return KIFSystemTestActor(inFile: file, atLine: line, delegate: self)
    }
}

extension KIFTestActor {
    func tester(file : String = #file, _ line : Int = #line) -> KIFUITestActor {
        return KIFUITestActor(inFile: file, atLine: line, delegate: self)
    }

    func system(file : String = #file, _ line : Int = #line) -> KIFSystemTestActor {
        return KIFSystemTestActor(inFile: file, atLine: line, delegate: self)
    }
}

See Documentation/Examples/Testable Swift for sample code.

Troubleshooting

Simulator launches but app doesn't appear, steps time out after 10 seconds

This issue occurs when XCTest does not have a valid Test Host. Reread the instructions above with regards to the "Bundle Loader" and "Test Host" settings. You may have missed something.

Step fails because a view cannot be found

If KIF is failing to find a view, the most likely cause is that the view doesn't have its accessibility label set. If the view is defined in a xib, then the label can be set using the inspector. If it's created programmatically, simply set the accessibilityLabel attribute to the desired label.

If the label is definitely set correctly, take a closer look at the error given by KIF. This error should tell you more specifically why the view was not accessible. If you are using -waitForTappableViewWithAccessibilityLabel:, then make sure the view is actually tappable. For items such as labels which cannot become the first responder, you may need to use -waitForViewWithAccessibilityLabel: instead.

Unrecognized selector when first trying to run

If the first time you try to run KIF you get the following error:

2011-06-13 13:54:53.295 Testable (Integration Tests)[12385:207] -[NSFileManager createUserDirectory:]: unrecognized selector sent to instance 0x4e02830
2011-06-13 13:54:53.298 Testable (Integration Tests)[12385:207] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSFileManager createUserDirectory:]: unrecognized selector sent to instance 0x4e02830'

or if you get another "unrecognized selector" error inside the KIF code, make sure that you've properly set the -ObjC flag as described above. Without this flag your app can't access the category methods that are necessary for KIF to work properly.

Continuous Integration

A continuous integration (CI) process is highly recommended and is extremely useful in ensuring that your application stays functional. The easiest way to do this will be with Xcode, either using Bots, or Jenkins or another tool that uses xcodebuild. For tools using xcodebuild, review the manpage for instructions on using test destinations.

Contributing

We're glad you're interested in KIF, and we'd love to see where you take it.

Any contributors to the master KIF repository must sign the Individual Contributor License Agreement (CLA). It's a short form that covers our bases and makes sure you're eligible to contribute.

When you have a change you'd like to see in the master repository, send a pull request. Before we merge your request, we'll make sure you're in the list of people who have signed a CLA.

Thanks, and happy testing!

alexzielenski/Mousecape

Cursor Manager for OSX

Mousecape

A free cursor manager for Mac OS 10.8+ built using private, nonintrusive CoreGraphics APIs.

How it works

Mousecape works by calling the API calls that Apple uses to initialize the system cursors in the system and it registers a daemon that will automatically apply the cursor on login and when cursors get unregistered.

It is unintrusive and works in the background. You just need to open the app, click Mousecape --> Install Helper Tool, apply your cursor and you're done!

Where do I get cursors?

A pack of cursors in Mousecape is called a cape, each cape contains a multiple scales of representations of many cursors. For example, the Arrow cursor can have 1x, 2x, 5x, and 10x representations while the Wait cursor can have 1x, and 2x.

There is an example cape file included in this Git Repo located here for download. It is a remake of Max Rudberg's loved Svanslös cursors generously crafted by Max for us to use. Simply double click the cape file with Mousecape on your system and it will be imported into your library.

How can I create my own cape?

You can create a new cape document in the Mousecape app by hitting ⌘N (Command-N) and editing it with ⌘E. Click the "+" button to add cursors to customize and symply drag your images into the fields provided.

How do animated cursors work?

When you want to animate a cursor, change the value in the frames field in the edit window and make sure frame duration is how you want it. Next, create an image that has all of your cursor frames stacked on top of each other vertically. Mousecape will traverse down the image for each frame, using a box the same size as whatever you put in the size field.

How can I say thanks?

Tell your friends.

Where can I get a copy of this sweet tool?

In the releases section of this GitHub page. There are stable reases there. The current version is 1813.

There's now the beginning of a wiki

Look for the wiki symbol in the toolbar here on this GitHub page or through here wiki section

LICENSE

I worked very hard researching the private methods used in Mousecape and creating this app. Please respect me and my work by not using any of the information provided here for commercial purposes.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Any redistribution, use, or modification is done solely for personal benefit and not for any commercial purpose or for monetary gain

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

aws-amplify/aws-sdk-ios

AWS SDK for iOS. For more information, see our web site:

⚠️ The AWS SDK for iOS is Deprecated.

We recommend that you start using AWS Amplify for Swift, our modern feature-rich library designed specifically for building cloud-connected apps powered by AWS. You can refer to the AWS SDK for iOS migration guide to help you transition to AWS Amplify for Swift. This version is scheduled to reach End of Support on August 1, 2026. After this date, no further updates of any kind will be provided. See maintenance policy for more information about the Amplify Client Library lifecycle.

To use the AWS SDK for iOS directly you can refer to the AWS SDK Documentation here and follow the setup instructions below. You can also look at sample apps in the AWS SDK for iOS Samples repo.

Setup

To use the AWS SDK for iOS, you will need the following installed on your development machine:

Xcode 11.0 or later
iOS 12 or later

Include the SDK for iOS in an Existing Application

We have a couple samples applications which showcase how to use the AWS SDK for iOS. Please note that the code in these sample applications is not of production quality, and should be considered as exactly what we called them: samples.

There are several ways to integrate the AWS Mobile SDK for iOS into your own project:

You should use ONE and only one of these ways to import the AWS Mobile SDK. Importing the SDK in multiple ways loads duplicate copies of the SDK into the project and causes compiler/linker errors.

Note: If you are using XCFrameworks (i.e., either Swift Package Manager, Carthage, or Dynamic Frameworks), some modules are named with the XCF suffix to work around a Swift issue. AWSMobileClient is named as AWSMobileClientXCF and AWSLocation is named as AWSLocationXCF. To use the AWSMobileClient or AWSLocation SDKs, import them as:

import AWSMobileClientXCF
import AWSLocationXCF

and use it your app code without the XCF suffix.

AWSMobileClient.default().initialize() 
let locationClient = AWSLocation.default()

Swift Package Manager

Swift Package Manager is distributed with Xcode. To start adding the AWS SDK to your iOS project, open your project in Xcode and select File > Swift Packages > Add Package Dependency.
Enter the URL for the AWS SDK for iOS Swift Package Manager GitHub repo (https://github.com/aws-amplify/aws-sdk-ios-spm) into the search bar and click Next.

NOTE: This URL is not the main URL of the SDK. We maintain the Swift Package Manager manifest (Package.swift) file for this library in a separate repo so that apps that use the SDK do not have to download the entire source repository in order to consume the binary targets.
You'll see the repository rules for which version of the SDK you want Swift Package Manager to install. Choose the first rule, Version, and select Up to Next Minor as it will use the latest compatible version of the dependency that can be detected from the main branch, then click Next.

NOTE: The AWS Mobile SDK for iOS does not use Semantic Versioning, and may introduce breaking API changes on minor version releases. We recommend setting your Version rule to Up to Next Minor and evaluating minor version releases to ensure they are compatible with your app.
Choose which of the libraries you want added to your project. Always select the AWSCore SDK. The remaining SDKs to install will vary based on which SDK you're trying to install. Most SDKs rely only on AWSCore, but for a full dependency list, see the README-spm-support file.

Note: AWSLex is not currently supported for the arm64 architecture through Swift Package Manager due to conflicts with a packaged binary dependency.

Select all that are appropriate, then click Finish.

You can always go back and modify which SPM packages are included in your project by opening the Swift Packages tab for your project: Click on the Project file in the Xcode navigator, then click on your project's icon, then select the Swift Packages tab.

CocoaPods

The AWS Mobile SDK for iOS is available through CocoaPods. If you have not installed CocoaPods, install CocoaPods by running the command:
```
 $ gem install cocoapods
 $ pod setup
```
Depending on your system settings, you may have to use sudo for installing cocoapods as follows:
```
 $ sudo gem install cocoapods
 $ pod setup
```
In your project directory (the directory where your *.xcodeproj file is), run the following to create a Podfile in your project.
```
 $ pod init
```
Edit the podfile to include the pods you want to integrate into your project. For example, if you need auth, you can use AWSMobileClient, and if you need analytics, you add AWSPinpoint. As a result, your podfile might look something like this:

target 'YourTarget' do
    pod 'AWSMobileClient'
    pod 'AWSPinpoint'
end

For a complete list of our pods, check out the .podspec files in the root directory of this project.

Then run the following command:
```
 $ pod install --repo-update
```
To open your project, open the newly generated *.xcworkspace file in your project's directory with XCode. You can do this by issuing the following command in your project folder:
```
 $ xed .
```
Note: Do NOT use *.xcodeproj. If you open up a project file instead of a workspace, you may receive the following error:
```
 ld: library not found for -lPods-AWSCore
 clang: error: linker command failed with exit code 1 (use -v to see invocation)
```

Carthage

XCFrameworks (recommended)

Carthage supports XCFrameworks in Xcode 12 or above. Follow the steps below to consume the AWS SDK for iOS using XCFrameworks:

Install Carthage 0.37.0 or greater.
Add the following to your Cartfile:
```
 github "aws-amplify/aws-sdk-ios"
```

Then run the following command:

 $ carthage update --use-xcframeworks --no-use-binaries

As of Carthage 0.37.0, prebuilt binaries using XCFrameworks are not supported, as mentioned in the Carthage release notes - https://github.com/Carthage/Carthage/releases/tag/0.37.0

On your application targets’ General settings tab, in the Embedded Binaries section, drag and drop each xcframework you want to use from the Carthage/Build folder on disk.

Frameworks with "fat libraries" (not recommended)

To build platform-specific framework bundles with multiple architectures in the binary, (Xcode 11 and below)

Install the latest version of Carthage.
Add the following to your Cartfile:
```
 github "aws-amplify/aws-sdk-ios"
```
Then run the following command:
```
 $ carthage update
```
With your project open in Xcode, select your Target. Under General tab, find Frameworks, Libraries, and Embedded Content and then click the + button.
Click the Add Other... button, then "Add Files..." in the popup menu, then navigate to the AWS<#ServiceName#>.framework files under Carthage > Build > iOS and select them. Do not check the Destination: Copy items if needed checkbox if prompted. Add the frameworks that you need for you specific use case. For example, if you are using AWSMobileClient and AWSPinpoint, you will want to add the following frameworks:
- AWSAuthCore.framework
- AWSCognitoIdentityProvider.framework
- AWSCognitoIdentityProviderASF.framework
- AWSCore.framework
- AWSMobileClient.framework
- AWSPinpoint.framework

Under the Build Phases tab in your Target, click the + button on the top left and then select New Run Script Phase. Then setup the build phase as follows. Make sure this phase is below the Embed Frameworks phase.

 Shell /bin/sh
 
 bash "${BUILT_PRODUCTS_DIR}/${FRAMEWORKS_FOLDER_PATH}/AWSCore.framework/strip-frameworks.sh"
 
 Show environment variables in build log: Checked
 Run script only when installing: Not checked
 
 Input Files: Empty
 Output Files: Empty

Note: Currently, the AWS SDK for iOS builds the Carthage binaries using the latest released version of Xcode. To consume the pre-built binaries your Xcode version needs to be the same, else you have to build the frameworks on your machine by passing --no-use-binaries flag to carthage update command.

Frameworks

XCFramework setup

Starting AWS SDK iOS version 2.22.1, SDK binaries are released as XCFrameworks. Follow the steps below to install XCFramework.

Download the latest SDK. Older SDK versions can be downloaded from https://releases.amplify.aws/aws-sdk-ios/aws-ios-sdk-#.#.#.zip, where #.#.# represents the version number. So for version 2.23.3, the download link is https://releases.amplify.aws/aws-sdk-ios/aws-ios-sdk-2.23.3.zip.

Note1: If you are using version < 2.22.1 please refer to the "Legacy framework setup" section below. Note2: To download version < 2.23.3 use this link https://sdk-for-ios.amazonwebservices.com/aws-ios-sdk-#.#.#.zip

Uncompress the ZIP file
On your application targets’ General settings tab, in the Embedded Binaries section, drag and drop each xcframework you want to use from the downloaded folder.

Legacy framework setup

Download the required SDK using https://sdk-for-ios.amazonwebservices.com/aws-ios-sdk-#.#.#.zip, where #.#.# represents the version number. So for version 2.10.2, the download link is https://sdk-for-ios.amazonwebservices.com/aws-ios-sdk-2.10.2.zip.

Note: If you are using version > 2.22.0 please refer to the "XCFramework setup" section above.

With your project open in Xcode, select your Target. Under General tab, find Embedded Binaries and then click the + button.
Click the Add Other... button, navigate to the AWS<#ServiceName#>.framework files and select them. Check the Destination: Copy items if needed checkbox when prompted. Add the frameworks that you need for you specific use case. For example, if you are using AWSMobileClient and AWSPinpoint, you will want to add the following frameworks:
- AWSAuthCore.framework
- AWSCognitoIdentityProvider.framework
- AWSCognitoIdentityProviderASF.framework
- AWSCore.framework
- AWSMobileClient.framework
- AWSPinpoint.framework

 Shell /bin/sh
 
 bash "${BUILT_PRODUCTS_DIR}/${FRAMEWORKS_FOLDER_PATH}/AWSCore.framework/strip-frameworks.sh"
 
 Show environment variables in build log: Checked
 Run script only when installing: Not checked
 
 Input Files: Empty
 Output Files: Empty

Update the SDK to a Newer Version

When we release a new version of the SDK, you can pick up the changes as described below.

CocoaPods

Run the following command in your project directory. CocoaPods automatically picks up the new changes.
```
 $ pod update
```
Note: If your pod is having an issue, you can delete Podfile.lock and Pods/ then run pod install to cleanly install the SDK.

Carthage

Run the following command in your project directory. Carthage automatically picks up the new changes.
```
 $ carthage update
```

Frameworks

In Xcode's Project Navigator, type "AWS" to find the AWS Frameworks or XCFrameworks that you manually added to your project. Select all of the AWS Frameworks and hit Delete on your keyboard. Then select Move to Trash.
Follow the installation process above to include the new version of the SDK.

Getting Started with Swift

Import the AWSCore header in the application delegate.
```
import AWSCore
```

Create a default service configuration by adding the following code snippet in the application:didFinishLaunchingWithOptions: application delegate method.

let credentialsProvider = AWSCognitoCredentialsProvider(
    regionType: CognitoRegionType,
    identityPoolId: CognitoIdentityPoolId)
let configuration = AWSServiceConfiguration(
    region: DefaultServiceRegionType,
    credentialsProvider: credentialsProvider)
AWSServiceManager.default().defaultServiceConfiguration = configuration

In Swift file you want to use the SDK, import the appropriate headers for the services you are using. The header file import convention is import AWSServiceName, as in the following examples:
```
import AWSS3
import AWSDynamoDB
import AWSSQS
import AWSSNS
```

Make a call to the AWS services.

let dynamoDB = AWSDynamoDB.default()
let listTableInput = AWSDynamoDBListTablesInput()
dynamoDB.listTables(listTableInput!).continueWith { (task:AWSTask<AWSDynamoDBListTablesOutput>) -> Any? in
    if let error = task.error as? NSError {
    print("Error occurred: \(error)")
        return nil
    }

    let listTablesOutput = task.result

    for tableName in listTablesOutput!.tableNames! {
        print("\(tableName)")
    }

    return nil
}

Note: Most of the service client classes have a singleton method to get a default client. The naming convention is + defaultSERVICENAME (e.g. + defaultDynamoDB in the above code snippet). This singleton method creates a service client with defaultServiceConfiguration, which you set up in step 5, and maintains a strong reference to the client.

Getting Started with Objective-C

Import the AWSCore header in the application delegate.
```
@import AWSCore;
```

Create a default service configuration by adding the following code snippet in the application:didFinishLaunchingWithOptions: application delegate method.

AWSCognitoCredentialsProvider *credentialsProvider = [[AWSCognitoCredentialsProvider alloc] initWithRegionType:CognitoRegionType
                                                                                                identityPoolId:CognitoIdentityPoolId];
AWSServiceConfiguration *configuration = [[AWSServiceConfiguration alloc] initWithRegion:DefaultServiceRegionType
                                                                     credentialsProvider:credentialsProvider];
AWSServiceManager.defaultServiceManager.defaultServiceConfiguration = configuration;

Import the appropriate headers for the services you are using. The header file import convention is @import AWSServiceName;, as in the following examples:
```
@import AWSS3;
@import AWSDynamoDB;
@import AWSSQS;
@import AWSSNS;
```

Make a call to the AWS services.

AWSSNS *sns = [AWSSNS defaultSNS];
AWSSNSListTopicsInput *listTopicsInput = [AWSSNSListTopicsInput new];
[[sns listTopics:listTopicsInput] continueWithBlock:^id(AWSTask *task) {
    // Do something with the response
    return nil;
}];

Note: Most of the service client classes have a singleton method to get a default client. The naming convention is + defaultSERVICENAME (e.g. + defaultS3SNS in the above code snippet). This singleton method creates a service client with defaultServiceConfiguration, which you set up in step 5, and maintains a strong reference to the client.

Working with AWSTask

The SDK returns AWSTask objects when operating on asynchronous operations to avoid blocking the UI thread.

The AWSTask class is a renamed version of BFTask from the Bolts framework. For complete documentation on Bolts, see the Bolts-iOS repo

Logging

As of version 2.5.4 of this SDK, logging utilizes CocoaLumberjack, a flexible, fast, open source logging framework. It supports many capabilities including the ability to set logging level per output target, for instance, concise messages logged to the console and verbose messages to a log file.

CocoaLumberjack logging levels are additive such that when the level is set to verbose, all messages from the levels below verbose are logged. It is also possible to set custom logging to meet your needs. For more information, see CocoaLumberjack

Changing Log Levels

Swift

AWSDDLog.sharedInstance.logLevel = .verbose

The following logging level options are available:

.off
.error
.warning
.info
.debug
.verbose

Objective-C

[AWSDDLog sharedInstance].logLevel = AWSDDLogLevelVerbose;

The following logging level options are available:

AWSDDLogLevelOff
AWSDDLogLevelError
AWSDDLogLevelWarning
AWSDDLogLevelInfo
AWSDDLogLevelDebug
AWSDDLogLevelVerbose

We recommend setting the log level to Off before publishing to the Apple App Store.

Targeting Log Output

CocoaLumberjack can direct logs to file or used as a framework that integrates with the Xcode console.

To initialize logging to files, use the following code:

Swift

let fileLogger: AWSDDFileLogger = AWSDDFileLogger() // File Logger
fileLogger.rollingFrequency = TimeInterval(60*60*24)  // 24 hours
fileLogger.logFileManager.maximumNumberOfLogFiles = 7
AWSDDLog.add(fileLogger)

Objective-C

AWSDDFileLogger *fileLogger = [[AWSDDFileLogger alloc] init]; // File Logger
fileLogger.rollingFrequency = 60 * 60 * 24; // 24 hour rolling
fileLogger.logFileManager.maximumNumberOfLogFiles = 7;
[AWSDDLog addLogger:fileLogger];

To initialize logging to your Xcode console, use the following code:

Swift

AWSDDLog.add(AWSDDOSLogger.sharedInstance) // Apple's unified logging

Objective-C

[AWSDDLog addLogger:[AWSDDOSLogger sharedInstance]]; // Apple's unified logging

Open Source Contributions

We welcome any and all contributions from the community! Make sure you read through our contribution guide here before submitting any PR's. Thanks! ❤️

Talk to Us

Visit our GitHub Issues to leave feedback and to connect with other users of the SDK.

Author

Amazon Web Services

License

See the LICENSE file for more info.

benbaker76/Hackintool

The Swiss army knife of vanilla Hackintoshing

Hackintool

The Swiss army knife of vanilla Hackintoshing

⚠️ Warning

Hackintool is not an automated patching tool that does all the work for you. Knowledge is required on how to patch before using it. Please read the Intel Framebuffer patching using WhateverGreen guide before you download this tool! I also recommend reading:

Mojave, Lilu, and WhateverGreen

Clover's KextsToPatch is not usable for framebuffer patching in Mojave for Skylake and newer generations.

Framebuffer Dumps

There are several ways to dump your framebuffer data (the second two require WhateverGreen and Lilu debug versions) to read in Hackintool:

Use the Framebuffer -> macOS 10.13.6 / Framebuffer -> macOS 10.14 menu to create patches without a framebuffer dump.
Use the -igfxdump boot flag to dump the IGPU framebuffer kext to /AppleIntelFramebuffer_X_Y (root of your boot drive) and then use File -> Open menu.
Use the -igfxfbdump boot flag to dump the native and patched framebuffer table to ioreg and then use File -> Import -> IOReg Dump menu.

Features

Supports generations from Sandy Bridge to Ice Lake (Sandy Bridge, Ivy Bridge, Haswell, Broadwell, Skylake, Kaby Lake, Coffee Lake, Cannon Lake, and Ice Lake)
Create All, Connectors, or VRAM patches
Detect Changes for auto patch creation
Create Clover patches in hex, base64, or Devices/Properties formats
Displays native GPU and Model identifiers
Display and edit Memory Info such as Stolen, Framebuffer, VRAM, Cursor, etc.
Tooltips for additional info when hovering over some items
Reads "live" data directly from Framebuffer kexts (if available; see Mojave note below)
File -> Open framebuffer file generated by WhateverGreen's -igfxdump boot flag
File -> Export -> Clover config.plist / File -> Export -> Framebuffer.txt file
Patch audio layout ID
Add USB port limit patch
Plug and unplug USB2/USB3 devices and set port connector types, then generate a USBPorts.kext
Advanced patching options (DVMT pre-alloc 32 MB, VRAM 2048 MB, Disable eGPU, Enable HDMI2.0 (4K), DP -> HDMI, GfxYTile Fix, Reboot Fix, USB port Limit, Spoof Audio Device ID, FB Port Limit, Spoof Gfx Device ID)

Screenshot

Click to expand

Release Notes

Click to expand

Updates are on Github
2.8.6 - Fix crash in getEDIDData, fix Import KextsToPatch
2.8.5 - Add "Show Installed Only" option for installed kexts
2.8.4 - Improved framebuffer enumeration, updated codecs and pci.ids
2.8.3 - Improved version checking routine, updated Turkish translation
2.8.2 - Updated Clover download location / OpenCore download support, Chinese translation update
2.8.1 - Data file updates
2.8.0 - Fixed OpenCore KextsToPatch format. Removed DSDT Rename auto selection
2.7.9 - Source is now on Github here
2.7.8 - Fix pcidevices.dsl compile error
2.7.7 - pcidevices.dsl export will now compile. Fix for Device Path
2.7.6 - Custom Device Path generation code (big thanks to @jaymonkey for helping test). Updated Chinese translation
2.7.5 - PCI DevicePath fix
2.7.4 - Added EveryMac.com Serial Check
2.7.3 - Added Serial Number Generator (thanks to vit9696 / MacInfoPkg team)
2.7.2 - Added EDID injection to IGPU. Added DPCD Max Link Rate patching. Added tooltips for Advanced / LSPCON patch options. Updated pci.ids / AppleALC audio data
2.7.1 - Bug fixes. Updated pci.ids / AppleALC audio data
2.7.0 - Launch process output fix (big thanks to @jaymonkey for the help testing this). Prepends "Intel" for IGPU name for Intel Power Gadget (thanks again to @jaymonkey for discovering this). System Info now includes all graphics cards. iMessage Keys are now clearly labeled. Added new OpenCore logo. Updated pci.ids / AppleALC audio data
2.6.9 - Disable Gatekeeper tool fix
2.6.8 - Catalina fixes
2.6.7 - Added "HDMI Infinite Loop Fix". Added LSPCON patching. Fixes
2.6.6 - Added "Disable Gatekeeper and mount the disk in read/write mode" tool. Change GFX0 to IGPU selection no longer shows for dGPU
2.6.5 - Improved BT hardware detection (when installed) and will show if FW Loaded (if using BrcmPatchRAM)
2.6.4 - Fixes
2.6.3 - Added Atheros BT device detection
2.6.2 - Added Bluetooth to Info->Misc
2.6.1 - Fixed USB device speeds
2.6.0 - USB fixes for macOS Catalina. USB now shows device speeds. Much improved Log viewer. Installing kexts on macOS Catalina will prompt to disable Gatekeeper and mount the disk in read/write mode. Fixed Atheros install for macOS Catalina. Added NativeDisplayBrightness to kext install list. Updated translations for Korean / Chinese
2.5.9 - ACPI names must be 4 characters (thanks P1LGRIM)
2.5.8 - Now using pci.ids for Audio Controllers
2.5.7 - Removed kextcache -u / call for rebuild cache. Added more command output for tools
2.5.6 - Added column sorting to PCI table
2.5.5 - Added ASRock DeskMini 310 system config
2.5.4 - Will now output mounting errors
2.5.3 - Fixed EveryMac.com Visit link
2.5.2 - Added Host, OS, Kernel and RAM System Info
2.5.1 - Add support for 0x3EA50005 0x3EA60005 0x3E980003 frame id for CFL refresh
2.5.0 - Fixed stdout/stderr output capture for admin privilege shell commands (thanks jaymonkey)
2.4.9 - Fixes
2.4.8 - Fixes
2.4.7 - Fixes
2.4.6 - "Rebuild KextCache and Repair Permissions" moved to tools section now has progress bar
2.4.5 - Output added for "Rebuild KextCache and Repair Permissions"
2.4.4 - Chinese language updates. Compiler improvements
2.4.3 - Chinese language updates. USB configurator fixes
2.4.2 - Changed Framebuffer Info to Selected / Current Framebuffer Info for easier comparison
2.4.1 - Chinese language update
2.4.0 - Now includes iMessageDebug data (ElNono / mdmwii / flux84 / sugarface / pokenguyen). Export system info data. View model info (everymac.com). Check serial feature. Preliminary OpenCore support (thanks vit9696)
2.3.9 - ComboBox fix (thanks telepati)
2.3.8 - Bug fixes (thanks ReddestDream)
2.3.7 - Improved Clover EFI Mounting. Clover PCI export now uses SubClass for device_type
2.3.6 - Bug fixes. "Use Intel HDMI" option added (hda-gfx=onboard-x). Added "Non Scaled" resolution type
2.3.5 - Fixed bug in Device Path generator (gfxutil). Added "Generate Windows UTC Registry Files" tool
2.3.4 - Updated audio codecs, Export PCI list in Clover and dsl format, Now dumps all ACPI tables and decompiles to dsl
2.3.3 - Extract DSDT (phpdev32), Auto update PCIIDs (MuntashirAkon), Export PCI list in JSON format
2.3.2 - Monitor PCI hotplug
2.3.1 - UI Updates
2.3.1 - Right-click on a PCI device and select "Copy IOReg Path". Launch IORegistryExplorer and select Go->Go to Path... menu, paste in the path and click the "Go to Path" button.
2.2.8 - Added warning for HWP state logging (previous state can only be restored after a reboot)
2.2.7 - Added VDA Decoder status. Added DevicePath for PCI devices. Export PCI Devices list to desktop
2.2.6 - Improved Boot EFI detection. Set Boot EFI manually. AppleIntelInfo shows 30 second timer to log CStates. Restores HWP state after logging. Added Intel Regs warning. Calculator now shows reverse bytes
2.2.4 - Added AppleIntelInfo options (Enable HWP, Log: CStates, IGPU, IPG Style, Intel Regs, MSRs). Added AppleIntelInfo 20 second delay for CState capture.
2.2.2 - Added Info tab (Network Interfaces, Graphic Devices, Audio Devices and Storage Devices). Will highlight power settings green or red to indicate issues
2.2.1 - Fixes
2.2.0 - New PCI Devices, Network, Power and Tools tab
2.1.9 - Added Github kext downloading. The download version may be older than the source version. Also due to Github API rate limits it will store the latest download urls. Added Install kext(s) function. Added Rebuild KextCache and Repair Permissions function
2.1.8 - Uses kextstat to get the versions
2.1.7 - Now detects more kexts
2.1.6 - Can now download the current version numbers of Lilu + Plugins
2.0.8 - Patch->System Configs menu with various configurations you can try if your Coffee Lake system is being troublesome (CaseySJ)
2.0.4 - Apply Clover patches (KernelToPatch, KextToPatch, DSDT Renames). View, create and edit NVRAM variables (be careful!). View installed Lilu + Plugins, download and automatically compile the latest versions
1.9.6 - Disk display enhancements (icons / mount / unmount buttons)
1.9.2 - Fixes
1.9.1 - Added SSDT-UIAC.aml / SSDT-USBX.aml export support
1.9.0 - Fixed launch bug (thanks @Pavo)
1.8.7 - Added USB Power DSDT Renames
1.8.6 - Added DSDT Renames
1.8.5 - Fixes
1.8.4 - Auto update capability using Sparkle framework
1.8.3 - Improved Audio Device detection / selection, window can now be resized
1.8.2 - Added translations; French (Matgen84), German (al6042), Korean (zisqo), Russian / Ukrainian (ctich)
1.8.1 - Clover downloader (Kozlek / JrCs / slice), NVRAM boot-args edit, improved authorization, UI update
1.8.0 - Improved USB power export (corpnewt), other fixes, new icon
1.7.9 - Added USB power export, EFI partition mounting, calculator and log viewer
1.7.8 - Added resolution injection from one-key-hidpi script (xzhih)
1.7.7 - Added EDID patching support for AMD & nVidia
1.7.6 - EDID overrides can now export custom icons
1.7.5 - Improved USB guide, added print button
1.7.4 - Fixed defaults
1.7.3 - Updates
1.7.2 - Renamed app to Hackintool, added EDID injection support (Andy Vandijck)
1.7.1 - Dark mode fixes
1.7.0 - USB & Audio info added, shows possible spoof / kext requirements
1.6.9 - Updates
1.6.8 - Added framebuffer-camellia and framebuffer-flags patching support
1.6.7 - Added Macmini8,1 and MacBookAir8,1 definitions
1.6.6 - Data file updates
1.6.5 - Fixed USBInjectAll detection
1.6.4 - Audio layout id detection improvement
1.6.3 - Now shows Audio Controller
1.6.2 - USB fixes
1.6.1 - Improved Spoof Audio Device Id option
1.6.0 - Fixes
1.5.9 - Now shows USB Controllers
1.5.8 - Will store and restore USB ports between app sessions for use with new USBInjectAll.kext (0.7.0) to include boot flags for excluding groups of ports
1.5.7 - Now detects EHC and hub ports (thanks to RehabMan & SavageAUS). Multi-select USB Ports. Now detects if USBInjectAll is installed
1.5.4 - Fixed audio codec detection when user has multiple audio devices. Added "Reboot Fix" advanced patch (sets connector pipe values to 18)
1.5.3 - Improved Export->Clover config.plist and now makes a backup (config-backup.plist)
1.5.2 - Added Patch->AzulPatcher4600
1.5.1 - USBPorts port-count fix
1.5.0 - Fixes
1.4.9 - Added tab to show if Lilu, WhateverGreen and AppleALC are installed and version info
1.4.8 - Fixed framebuffer-cursormem output for iASL DSL Source patching
1.4.7 - Added support for new WEG -igfxfbdump boot flag using File->Import->IOReg Dump menu
1.4.6 - Fixes. Added Framebuffer->macOS 10.14 menu item. Added QE/CI and Metal support detection
1.4.5 - Added support for framebuffer-cursormem (Haswell)
1.4.4 - Added ability to inject valid device-id's
1.4.3 - Fixes
1.4.2 - Added Patch->Import KextsToPatch / Apply Current Patches menu. Renamed USBPower.kext -> USBPorts.kext
1.4.1 - Added TypeC USB ports
1.4.0 - Improved Intel Generation detection
1.3.9 - Now using AppleIntelFramebuffer@X index for connector association
1.3.8 - Fixed bug AppleIntelFramebuffer port-number should be connecter index + 4 or 0 for internal (RehabMan)
1.3.7 - Shows Display Info for connected displays on connector ports (with display hot plug support), fixed iASL DSL Source hex output, connector drag-drop to change order
1.3.6 - Fixes
1.3.5 - Will try HDAS if HDEF is not found
1.3.4 - Added AllData connector patch method (RehabMan). Will try GFX0 if IGPU is not found
1.3.3 - Fixes. Added more audio layout-id's (vandroiy2013)
1.3.2 - Fixes
1.3.1 - Fixes. Added new menu Framebuffer->Current Version / macOS 10.13.6
1.3.0 - Added audio patching, Clover config.plist exporting, USB patching, advanced auto patching
1.2.8 - Added iASL DSL Source patch output, display detected Intel gen and platform-id
1.2.7 - File->Export framebuffer text file
1.2.6 - Fix preallocated memory calculation formula (vit9696)
1.2.5 - Still outputs a config.plist/Devices/Properties patch when "Auto Detect Changes" is selected
1.2.4 - Fixes
1.2.3 - config.plist/Devices/Properties patch now outputs data format
1.2.2 - Fixes
1.2.1 - Updates and fixes
1.2.0 - Added support for Cannon Lake and Ice Lake
1.1.0 - Added MacBookPro15,1 and MacBookPro15,2 models
1.0.9 - Support for Mojave, Coffee Lake, WhateverGreen's -igfxdump boot flag and Clover's config.plist/Devices/Properties patch output
1.0.8 - Updates
1.0.7 - Fixed support for dark mode
1.0.6 - Better backwards compatibility
1.0.5 - Detects Chipset / Address on Startup, Edit Memory Values Easier
1.0.4 - Added GPU / Model Info
1.0.3 - Added Tooltips
1.0.2 - Added Memory tab
1.0.1 - Minor Fixes
1.0.0 - Initial Release

Credits & Contributions

vit9696 for WhateverGreen (full credits), Lilu (full credits), AppleALC (full credits), USBPorts.kext and additional help
vit9696 for IntelFramebuffer.bt with additional work by bcc9, Piker-Alpha and joevt
daliansky for Intel Core Platform ID and SMBIOS Quick Reference
Clover Development Team for various technical info
vandroiy2013 for audio id data from AppleALC
RehabMan for all data patching method, ioreg framebuffer dump and other contributions
EDID injection (Andy Vandijck / Marchrius)
USB power injection (corpnewt)
HDA controllers / codec lists by the VoodooHDA project
System Configs compilation (CaseySJ)
Clover downloader (Kozlek / JrCs / slice)
Kext compiler & installer (Sascha Lamprecht / Gengik84 / LAbyOne)
Atheros & SATA kexts (Sascha Lamprecht)
DPCIManager (phpdev32 / MuntashirAkon)
AppleIntelInfo (Pike R. Alpha)
gfxutil (mcmatrix)
VDADecoderChecker (Andy Breuhan)
iMessageDebug (ElNono / mdmwii / flux84 / sugarface / pokenguyen)
macserial (vit9696 / MacInfoPkg team)
Model data (everymac.com)
Translations: French (Matgen84), German (al6042), Korean (zisqo), Russian / Ukrainian (ctich), Chinese (daliansky, Bat.bat, penghubingzhou)
Sparkle framework by Andy Matuschak
Icon & UI updates by ultratiem

GitHub Objective-C Daily Trending Repositories

opa334/TrollStore

TrollStore

Installing TrollStore

Updating TrollStore

Uninstalling an app

Persistence Helper

URL Scheme

Features

Banned entitlements

Unsandboxing

Root Helpers

Things that are not possible using TrollStore

Compilation

Credits and Further Reading

PojavLauncherTeam/PojavLauncher_iOS

PojavLauncher for iOS

Important note

Introduction

Getting started with PojavLauncher

Requirements

Setting up to sideload

Installing PojavLauncher

Release build (TrollStore)

Release build (AltStore/SideStore trusted source)

Nightly builds

Enabling JIT

Contributors

Third party components and their licenses

Special thanks to MacStadium!

Mininglamp-OSS/octo-ios

OCTO iOS

🌟 Why OCTO iOS

🚀 Quickstart

📦 Modules / Architecture

🔗 OCTO Ecosystem

🧭 Philosophy

🤝 Contributing

📄 License

🙏 Acknowledgments

geode-sdk/ios-launcher

Geode iOS Launcher

Requirements

Quick Start

Support

Building / Development

Libraries

License

roothide/Bootstrap

roothide Bootstrap

WARNING: By using this software, you take full responsibility for what you do with it. Any unofficial modifications to your device may cause irreparable damage. Refer to the FAQ linked in the Usage section for safe usage of this software.

Building

Usage

Develop tweaks

Discord server

The "Our Table" Icon

Credits

roothide/Developer

update jailbreak apps/tweaks for roothide

support

more info

mixpanel/mixpanel-iphone

Table of Contents

Overview

Quick Start Guide

1. Install Mixpanel

Installation Option 1: CocoaPods

Installation Option 2: Carthage

Installation Option 3: Swift Package Manager

2. Initialize Mixpanel

3. Send Data

4. Check for Success

Complete Code Example

FAQ

I want to know more!

34306/FilzaJailedDS

FilzaJailedDS

Credit

rollbar/rollbar-apple

Rollbar Apple MonoRepo

WARNING: By using this software, you take full responsibility for what you do with it. Any unofficial modifications to your device may cause irreparable damage. Refer to the FAQ linked in the `Usage` section for safe usage of this software.