#gilbot-reactnative-testflight

1 messages · Page 1 of 1 (latest)

untold python
#

Hey @faint belfry I don't know much about testflight but I can ask my team, do you have a lot more details?

faint belfry
#

sure thing, so we installed the latest react native stripe package: https://github.com/stripe/stripe-react-native

I followed all of the troubleshoot instructions and everything however, whenever i try to archive and upload an ipa to testflight our build doesnt show up.

untold python
#

that is unfortunately quite vague

#

Like what happened, did you never use Stripe before and suddenly started using Stripe + React Native together?

faint belfry
#

we reached out to apple and they said it might be something due to purpose strings?

from apple
purpose strings are required for access to any protected class

untold python
#

Something else? What happens locally?

faint belfry
#

locally it works fine

#

yea we install the stripe sdk package recently to handle payments

untold python
#

Is it possible other things changed? Like did you try removing our package first to confirm that is the issue?

faint belfry
#

yes i did

untold python
#

so as soon as you remove our package it works and when you add it, it doesn't, even without changing anything else in the code?

faint belfry
#

yes

#

the moment we install the package our builds stop showing up in testflight

untold python
#

okay without changing anything else in the app, not referencing Stripe or anything?

faint belfry
#

yup

#

literally just install the package and running pod install

untold python
faint belfry
#

the one major difference i see is your info.plist has this and mine doesnt

<dict>
<key>CFBundleTypeRole</key>
<string>Editor</string>
<key>CFBundleURLName</key>
<string>com.stripe.react.native</string>
<key>CFBundleURLSchemes</key>
<array>
<string>weixin</string>
</array>
</dict>

#

is that section necessary?

untold python
#

no that shouldn't be necessary

faint belfry
#

damn

#

is there anything else you can think that might be the issue?

untold python
#

Unfortunately no. I'm asking my team but right now their recommendation is to get someone from Apple to provide more details (like escalating to a higher support layer with more details)

faint belfry
#

dang, no worries appreciate the help

untold python
#

yeah 2 other people on my team think that's the best next step, we can't find any other possibilities here unfortunately

faint belfry
#

ok ill reach out and see if they can give any helpful information

untold python
#

Sounds good, sorry we couldn't help more