Closed StefanWallin closed 3 months ago
Hey @StefanWallin
This looks like https://github.com/Adyen/adyen-3ds2-ios/issues/34
I'll check with 3DS2 team..
We just released 2.0.0-rc.1 and 1.2.1 that uses latest Adyen3DS.
@StefanWallin could you verify the fix ?
Well, we've only seen this a couple of times. Since I filed this issue, only once and that was on 31st of march. We are also currently stuck with apple, but I'll try to squeeze this into an upcoming release and then we'll just have wait and see...
I'll close this ticket for now. Feel free to leave feedback and continue the discussion here.
Describe the bug This is a bug we've encountered in our Firebase Crashlytics Reporting.
This causes a fatal exception for us. We have two occurrences so far. Not a major headache yet.
iOS only, we deploy both to Android and iOS
From our telemetry it looks like both of these devices had network issues at the time because they had not handshaken with our backend on app start which they usually do.
The URL referenced above is also 404.
To Reproduce Steps to reproduce the behavior: I don't know honestly.
Expected behavior The app to not crash with the above exception.
Screenshots Device 1
1 minute 38 seconds
"@adyen/react-native": "^1.1.0",
Device 2
2 minutes 20 seconds
"@adyen/react-native": "^1.1.0",
Additional context Not sure what context is relevant for you, ask questions and I will try to answer.