Skip to content
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

Problems conflicting with BoringSSL #219

Open
dsdsk opened this issue Mar 30, 2018 · 1 comment
Open

Problems conflicting with BoringSSL #219

dsdsk opened this issue Mar 30, 2018 · 1 comment

Comments

@dsdsk
Copy link

dsdsk commented Mar 30, 2018

Purchased information is acquired using RMAppReceipt.
It is now supposed to use Firestore which is a function of Firebase, but BoringSSL seems to be necessary here.
When you introduce the library via Cocoapods, BoringSSL also enters at the same time.

It seems that this BoringSSL conflicts with OpenSSL used within RMAppReceipt.
pkcs7.h exists in both OpenSSL and BoringSSL, but pkcs7.h importing with RMAppReceipt seems to have watched BoringSSL.
An error such as not being able to find PKCS7 appears in RMAppReceipt.

Below is a screenshot of RMAppReceipt
2018-03-30 12 16 20

Does anyone know the solution?

--
I am writing using Google Translate.
It may be a strange sentence, but please understand.

@dflateau
Copy link

dflateau commented Jun 1, 2018

I also have this problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants