-
Notifications
You must be signed in to change notification settings - Fork 889
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Libraries collision AWS Iot and React Native #4956
Comments
Thanks for opening this @salitbl ! The team will take a look and post any updates here. |
@ruisebas |
@salitbl sorry for the delay, this change will be released in the next couple of days. If you want to test it, you can target the |
@ruisebas |
No, I don't know why it would crash with React native. Could you share the full symbolicated crashlog? That might give us a hint of what's wrong. |
That is not helpful, and it doesn't reference anything within the In the meantime, I have some follow up questions:
|
@ruisebas |
Hi @salitbl. We held the release due to the crash you reported, and we were waiting to hear back from you. If that's the case, then we will release a new version next week. |
@ruisebas |
@ruisebas |
@ruisebas |
Libraries collision AWS Iot and React Native
I am trying to developing an App with React Native and with private native SDK that use AWSIoT.
When I am trying to run this project, the build is failed duo to 12 duplicate codes in classes For example:
❌ duplicate symbol 'OBJC_IVAR$_SRIOConsumer._scanner' in
┌─ libAWSIoT.a(AWSSRWebSocket.o)
└─ libSocketRocket.a(SRIOConsumer.o)
duplicate symbol 'OBJC_CLASS$_SRIOConsumerPool' in
┌─ libAWSIoT.a(AWSSRWebSocket.o)
└─ libSocketRocket.a(SRIOConsumerPool.o)
❌ duplicate symbol '_SRHTTPResponseErrorKey' in
┌─ libAWSIoT.a(AWSSRWebSocket.o)
└─ libSocketRocket.a(SRWebSocket.o)
AWSSRWebSocket include @interface SRIOConsumer and SocketRocket also has @interface SRIOConsumer Do you have any idea how to resolve this issue?
Which AWS Services are you utilizing? - AWSIoT
Environment
Device Information
The text was updated successfully, but these errors were encountered: