3.2.2
0.59.9
iOS
Build project successfully
Failing with build errors in RNIap
Emulator
Add RNIap v3 to a project, perform the linking and observe the errors shown in below screenshot

@varungupta85 Please try 3.2.4.
Ok, let's invest this problem further!

Guys I am also facing this build problem with
Xcode Version 10.1 (10B61)
"react-native-iap": "^3.2.4",
@hyochan Like other people have reported, I also updated to 3.2.4 and still observing the same problem.
I have same problem
I have to downgrade to "react-native-iap": "2.4.0" to fix build error
I also encountered this problem, I saw that others solved it by downgrading, but the author suggested using version 3.2.0. I should downgrade or wait to fix this bug?
xcode:10.1
"react-native": "^0.59.10",
"react-native-iap": "^3.3.2",

I can't reproduce this in my env. So please generate minimal reproduction maybe sharing some codes.
For me, the problem is Xcode: updating from 10.1 to 10.2.1 'm able to build correctly, but honestly I don't know if it works with iOS versions <= 12.1
Any news about that issue ?
I am using Xcode 10.1 and same error occur. Then I update Xcode to 10.3. Xcode built successfully.
Running into the same issue, on Xcode 10.1, going to get Xcode 10.3 dmg and run side by side to see if it solves it.
Update: After a full update to Mojave and Xcode 10.3 the build seems to be working.
@hyochan this issue seems to be compatible with Xcode > 10.2
Can we make it compatible with 10.1 please since many users can't upgrade their Xcode due to the limitation of upgrading OS ?
Thank you very much @doomsower, works fine on my side with XCode Version 10.1 (10B61) and rn-iap 3.4.0.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "For Discussion" or "Good first issue" and I will leave it open. Thank you for your contributions.
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.
Most helpful comment
@hyochan Like other people have reported, I also updated to
3.2.4and still observing the same problem.