I have a Vue app that works on one (Windows) machine, but not on another (Mac) machine. The non-working one just gives a message "You do not have permission to access this app" in the browser.
The only error in the console is
DevTools failed to load source map: Could not load content for https://unpkg.com/#popperjs/popper.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
Any ideas? All my other Vue apps work fine
You didn't provide much information about what exactly you're doing that you're getting that error and where. That being said, this is likely not a Vue.js issue, rather a Mac OS issue with permissions. See if this question is related.
Additionally, the URL from the console https://unpkg.com/#popperjs/popper.min.js.map returns Cannot find package message, so it is indeed incorrect, the correct URL would probably be https://unpkg.com/#popperjs/core#2/dist/umd/popper.min.js.map
Related
I've been struggling for the past few days trying to resolve the issue with all my axios requests. No matter what I change, I keep getting the error:
[Error: Network Error]
When this error happens, it closes the application into the background of the phone but doesn't crash. There is not other error logs or warnings so it's I'm finding it hard to debug the issue.
This is not being sent to localhost, this is sent a public domain as I know there are people having issues with localhost and having to switch to use IP address. However it's happening when I'm using public domain.
Has anyone come across this with their expo build on android before?
Update:
The APIs work in postman, so it's only an issue when sending requests via the expo application.
Update Fixed:
Finally found the issue flagging:
canceled due to java.lang.NoSuchMethodError: No virtual method toString(Z)Ljava/lang/String; in class Lokhttp3/Cookie;
I had to had the following to build.gradle
implementation 'com.squareup.okhttp3:okhttp:4.7.2'
implementation 'com.squareup.okhttp3:logging-interceptor:4.4.1'
implementation 'com.squareup.okhttp3:okhttp-urlconnection:4.4.1'
Android dont accept HTTP protocol Api so keep sure you are using a HTTPS protocol Api
I'd like to use expo start --tunnel to allow connecting to the App over the internet.
However, right after starting, the DevTools open and show me the following error:
Error loading DevTools
ValidationError: "urlType" must be one of [exp, http, redirect, no-protocol]
The console shows me:
Starting Metro Bundler.
Tunnel URL not found (it might not be ready yet), falling back to LAN URL.
Tunnel URL not found (it might not be ready yet), falling back to LAN URL.
So far so bad.. I've then looked into the .expo/packager-info.json to see what URLs have been generated. The file looks like this:
{
"devToolsPort": 19002,
"expoServerPort": 19000,
"packagerPort": 19001,
"packagerPid": 7316,
"expoServerNgrokUrl": "https://sz-p2a.anonymous.123.exp.direct",
"packagerNgrokUrl": "https://packager.sz-p2a.anonymous.123.exp.direct",
"ngrokPid": 5316,
"webpackServerPort": null
}
Then I've tried to open these URLs on the target devices. When doing so, I get an SSLPeerUnverifiedException because of an invalid certificate. I think it's the same error that I get when navigating to the URL directly in the browser.
So, am I doing anything wrong or is the tunnel workflow broken right now?
What might I do to get it working?
I somehow bypassed this problem by removing https from the link.
To do so, take the expoServerNgrokUrl from .expo/packager-info.json and turn:
https://sz-p2a.anonymous.123.exp.direct
into
http://sz-p2a.anonymous.123.exp.direct
Then you can send it to any Expo device.
I had the same issue, logged out expo logout, logged in again expo login and it worked.
One of our clients is triggering this error when trying to use our site's file upload functionality:
[uwsgi-body-read] Error reading 65536 bytes.
Content-Length: 543426 consumed: 233 left: 543193
message: Client closed connection
Every other user that has tested uploading the same file has not been able to reproduce this issue even with same OS (Windows) and browser (Chrome). I searched but was unable to find an explanation of the "Client closed connection" error, so I am not clear what the usual causes are. Is there a particular category of issue that typically causes these errors in uWSGI?
I found this github issue which seems to suggest that the problem is related to Safari or IE, but the client is using Chrome on Windows, and we have been unable to reproduce with that same setup. We are using version 2.0.18 of uWSGI.
I was able to get on a call with the client and figured out what the issue was: he was trying to upload a file out of a shared drive. The file when chosen from a shared drive on a windows machine would fail, triggering the uwsgi-body-read error on the backend. When the file was dragged to the desktop and chosen from there, the upload succeeded without issue. The issue is potentially related to windows, because I was able to upload from a shared NAS from a Mac. My team has not yet investigated the issue further.
I have an app that is failing to load in IE. When I look in the console I see
The same code works in IE11 but the code not woking in RDP IE11 couldnot find out exact cause for the issue.
During save it says couldn't download zip document
SCRIPT7002: XMLHttpRequest: Network Error 0x800c0007, No data is
available for the requested resource
Had the same error. It was due to IE not handling deflate properly. Use gzip instead of deflate.
In Chrome 21.0.1180.75 on OS X 10.8, my Rails app fails to load:
(Image of error page)
The text is below, if you don't want to load the image:
This webpage is not available
The webpage at http://127.0.0.1:3000/ might be temporarily down or it may have moved permanently to a new web address.
Error 325 (net::ERR_RESPONSE_HEADERS_TOO_BIG): Unknown error.
It fails when I try to access it using localhost:3000, 127.0.0.1:3000, and 0.0.0.0:3000, but if I access using my local IP address, it's fine. This only happens in Chrome. Firefox, Safari, and Opera are able to load localhost perfectly fine.
I've already cleared cache and cookies, to no avail. Any ideas on what might be happening?
From http://productforums.google.com/forum/#!topic/chrome/N0zL6FXq2SE%5B1-25%5D:
Storing a too large array
Use of a header redirect during logic flow
Un-setting a cookie array
See if your code is triggering any of these situations.