By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement . We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug description:

Hi everyone. I am using this wonderful library and it gives error I attached below only at ios. I checked documentations but couldn't find the reason why this error occurs. Are there any body experienced this? (Note: android works without no problem)

Screenshots/Videos:

Environment:

OS: ios

OS version: all

react-native version:

react-native-webview version:

I logged onError and saw that an URL while redirection gives 500 error. So react-native-webview gives this -1004 error if some server gives 500.

It is nog bug of this component.

I am having a similar issue. Unfortunately for me, the App Store Review team is having this issue, which I am not able to reproduce at all in simulation or on physical iPhone.
@ozergul , you are saying that the problem comes from the server giving an error code 500, and you didn't have to change anything on the App side to get it to work? But how could it be working for Android and not iOS? (the server is the same, no?)

@nolife08021 did you find a solution to the problem?

@tingofurro our problem was related with third party payment processor. They have had very simple bug on their backends (related with useragent)
That's why app was broken on Ios but not Android

I would prefer adding some logs to backend to understand why the web page broken for App Store Review team

Or see my above message. Log onError with sentry or something else and you will see exactly which page is broken

Thank you for your reply @ozergul . I'll keep debugging, I believe it might be related to DNS as I had the App review team try the same URL in the Safari browser of the simulator and that didn't work as well, so it is unrelated to react-native-webview...

Very mysterious.

hi @tingofurro thanks! do you have by any chance the source of where apple states this about their testing environment not following up Dynamic DNS?

and what's the solution for that case?

hey @ednjv , I never found the information in their documentation, I just tested it empirically.
I changed my domain name to point to a static IP directly, and when I resubmitted with no other change, I got through to the next step (which were other problems), but eventually got the app accepted!

I hope this helps :)