Rust Libs Framework for IOS

[randogoth]

Validation failed Invalid bundle structure. The "Runner.app/libonod3000.dylib" binary file is not permitted. Your app cannot contain standalone executables or libraries, other than a valid CFBundleExecutable of supported bundles. For details, visit: https://developer.apple.com/documentation/ bundleresources/placing_content_in_a_bundle (ID: 7d7a0a95-825d-4b21-b22f-8414fc5781c0)
Validation failed Invalid bundle structure. The "Runner.app/libocell.dylib" binary file is not permitted. Your app cannot contain standalone executables or libraries, other than a valid CFBundleExecutable of supported bundles. For details, visit: https://developer.apple.com/documentation/ bundleresources/placing_content_in_a_bundle (ID: f814cacf-7144-4ce1-b66a-45eaea25783a)
Upload Symbols Failed The archive did not include a dSYM for the libocelli.dylib with the UUIDs [F126F15E-A222-3D5C-

[randogoth]

1. Create a New Cocoa Touch Framework in Xcode

• New Framework Target:
  Open your Xcode project and add a new target via File > New > Target…. Select Cocoa Touch Framework and give it a name (for example, MyRustFramework).

• Framework Structure:
  Xcode will create a bundle with the following structure:

  MyRustFramework.framework/
      Headers/         // For public header files (if needed)
      Modules/         // For module maps (if using Swift/Objective-C bridging)
      MyRustFramework // The executable binary (your Rust dylib, once renamed)
      Info.plist       // Bundle metadata
  

---

2. Integrate Your Rust dylib

• Add the dylib:
  Drag your compiled Rust dylib file into the framework’s folder in Xcode.

  • Rename if necessary: Rename it to match your framework’s name (e.g., MyRustFramework) so that it becomes the framework’s main executable.

• Update Info.plist:
  Edit the framework’s Info.plist to include the key CFBundleExecutable with the value set to your binary’s name (e.g., MyRustFramework).

---

3. Expose Your FFI Bindings (Optional)

• Header Files:
  If you need to call your Rust functions from Swift or Objective-C, generate or write a header file that declares your FFI functions. Tools like [cbindgen](https://github.com/eqrion/cbindgen) can help generate these headers automatically.

• Place Headers:
  Add these headers to the framework’s Headers directory so they are publicly available for bridging.

---

4. Embed and Sign the Framework in Your Flutter App

• Linking:
  In your Flutter app’s iOS project (typically under the Runner target), go to the General tab and add your new framework under Frameworks, Libraries, and Embedded Content.

• Embed & Sign:
  Set the framework’s embed option to “Embed & Sign” so that it’s properly packaged and signed with your app.

---

5. Test and Archive

• Local Testing:
  Run your app on both a simulator and a physical device to verify that the framework loads correctly and that FFI calls to your Rust code work as expected.

• Archive and Validate:
  Create an archive of your app and validate it using Xcode’s Organizer to ensure that the bundle structure meets Apple’s requirements.

---

By repackaging your Rust-built dylib as a framework, you’re conforming to the iOS guidelines for embedded code, which should help you pass App Store review. For more details on the bundle structure, refer to Apple’s documentation:
https://developer.apple.com/documentation/bundleresources/placing_content_in_a_bundle citeturn0search0