Skip to content

Problems conflicting with BoringSSL #219

@dsdsk

Description

@dsdsk

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.

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