feat(jans-cedarling): create uniffi binding for cedarling with sample ios app using it

jans-cedarling/.gitignore

@@ -97,3 +97,6 @@ docs/_build/
 
 # Pyenv
 .python-version
+
+# allow commit of cedarling_native_apps bindings
+!/bindings/cedarling_native_apps/src/bin

jans-cedarling/bindings/cedarling_native_apps/Cargo.toml

@@ -0,0 +1,23 @@
+[package]
+name = "cedarling_native_apps"
+version = "0.1.0"
+edition = "2021"
+
+[lib]
+crate_type = ["cdylib", "staticlib"]
+name = "mobile"
+
+[dependencies]
+cedarling = { workspace = true, features = ["blocking"]}
+jsonwebtoken = "9.3.0"
+openssl = { version = "0.10.35", features = ["vendored"] }
+once_cell = "1.20.2"
+uniffi = { version = "0.29.0", features = [ "cli" ] }
+uniffi_macros = "0.29.0"  # Procedural macros support
+serde = { workspace = true }
+serde_json = { workspace = true }
+thiserror.workspace = true
+
+[dev-dependencies]
+# is used in testing
+test_utils = { workspace = true }

jans-cedarling/bindings/cedarling_native_apps/README.md

@@ -0,0 +1,55 @@
+# Cedarling Native Apps
+
+This module is designed to build cedarling bindings for iOS and android apps.
+
+## iOS
+
+### Building 
+
+1. Build the library:
+
+```bash
+cargo build
+```
+
+In target/debug, you should find the libmobile.dylib file.
+
+2. Generate the bindings:
+
+```bash
+cargo run --bin uniffi-bindgen generate --library ./target/debug/libmobile.dylib --language swift --out-dir ./bindings/cedarling_native_apps/output
+```
+
+3. Building the iOS binaries and adding these targets to Rust.
+
+```bash
+rustup target add aarch64-apple-ios-sim aarch64-apple-ios
+```
+
+4. Build the library for Swift.
+
+```bash
+cargo build --release --target=aarch64-apple-ios-sim
+cargo build --release --target=aarch64-apple-ios
+```
+
+You should have two binaries target/aarch64-apple-ios-sim/release/libmobile.a and target/aarch64-apple-ios/release/libmobile.a.
+
+5. The XCFramework will allow us to import the library with zero effort in Xcode. First, we need to rename the file ./bindings/cedarling_native_apps/output/mobileFFI.modulemap to ./bindings/cedarling_native_apps/output/module.modulemap.
+
+Then, we can create the XCFramework:
+
+```bash
+xcodebuild -create-xcframework \
+        -library ./target/aarch64-apple-ios-sim/release/libmobile.a -headers ./bindings/cedarling_native_apps/output \
+        -library ./target/aarch64-apple-ios/release/libmobile.a -headers ./bindings/cedarling_native_apps/output \
+        -output "ios/Mobile.xcframework"
+```
+
+6. Open ./jans-cedarling/bindings/cedarling_native_apps/iOSApp in Xcode. Import both the XCFramework Mobile.xcframework and the Swift file bindings bindings/Mobile.swift files into your project (drag and drop should work).
+
+7. Run iOS project on simulator. 
+
+## Android
+
+- WIP...

jans-cedarling/bindings/cedarling_native_apps/iOSApp/.gitignore

@@ -0,0 +1,62 @@
+# Xcode
+#
+# gitignore contributors: remember to update Global/Xcode.gitignore, Objective-C.gitignore & Swift.gitignore
+
+## User settings
+xcuserdata/
+
+## Obj-C/Swift specific
+*.hmap
+
+## App packaging
+*.ipa
+*.dSYM.zip
+*.dSYM
+
+## Playgrounds
+timeline.xctimeline
+playground.xcworkspace
+
+# Swift Package Manager
+#
+# Add this line if you want to avoid checking in source code from Swift Package Manager dependencies.
+# Packages/
+# Package.pins
+# Package.resolved
+# *.xcodeproj
+#
+# Xcode automatically generates this directory with a .xcworkspacedata file and xcuserdata
+# hence it is not needed unless you have added a package configuration file to your project
+# .swiftpm
+
+.build/
+
+# CocoaPods
+#
+# We recommend against adding the Pods directory to your .gitignore. However
+# you should judge for yourself, the pros and cons are mentioned at:
+# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
+#
+# Pods/
+#
+# Add this line if you want to avoid checking in source code from the Xcode workspace
+# *.xcworkspace
+
+# Carthage
+#
+# Add this line if you want to avoid checking in source code from Carthage dependencies.
+# Carthage/Checkouts
+
+Carthage/Build/
+
+# fastlane
+#
+# It is recommended to not store the screenshots in the git repo.
+# Instead, use fastlane to re-generate the screenshots whenever they are needed.
+# For more information about the recommended setup visit:
+# https://docs.fastlane.tools/best-practices/source-control/#source-control
+
+fastlane/report.xml
+fastlane/Preview.html
+fastlane/screenshots/**/*.png
+fastlane/test_output