Skip to content

error 'Iterable_React_Native_SDK-Swift.h' file not found #774

Closed

Description

@quinton22

When attempting to build with version 2.1.0, I run into this error:

error 'Iterable_React_Native_SDK-Swift.h' file not found

It looks like this is imported in RNIterableAPI.mm, but I cannot find Iterable_React_Native_SDK.swift in the repo.

Activity

  1. dazlious commented on Nov 6, 2025

    @dazlious

    Same here for us. We are using old architecture

  2. lposen commented on Nov 11, 2025

    @lposen
    Contributor

    You’ll need to enable dynamic frameworks in your project to resolve this issue.

    You can find the setup instructions here:
    👉 Installing Iterable’s React Native SDK – Step 3.3: Import the SDK

  3. dazlious commented on Nov 17, 2025

    @dazlious

    See #778 (comment)
    XCode 26.1

  4. lposen commented on Nov 19, 2025

    @lposen
    Contributor

    This is a separate issue issue which only occurs in Github Actions, which can run slightly differently than on your local machine.

    See #778 (comment) XCode 26.1

  5. alexstaravoitau commented on Nov 21, 2025

    @alexstaravoitau

    @lposen I get the same error in Xcode 26.1 when running locally, with dynamic linking enabled for iOS Iterable modules (as per SDK setup instructions).

    Switching to angled header import in RNIterableAPI.mm fixes the issue, and I seemingly don't need to use dynamic linking anymore either. I basically changed this:

    #import "Iterable_React_Native_SDK-Swift.h"

    ..to this:

    #import <Iterable_React_Native_SDK/Iterable_React_Native_SDK-Swift.h>
  6. dazlious commented on Nov 21, 2025

    @dazlious

    @lposen I get the same error in Xcode 26.1 when running locally, with dynamic linking enabled for iOS Iterable modules (as per SDK setup instructions).

    Switching to angled header import in RNIterableAPI.mm fixes the issue, and I seemingly don't need to use dynamic linking anymore either. I basically changed this:

    #import "Iterable_React_Native_SDK-Swift.h"
    ..to this:

    #import <Iterable_React_Native_SDK/Iterable_React_Native_SDK-Swift.h>

    This seems to help me installing 2.1.0 now as the dynamic linkage was not working for us.
    Unfortunately, when sending pushes to any version above 2.0.2 I get PushUninstall and never receive a push

  7. reopened this on Dec 1, 2025
  8. lposen commented on Dec 1, 2025

    @lposen
    Contributor

    Sorry guys -- didn't see your comments was closed. Reopened it. Will respond in seperate comments.

  9. lposen commented on Dec 1, 2025

    @lposen
    Contributor

    @lposen I get the same error in Xcode 26.1 when running locally, with dynamic linking enabled for iOS Iterable modules (as per SDK setup instructions).

    Switching to angled header import in RNIterableAPI.mm fixes the issue, and I seemingly don't need to use dynamic linking anymore either. I basically changed this:

    #import "Iterable_React_Native_SDK-Swift.h"
    ..to this:

    #import <Iterable_React_Native_SDK/Iterable_React_Native_SDK-Swift.h>

    @alexstaravoitau -- Interesting! Out of interest, did you patch our sdk, or put this elsewhere in your code?

  10. lposen commented on Dec 1, 2025

    @lposen
    Contributor

    @lposen I get the same error in Xcode 26.1 when running locally, with dynamic linking enabled for iOS Iterable modules (as per SDK setup instructions).
    Switching to angled header import in RNIterableAPI.mm fixes the issue, and I seemingly don't need to use dynamic linking anymore either. I basically changed this:
    #import "Iterable_React_Native_SDK-Swift.h"
    ..to this:
    #import <Iterable_React_Native_SDK/Iterable_React_Native_SDK-Swift.h>

    This seems to help me installing 2.1.0 now as the dynamic linkage was not working for us. Unfortunately, when sending pushes to any version above 2.0.2 I get PushUninstall and never receive a push

    @dazlious -- just to make sure that I understand before I start debugging:

    1. Changing to #import <Iterable_React_Native_SDK/Iterable_React_Native_SDK-Swift.h> fixed build issues
    2. If you downgrade to 2.0.2 and lower and rebuild, push works
    3. If you use 2.0.3 and higher, push does not work (and you are seeing PushUninstall).

    Is this correct?

  11. alexstaravoitau commented on Dec 2, 2025

    @alexstaravoitau

    Interesting! Out of interest, did you patch our sdk, or put this elsewhere in your code?

    @lposen I've patched the SDK—sorry didn't get a chance to open a PR earlier, just submitted one now: #789

  12. dazlious commented on Dec 2, 2025

    @dazlious

    Yes, I have also patched the SDK in version 2.1.0 to use @alexstaravoitau solution. Although I installed the linkage pod, I get a lot of errors - so the only viable way of getting 2.1.0 to run was patching

  13. dazlious commented on Dec 2, 2025

    @dazlious

    @lposen I get the same error in Xcode 26.1 when running locally, with dynamic linking enabled for iOS Iterable modules (as per SDK setup instructions).
    Switching to angled header import in RNIterableAPI.mm fixes the issue, and I seemingly don't need to use dynamic linking anymore either. I basically changed this:
    #import "Iterable_React_Native_SDK-Swift.h"
    ..to this:
    #import <Iterable_React_Native_SDK/Iterable_React_Native_SDK-Swift.h>

    This seems to help me installing 2.1.0 now as the dynamic linkage was not working for us. Unfortunately, when sending pushes to any version above 2.0.2 I get PushUninstall and never receive a push

    @dazlious -- just to make sure that I understand before I start debugging:

    1. Changing to #import <Iterable_React_Native_SDK/Iterable_React_Native_SDK-Swift.h> fixed build issues
    2. If you downgrade to 2.0.2 and lower and rebuild, push works
    3. If you use 2.0.3 and higher, push does not work (and you are seeing PushUninstall).

    Is this correct?

    Yes:

    1. patching helped me install 2.1.0
    2. version 2.0.2 seems fine (although I can only use it with XCode 16.4)
    3. in versions 2.0.3, 2.0.4, 2.1.0 I get PushUninstall every time I send a push to a device - the push never arrives
  14. facundo-serfe commented on Dec 31, 2025

    @facundo-serfe

    Hey guys, I have the same issue, I'm using expo with the v2.0.0 SDK version, and I have a self-hosted mac runner to build the apps running a github action, but I have that issue as well:

    Image

    I installed Xcode 26 and Xcode 16.4, cause one time ago we're solved some issues using the last one, but in my case I don't find the .mm file, I only see these files:

    Image
  15. lposen commented on Jan 9, 2026

    @lposen
    Contributor

    Hey guys, I have the same issue, I'm using expo with the v2.0.0 SDK version, and I have a self-hosted mac runner to build the apps running a github action, but I have that issue as well:

    Image I installed Xcode 26 and Xcode 16.4, cause one time ago we're solved some issues using the last one, but in my case I don't find the .mm file, I only see these files: Image

    Hi @facundo-serfe. The .mm file was added in 2.1.0, so I'm unsure why your runner is trying to pull it. Please also note: 2.0.0 is not officially compatible with either expo or New Architecture -- you would have to upgrade to 2.1.0 for either of these.

  16. lposen commented on Jan 9, 2026

    @lposen
    Contributor

    3. in versions 2.0.3, 2.0.4, 2.1.0 I get PushUninstall every time I send a push to a device - the push never arrives

    Hi @dazlious. Upgrading to 2.2.0 should fix this problem. This version contains the latest versions of our Android and iOS SDKs and support for later Android/iOS versions. Please let me know if you're still experiencing issues after the upgrade.

  17. dazlious commented on Jan 9, 2026

    @dazlious
    1. in versions 2.0.3, 2.0.4, 2.1.0 I get PushUninstall every time I send a push to a device - the push never arrives

    Hi @dazlious. Upgrading to 2.2.0 should fix this problem. This version contains the latest versions of our Android and iOS SDKs and support for later Android/iOS versions. Please let me know if you're still experiencing issues after the upgrade.

    Yep, 2.2.0 seem to have fixed that for local installs.

  18. rejitha3391 commented on Jan 27, 2026

    @rejitha3391

    I’ve upgraded to the latest React Native Iterable SDK (react-native-iterable-sdk) v2.2.0, but I’m still hitting the same build error when building via Xcode 26.2.

    Environment:

    • React Native: 0.83.1
    • New Architecture: enabled
    • iOS build: Xcode 26.2
    • react-native-iterable-sdk: 2.2.0
  19. added a commit that references this issue on Apr 7, 2026
  20. added a commit that references this issue on Apr 7, 2026
    3aecae2
  21. franco-zalamena-iterable commented on Jun 29, 2026

    @franco-zalamena-iterable

    React Native 0.8x was not supported at the time, from version 3.0.1 onwards these versions are supported.

    Could you test it with the latest Iterable SDK version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions