Ios network error

Describe the bug

While making any post request using Axios package. I am getting a Network error. While the same API seems to be working perfectly fine with Android devices. It is not an issue with the API.

To Reproduce

Axios post request throws a network error message. If I make the call again inside the catch block then it works fine.

axios
      .post(
        base_url + 'generatePaymentIntent',
        {
          // unit_id: 1,
          token: obj,
          order_type: 'ORD',
          order_data: {
            order_type: order_type,
            apt_id: apt_id,
          },
        },
        Loginheader,
      )
        .then(item => {
        this.setState({
          loading: false,
        });
        console.log('--------generate intent----------');
          console.log(item);
        if (item.data.code === 200) {
          const {price} = item.data.data.order_data;
          

          this.displayPaymentModal(
            'Confirm Payment',
            `Final Price: $${price}`,
            this.props.navigation,
            item.data.code,
            'Make Payment',
            item.data.data,
          );
        }
      })
      .catch(e => {
        this.setState({
          loading: false,
        });
        console.log('--------catch generate intent----------');
        // console.log(e.response);
        // const {message, code} = e.response;
        // this.retryPopup(
        //   `Error getting payment Intent`,
        //   message,
        //   '',
        //   code,
        //   'onetime',
        // );
        console.log(e.response);

        console.log(JSON.stringify(e));

        if (e.message === 'Network Error') {
          // this.makeOneTimePayment(order_type, apt_id);
          this.retryPopup(
              `Error getting payment Intent`,
              'RETRY',
              '',
              '400',
              'onetime',
            );
        }
      });

Expected behavior

It shouldn’t through network error. What should be done to fix this behavior specifically for iOS devices/simulators.

Environment

• Axios Version [e.g. 0.19.2]
• Additional Library Versions [e.g. React 16.9.0, React Native 0.62.2]

Additional context/Screenshots

N/A

Hello, I’m making iOS application with react-native. I’m using external server to check some data, so I allowed all of http request in Info.plist file.

But as you can see, in console of screen shot, Promise Rejection —
Network Error occurred.

same code in Android, it works well.

I tested it in iOS simulator and real device, both failed.

Can you help me what is problem.

Thanks.

the http code part is like this, this works well in Android emulator.

axios.get('http://suggest.hub.daum.net/suggest?q='+query+'&mod=json&code=utf_in_out&callback=suggestCallback&id=54')
            .then((response) => {
                ...
            });

plus…

this is full code.

 findStock = (query, cb) => {
        console.log('find stock ' + query);
        if (query === '') {
            console.log('set default sgs');
            this.setState({suggestions: []})
            return [];
        }

        else {
            axios.get('http://suggest.hub.daum.net/suggest?q=' + query + '&mod=json&code=utf_in_out&callback=suggestCallback&id=54')
                .then((response) => {
                    console.log(response);
                    var suggestions = (JSON.parse(response.data.substring(0, response.data.length - 2).replace('suggestCallback (', '')).items);
                    cb(suggestions);
                })
                .catch((error) => {
                    console.log(error);
                    throw error;
                });
        }
    };


    render() {

        var that = this;
        const comp = (a, b) => a.toLowerCase().trim() === b.toLowerCase().trim();

        var _saveCondition = (stock, types, filters) => {
            Keyboard.dismiss();
            this.props.onStartCreateCondition(stock, types, filters);
        };

        return (
            <View style={{ flex: 1, justifyContent: 'flex-start', backgroundColor: '#3e63bc'}}>
                <HeaderComponent showToPrevious={true}/>

                <View style={{ padding: 30, zIndex: 10 }}>
                    <View style={{ marginBottom: 25 }}>
                        <Text style={{ color: '#fff', fontSize:15}}>알림 조건 추가</Text>
                    </View>

                    <View style={{ flexDirection: 'row', zIndex: 2, height: 45, alignItems: 'center' }}>
                        <View style={{ justifyContent: 'center', height: 100}}>
                            <Icon
                                name='search'
                                color='#fff'
                                size={25}
                            />
                        </View>
                        <Autocomplete
                            style={{ marginLeft:0, paddingLeft:0, fontSize: 14, height:34, color: '#afc5da' }}
                            containerStyle={{ marginLeft: 10, flex: 1, height:40}}
                            inputContainerStyle={{ marginLeft:0, paddingLeft:0, borderWidth: 0, borderBottomWidth: 1, borderBottomColor: '#afc5da', }}
                            listContainerStyle={{ marginTop:-10, paddingTop:0 }}
                            listStyle={{ margin: 0, backgroundColor: '#afc5da' }}
                            data={this.state.suggestions.length === 1 && comp(this.state.query, this.state.suggestions[0]) ? ['aaaaa'] : this.state.suggestions}
                            defaultValue={this.state.query}
                            onChangeText={(text) => {

                            this.setState({ query: text});
                            this.findStock( text, function(sgs) {
                            that.setState({suggestions : sgs})
                             });

                            }}
                            placeholder="종목명을 입력하세요."
                            placeholderTextColor={'#afc5da'}
                            renderItem={data => (
                            <TouchableOpacity onPress={() => {
                            this.setState( { query: data });
                            that.setState({ suggestions : []})
                            Keyboard.dismiss();
                            }}>
                                <Text>{data}</Text>
                            </TouchableOpacity>
                        )}
                        />

                    </View>
                    ....

Ios axios network error

The server should be setting the following CORS headers along with the response:

You might have to tweak the values depending on your use case, but open the Network tab in your browser, click on the request and check if your server is setting these CORS-related headers.

The headers are:

• Access-Control-Allow-Origin — which origins are allowed to make requests to the server.
• Access-Control-Allow-Methods — which HTTP methods the origins are allowed to use when making requests to the server
• Access-Control-Allow-Headers — which HTTP headers the origins are allowed to use when making requests to the server
• Access-Control-Allow-Credentials — whether to expose the server response to the frontend when the request’s credentials mode is set to include . When credentials mode is set to include , our frontend will always send user credentials (i.e. cookies, auth headers) even for CORS calls.

There is also an Access-Control-Allow-Credentials header. Setting it to true is only necessary if your browser sends user credentials with requests (e.g. cookies or the Authorization header).

When an asterisk * is set for the Access-Control-Allow-Origin header, any origin on the internet can access the server.

You would want to narrow this down in production, but it’s a useful tool when debugging.

Note that the Access-Control-Allow-Credentials header cannot be set to true if Access-Control-Allow-Origin is set to an asterisk * .

When the Access-Control-Allow-Headers is set to an asterisk, all headers are allowed in a preflight request.

Make sure that the URL you’re passing to axios is correct #

Make sure that the URL you’ve specified when making the HTTP request is correct and complete.

Источник

Axios returns a generic «Network Error» even when the request got a response code #4420

Comments

Miodec commented Jan 23, 2022 •

Describe the bug

When making a request to my API, the catch block has a generic «Network Error» message, but when checking in the network inspector the request got a response code 413. This causes my users to incorrectly report that ‘the website thinks i dont have a solid internet connection’. I suspect this happens for other codes too because this has been going on for a while.

To Reproduce

Make a request with a very large payload to trigger a 413 response

Expected behavior

The catch block should have the response code

Environment

• Axios Version: 0.25.0 and 0.21.2
• Adapter: xhr (i think? i dont remember changing this, so i guess whatever is default?)
• Browser: Chrome
• Browser Version: 97.0.4692.99
• Node.js Version: 14.18.1
• OS: OSX 12.1

Additional context/Screenshots

The text was updated successfully, but these errors were encountered:

gigerIT commented Jan 24, 2022 •

We also see an increased number of Network Errors in our app. It must be iOS related, the logs shows only: iPhone, Mac, iPad (90% with iOS 14.X) devices for it.
Downgrading to 0.24.0 now to check if it fixes the error.

Edit: same issue with 0.24.0
Exception:
Error: Network Error
at apply(./node_modules/core-js/internals/wrap-error-constructor-with-cause.js:34:66)
at Error(./node_modules/core-js/modules/es.error.cause.js:28:43)
at createError(./node_modules/axios/lib/core/createError.js:16:19)
at apply(./node_modules/axios/lib/adapters/xhr.js:117:14)
at r(./node_modules/@sentry/browser/esm/helpers.js:73:23)

Edit2: the issue startet on January 21. with axios 0.21.4. We did no updates or changes at this day, so i highly suspect it is caused by an iOS update/security patch. I wasn’t able to reprocude it on our iOS test devices so far.

felipe7229 commented Jan 24, 2022

Same issue happens in my application. I’m waiting for more details

essedger commented Jan 25, 2022 •

Same issue happens in my application too.
React Native, iOS 15.0, iPhone 12 simulator, axios 0.24.0 (tried 0.25.0 — the same issue)

This comment has been hidden.

Miodec commented Jan 28, 2022

Any chance you could have a look into this? I feel like this is quite important, since it makes it impossible to do proper error handling, makes it harder to debug and confuses users.

essedger commented Jan 28, 2022

@manugch @Miodec do you have any DNS ad blockers? I disabled my AdGuard and now it works fine. Can you check any any blockers/vpn?

gigerIT commented Jan 28, 2022 •

@manugch @Miodec do you have any DNS ad blockers? I disabled my AdGuard and now it works fine. Can you check any any blockers/vpn?

No Adblockers. I also see the error happening on visitor devices in our sentry logs, over 112 iOS devices by now who crashed with that unhandled «Network Error».
It affects only iOS devices as I said before Mac, iPhone, iPad mostly iOS/Safari 14.1.X

Miodec commented Jan 28, 2022

@manugch @Miodec do you have any DNS ad blockers? I disabled my AdGuard and now it works fine. Can you check any any blockers/vpn?

Tested without adblock — same thing.

kumarldh commented Feb 14, 2022

Somewhat similar situation for my ecommerce store as well. 91% «Network Error» on Safari(iOS). Safari follows a strict «Same Origin Policy» and I have noticed that most MarTech integrations throw errors on Safari. However, for me, these 91% errors are in my app and not in with 3rd party tags/pixels.

DerekSteinke commented Feb 15, 2022 •

I am seeing the exact same issue. A generic error saying Error: Network Error with no other information when getting 403s. According to the docs, the error should still include the response code and headers, but it doesn’t.

• Axios 0.21.4 & 0.26.0
• Node.js v16.13.1
• Firefox 96.0.3 & Chrome 98.0.4758.82
• Windows 10 Pro (Build 19041)

pierroberto commented Mar 2, 2022

I had a similar problem. I realized that was a CORS problem. Do you have any OPTIONS call before the actual API call?

kumarldh commented Mar 3, 2022

@pierroberto I see this error for API calls which are on same domain, relative paths like /api/getsomedata .

Tofandel commented Mar 10, 2022 •

Looking at the code, there seems to be a catch all in the XHR adapters https://github.com/axios/axios/blob/master/lib/adapters/xhr.js#L118

It’s not there in the HTTP adapter which will give the correct error so you may want to switch to that

I think it’s because the XHR spec doesn’t give any clue about the error, so I don’t think it can be fixed. As your then dependant on the browser implementation to trigger the .onError only if HTTP code = 0, and it seems some will trigger this with codes in the 400 range

Miodec commented Mar 13, 2022 •

I think it’s because the XHR spec doesn’t give any clue about the error, so I don’t think it can be fixed.

So, why does the console correctly show errors like ERR_FAILED 413 in this case, or CONNECTION_REFUSED or SSL_CERT_DATE_INVALID that I ran into in other cases? All of them give Network Error , but somehow show up correctly in the console.

Pretty sure using HTTP is not the best solution as its not supported in every browser (webpack replaces it with xhr)

EDIT: Right.. Im assuming its related to the // Real errors are hidden from us by the browser comment.

Miodec commented Mar 13, 2022

Alright, I figured things out (im still learning so some details could be wrong)

Basically, there is no way around it. Axios is just a wrapper for XMLHttpRequest (just realised that’s where the XHR acronym comes from) to make it a bit easier to use and less complicated to write. Axios gives us a Network Error because xhr itself doesn’t give us any info about the error. You can see for yourself by doing a simple request to an endpoint that doesn’t exist:

The console.log will give us (drumroll please):

Absolutely nothing 🙂

However, the console error will show GET http://localhost:5005/ net::ERR_CONNECTION_REFUSED (still don’t understand why the error is in the console but not in the event listener parameter)

So either way, this is not the fault of Axios. The only fix here that was mentioned by @Tofandel is to switch to the HTTP adapter at the expense of some compatibility — I don’t know how big this expense is exactly. Axios uses Node’s HTTPS module in its HTTP adapter and I’m not sure yet what things like webpack will replace it with. If I remember ill update this comment with my further findings.

Источник

Get requests giving «Network Error» for react native 0.59.10 built with xcode 11 for devices with iOS 13 #2505

Comments

RogerParis commented Oct 30, 2019

Describe the bug
After upgrading to xcode 11, in my react native application builds, all GET requests get «Network Error» for devices with iOS 13

To Reproduce
This is happening with all react native applications built with xcode 11 for devices with iOS 13.
For devices with iOS 12 everything works as expected.
And builds with xcode 10.3 works for devices with iOS 13 too.
It’s the combination of axios with xcode 11 for iOS 13 devices only.
Apps with fetch instead of axios work for iOS 13 devices. So we will have to unfortunately switch to fetch if we don’t find a solution.

Expected behavior
I expect that the GET requests work and don’t always send «Network Error» for apps with devices with iOS 13 built with xcode 11

Environment:

• Axios Version 0.19.0
• XCODE Version 11
• react native Version 0.59.10

The text was updated successfully, but these errors were encountered:

yasuf commented Oct 30, 2019

can you try using axios version 0.18.0? I see that low level errors are caught by that Network Error but if 0.18.0 works, that can help us debug this by seeing the diff between versions

RogerParis commented Oct 30, 2019

Thanks for your answer @yasuf . Unfortunately I was at 0.18.0 before and this happens. I hoped the upgrade to 0.19.0 would help but it didn’t.

whhlulu commented Oct 31, 2019 •

There is the same phenomenon. Would you like to solve it?

I’m trying to do this, and I can fix it.

yasuf commented Oct 31, 2019 •

it would help if I can have an example project to see the error and try a few fixes on the axios end, is the error happening on any request?
edit: nevermind I just saw your comment about it being on all GET requests, I can investigate with that

whhlulu commented Nov 1, 2019

I can’t give an example, it’s too much trouble, I don’t know how to provide.
Get request I gave the ’data‘ property in ’options‘, then, I got a very clear error: ‘GET method must not have a body’, after deleting ’data‘, it’s all right

RogerParis commented Nov 4, 2019

Thanks @yasuf . Let me know if you find something. I don’t send any data so I don’t think is the same problem as whhlulu

RogerParis commented Nov 7, 2019

@yasuf Did you have the chance to check it?

mspitzenberg commented Dec 3, 2019

@yasuf Would be awesome to get an update as well

StevieWag commented Dec 4, 2019

Same problem here.

imdanielpiva commented Dec 23, 2019

Having the same problem, I’ve commented more about it here #2580 (comment)

Источник

Error: Network Error #2766

Comments

2xSamurai commented Feb 19, 2020 •

Describe the bug
I have a react native app.
All my Axios requests are failing on anrdoid 7.
It works flawlessly on iOS and newer Android versions.
I am calling a serverside API. And no I am not using localhost.
I think CORS are also setup correctly.

This is what I am getting as a response.
Error: Network Error
at createError (createError.js:16)
at XMLHttpRequest.handleError (xhr.js:83)
at XMLHttpRequest.dispatchEvent (event-target-shim.js:818)
at XMLHttpRequest.setReadyState (XMLHttpRequest.js:574)
at XMLHttpRequest.__didCompleteResponse (XMLHttpRequest.js:388)
at XMLHttpRequest.js:501
at RCTDeviceEventEmitter.emit (EventEmitter.js:189)
at MessageQueue.__callFunction (MessageQueue.js:436)
at MessageQueue.js:111
at MessageQueue.__guard (MessageQueue.js:384)

To Reproduce
Try an axios request in Android 7

Expected behavior
Not to fail I guess.

Environment:

• Axios Version 0.19.2
• OS: Android 7
• Additional Library Versions [React 16.9.0, React Native 0.61.5]

Additional context/Screenshots

These are there in the Manifest file in Android.

The text was updated successfully, but these errors were encountered:

Источник

«NETWORK ERROR» when making API call in react-native Android, while works in iOS #31045

Comments

callmemonky commented Feb 24, 2021 •

Please provide all the information requested. Issues that do not follow this format are likely to stall.

Description

API calls not working in Android devices, while its working in iOS simulator and device

My network_security_config.xml

I’ve included this file (network_security_config.xml) in AndroidManifest.xml (android/app/src/main) too.

My FLIPPER_VERSION

Also I’ve commented out

API calls are successfully working in iOS devices but not working in android.

React Native version:

System:
OS: macOS 11.2.1
CPU: (8) x64 Apple M1
Memory: 33.83 MB / 8.00 GB
Shell: 5.8 — /bin/zsh
Binaries:
Node: 14.15.3 — /usr/local/bin/node
Yarn: Not Found
npm: 6.14.9 — /usr/local/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.10.1 — /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
Android SDK:
API Levels: 29
Build Tools: 28.0.3, 29.0.2
System Images: android-29 | Intel x86 Atom_64
Android NDK: Not Found
IDEs:
Android Studio: 4.1 AI-201.8743.12.41.7042882
Xcode: 12.4/12D4e — /usr/bin/xcodebuild
Languages:
Java: 1.8.0_282 — /usr/bin/javac
Python: 2.7.16 — /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: ^16.13.1 => 16.14.0
react-native: ^0.63.2 => 0.63.4
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

Steps To Reproduce

Provide a detailed list of steps that reproduce the issue.

1. Tried making API calls in Android.
2. Its not working, its working in iOS devices.

Expected Results

Successful API Calls.

Snack, code example, screenshot, or link to a repository:

Please provide a Snack (https://snack.expo.io/), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
You may provide a screenshot of the application if you think it is relevant to your bug report.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

The text was updated successfully, but these errors were encountered:

Источник

Do you get the Unable to join the network error on your iPhone in iOS 15? This is a new popup that informs you about a potential Wi-Fi issue! Your device detected that the network is operating on WiFi channels that are in use by several other nearby networks. This can lead to interferences and performance issues!

How To Fix Unable To Join Network Wi-Fi Error

So, if your WiFi connection acts glitchy, is lagging or not performing as usual, iOS 15 (iOS 16) recommends you to restart your wireless router!

The reasoning behind this is that a reboot might allow your WiFi router to automatically reconfigure and choose the best channel to use, in the current circumstances.

Update (October 10)

Disable MAC Filering

Joseel informs that disabling Mac filtering solved this issue on an ASUS router.

Tip: You can turn Mac Filtering back ON if you disable Private Address (it turns on automatically after update). Disable Private Address in Settings -> Wi-Fi -> tap the ‘i’ icon next to the network name and turn Off Private Wi-Fi Address.

Fix has also recently been confirmed by Angus for the Unable to Join Wifi network error in iOS 16:

“After ios 16 update last night, same problem as above posters. turn off the Private Wifi-Address option or add the Private MAC Address shown to the MAC Filter Allow list, solved it for me.”

How To Restart Wi-Fi Router

Wireless routers can be restarted both manually or via their software interface.

Some reboot a WiFi router by turning it OFF and then back ON, however this might not cause a full restart. Instead I recommend you to do the following:

• 1. Turn your Wi-Fi router or modem OFF, by unplugging it from the power outlet!
• 2. Wait for 30 seconds and then plug it back in to the power source.
• 3. Allow the device one or two minutes to turn back ON. If it doesn’t press the power button to start it manually!

Important: Don’t confuse restart (reboot) with reset. Resetting a WiFi router implies whipping out all the info, including settings and WiFi passwords. That’s not what the ‘Unable to join network’ WiFi error suggests you to do!

How To Restart WiFi Router From Safari

• You can also reboot your router by tapping the https://192.168.0.1 address into Safari.
• You will have to log-in. Depending on the type of your wireless router the credentials are either admin (username), admin (password), or any other strings that you’ve configured.
• In the admin panel you will find the Restart Wi-Fi router option!

Why Is This New Wi-Fi Warning Helpful?

Users that live in an apartment building or any other location that has lots of nearby WiFi networks will find this new popup quite useful.

Most hotspots are set to automatically select the less crowded Wi-Fi channels, however sometimes having a popup that informs you about a possible set up problem can be very useful and help you to quickly solve WiFi problems.

Often when Wi-Fi networks are slow, they’re dealing with a channel problem caused by interference. It takes time for a WiFi router to change channels. Getting the notification will allow you to rush the change via the restart procedure.

Trick To Check Wi-Fi Channels Used By Nearby Networks

Unfortunately iOS 15 still doesn’t allow Wi-Fi to show the available channel numbers. However, there is a workaround:

• 1. Download Apple’s AirPort Utility app (direct link).
  Fact: You don’t need an AirPort compatible device for this to work!
• 2. Open Settings on your iPhone and scroll for AirPort Utility. Tap it.
• 3. Enable the Wi-Fi Scanner option.



• 4. Return to the AirPort Utility app and tap on Wi-Fi Scan available in the top-right corner.
• 5. Go For Scan.
• 6. Tap on the detected nearby networks to get info about channels, frequency, noise and more!

Has the ‘Unable to join the network’ error been fixed on your iPhone after restarting your router? Did you perform other fixes in order to solve it? Share your feedback in the comments section.

Related: Is your iPhone prompting you to share Wi-Fi password with a nearby Apple device every time you unlock it? This is an iOS 15 bug. Here is how to fix it!