droidcoder_code

[solid sorrel]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1471245677634916453

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[livid fern]

So after clicking the button using testEnv={true} on iOS I see a mock up screen with card details, here I send the app to the background and then open it again, the mock screen is gone and the app becomes unresponsive

[worldly marsh]

Hello
Hmm are you seeing any specific logs before the app gets stuck?

Also is this happening on Android/iOS or both?

[livid fern]

Just iOS at the moment

No logs : onComplete={({ error }) => {
setVisible(false);
if (!error) {
context.setAppleWalletStatus('added')
savePass(cardData.id!).then(() => {
console.log('Pass completed');
}).catch(console.error)
} else {
console.error('Error adding card to wallet:', error);
}
}}

nothing comes on onComplete

works fine if I click buttons on the mock screen

but if disappears on its own then no logs

I also tried with log after setVisible(false); but no luck

using version 0.57.0

[worldly marsh]

You mentioned test and prod environment. Are you switching between both OR is this just happening in test environment?

[livid fern]

no it is happening on both

it happened first on prod and then I confirmed it also happens on test

different phones and different iOS versions

[worldly marsh]

Do you have any useEffects in the same components? If so, can you add some console logs there to see if any of them are resetting the Ephemeral key or something?

[livid fern]

sure I can try that

Ephemeral key is not cleared

[worldly marsh]

Can you force it to clear and refetch?

[livid fern]

ok

I moved it to use useFocusEffect hook so when the screen is at foreground it re fetches but the mock screen is gone

[worldly marsh]

With the new key, you would need to click on the button again

[livid fern]

ah right let me try again

still happening

let me see if I can show you a video

last seconds show me trying to press all over the place but nothing happens

[worldly marsh]

Ah okay I see. I think this might be expected behavior and something that's just baked into iOS. I've seen this happen with a couple of airline apps myself when I tried to add boarding pass and moved the app in the background.

i'm curious about the Stripe error you get when you try to present the sheet again

About 22-23s mark

[livid fern]

ah that is a console log I made it is because I clicked the cancel

Error adding card to wallet: {"code": "Canceled", "declineCode": null, "localizedMessage": "The operation couldn’t be completed. (PKPassKitErrorDomain error 1.)", "message": "The operation couldn’t be completed. (PKPassKitErrorDomain error 1.)", "stripeErrorCode": null, "type": null}

console.error('Error adding card to wallet:', error);

so this is actually nothing to do with the Stripe sdk then but rather PassKit on Apple side

[worldly marsh]

Could be, yeah

I don't know what that error code maps to though, let me see if I can find it

Would you mind sharing your Stripe account ID? I am going to try and see if we have any internal logs about this

[livid fern]

this is probably with the founders of the company, I just been hired to fix issues and ship it to production

[worldly marsh]

Also, was this working before and just stopped working after the SDK upgrade?

[livid fern]

don't know this was catched yesterday by new QA

not sure if this was happening but I guess no one tested this edge case before

but no worries since this seems to be an edge case scenario

[worldly marsh]

Hmm yeah, I can't test it myself at the moment either since it requires approvals etc but if you can create a minimal repro app that we can use to reproduce the issue then I or someone my team would be happy to dig deeper into this.