Exclude Apple pay or PassKit framework from the generated binary

[nfmshow]

Is it possible to exclude apple pay in an expo workflow. We only intend to use this library in our android build, we already use apple in app purchase services for our ios builds. The problem is that apple pay dependencies still gets bundled and our ios app binary gets rejected when we submit it to app store connect.

This is the rejection message

"The app binary includes the PassKit framework for implementing Apple Pay, but we were unable to verify any integration of Apple Pay within the app."

Is there a way to specify that apple pay should be excluded.

[imraann0]

Is it possible to exclude apple pay in an expo workflow. We only intend to use this library in our android build, we already use apple in app purchase services for our ios builds. The problem is that apple pay dependencies still gets bundled and our ios app binary gets rejected when we submit it to app store connect.

This is the rejection message

"The app binary includes the PassKit framework for implementing Apple Pay, but we were unable to verify any integration of Apple Pay within the app."

Is there a way to specify that apple pay should be excluded.

did you find solution for this

[UsamaAshraf82]

+1