I'm trying out Polymer web components for the first time and everything is working perfectly fine using Brackets Live Preview.
But when I try to deploy the app using Firebase hosting I get a READ ERROR.
READ ERROR - Could not read directory. Remove symbolic links / shortcuts and try again.
I updated firebase-tools but still get the same error.
I've spent so many hours going through tech forums hoping I'd find somebody having the same issue but unsuccessful.
Any information regarding my inquiry is much appreciated.
Your app's directory contains a shortcut or a symbolic link. You need to replace that with the actual content before firebase-tools can upload the site. Once you've removed the shortcut firebase deploy should work as expected
Related
This is my 5th project deployed to the Vercel via GitHub (after almost year break). However after importing the project from the GitHub and pushing it to Vercel I am getting 404 page with a link to unhelpful page with explanation why I might see the 404 page (which naturally does not resolve even remotely the issue). I don't understand. My previous 4 projects were deployed this way and they work to this day. Simple push to the GitHub will update the project and publish it live. The projects says it is build, there are no errors. It works on local building it with npm run dev.
The project was added the recommended way as per the Next documentation using npx - command was copy-pasted from the documentation.
I have consulted this with how to publish Next.js project to Vercel and there are simple 4 steps which I did.
Does anyone maybe had similar experience and managed to resolve this kind of issue? Thank you kindly for your time.
On firebase console, it says my files are successfully deployed but in actual web page, it is just a black page with one senetence "Error: could not handle the request"
i did not started this project i am working on, and i have no idea what to do.
BTW, no errors are loged in firebase-debug.log
All things are clear, except for the web page.
As far as i know, this is based on Next.js, if you would care to know.
I opened up the file from the root folder, used "cd (myfilename)" command to go into the actual project, and then executed firebase deploy.
I googled thousands of times, and I doubted these:
node js version problem?
os problem? (i work on Window, and the first start was from Mac)
number one i solved. number two? i dont know.
Please help me out if you have any idea or can guess why this happens.
I have a multi-page web application written in Flutter which uploaded on Firebase hosting . All the pages work fine but half of the homepage is grey. Photo attached. Really appreciate for help.
Also, I'm getting this error when I run: flutter run -d chrome --release
Oops; flutter has exited unexpectedly: "ProcessException: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event
log or use the command-line sxstrace.exe tool for more detail.
Command: C:\Users\abc\AppData\Local\Google\Chrome\Application\chrome.exe --user-data-dir=C:\Users\abc\AppData\Local\Temp\flutter_tools.2b59d482\flutter_tools_chrome_device.4fad7966 --remote-debugging-port=2576 --disable-background-timer-throttling --disable-extensions --disable-popup-blocking --bwsi --no-first-run --no-default-browser-check
--disable-default-apps --disable-translate http://localhost:11541".
I have also faced same issue while host web app in firebase.
the issue is not in firebase host. the issue is in your code. your code will completely work in debug mode. but not in released mode.
check every warning in logs.
it is mostly happen because of wrong use of expanded or flexible widget
So I just got into meteor like a month ago, and I just finished my first website after about 2 weeks. Its a social media website kinda like twitter. I also downloaded accounts-ui and accounts-password packages, and I implemented them in the website pretty loosely. But heres the thing, I wanna deploy the website to galaxy using the subdomain .meteorapp.com, and it just doesn't seem to work. I keep getting the same error in the logs which is: "Error: MONGO_URL must be set in environment". I looked it up, and I just dont know what to do. from what I read online you need to make a settings.json file, then add this code:
"galaxy.meteor.com": {
"env": {
"ROOT_URL": "http://blueslipgang.meteorapp.com/",
"DEPLOY_HOSTNAME":"galaxy.meteor.com"
"MONGO_URL":"mongodb://127.0.0.1:3001/meteor"
}
}
so thats what I did, and i added this file to the client file, the server file, and even inside no file. I just cant seem to get the website to deploy. I really wanna deploy this website so me and my friend's can use it, but its just not deploying.
so what am I doing wrong, and what do I need to do to fix it. Any help would be really, really appreciated, I worked pretty hard to make this app, and it would really suck if I cant even deploy it.
Thank you
Galaxy doesn't provide a MongoDB service, so you will need to sign up for a MongoDB account (Atlas has a free tier) and use that. Setting the MONGO_URL to localhost/127.0.0.1 will throw an error on launch.
Also, to use the settings.json when deploying, you will need to make sure you have the --settings flag set in your deploy command:
DEPLOY_HOSTNAME=galaxy.meteor.com meteor deploy [hostname] --settings settings.json
Also have a read through the official galaxy guide
If you have ongoing problems, I suggest posting on the Meteor forums and the community can help step by step with each issue you run into
I've been at this for past 2 days and I'm getting weird errors from the store.
I'm trying to upload an update to my application "CoManga" via the store and it's not working out.
I'm working on Xamarin.Forms (UWP) and before making the appxbundle, I made sure and "associated my app with CoManga" from my developer account. All the information over there matches and should work fine without any issues.
Then I made a release of my UWP app, got the bundle and I tried to upload it to UWP.
It said that the Publisher info is different, so it couldn't upload. This is weird because I tried signing the bundle with my developer account itself.
Now, I tried building and signing the app bundle from app center. I got the appxbundle and that I tried to upload. But, since today it's giving me weird error :
The package comic_dl.UWP_2.1.15.0_ARM_x86_x64.appxbundle is taking a
long time to process. If this isn’t completed soon, try refreshing the
page, or remove the package and then upload it again. If you continue
to see this issue, contact support.
This package I tried to build from my system manually : https://drive.google.com/open?id=1VVvF6IB70R2DKNUgBJcqw-HryL1LIwgo
This is what I got from App center : https://drive.google.com/open?id=1o0sGKU2AKVgrcTelIoRFz7QCe8Do0WJ3
This is the Store ID : 9N81F8B5WW93
Can someone guide me what I might be doing wrong/missing something.
Thanks
EDIT Update : So, I followed the suggestion and contacted Microsoft's Team for help on this issue. After 3 months of multiple contacts, I was able to get someone to reply back and follow the case. Even they tried things on their end and I tried by deleting all the certificate files I had in my current project and tried to manually build the manifest file and then it worked. I'm not entirely sure what worked out in the end. But, you can try these things if you run into this issue.
1.) Clean your project.
2.) Delete .vs directory.
3.) Look for any certificate files in your project. Back them up somewhere else and then delete them from the project (Don't exclude from project, just delete them entirely). Clean and rebuild your solution.
4.) Check if the application is already installed on your system (When you debug, VS will install your UWP app on your machine to run it). If it's installed, uninstall it completely.
5.) Make a backup of your manifest file and try to create a new manifest file.
These are the links I received from Microsoft Help:
PFN and package publisher name must match values here: https://partner.microsoft.com/en-us/dashboard/products/{YourAppID}/identity
Update manually: https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/how-to-create-a-package-manifest-manually
Update in VS: https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/generate-package-manifest
If these values were pulled from test certificate, partner needs to update their test cert: https://learn.microsoft.com/en-us/windows/msix/package/create-certificate-package-signing
I think this problem is not caused by anything code related, but rather it is a problem on the Store side. I would suggest contacting the Store support, they should be able to investigate if there is something wrong with your app package or the problem is on their side.
For support go to the official website, click the Contact Us tab and fill out the form accordingly.
The team should be able to advise even for the first error with different publisher info. If your app was always associated with the same account, there is no reason it should give you such an error message.
I had this issue gazillion of times. It is so frustrating. That error message isn't useful at all.
Anyway - I think it is something in Package.appxmanifest, something in Identity tag.
Retrieving some necessary info from store helped me.
Click right on your project -> Publish -> Associate App with the Store. This will update Package Display Name,Package Name,Publisher ID,Publisher Display Name and Version with correct values (within Package.appxmanifes).
Also be careful with version number. The last from numbers must be zero. 1.1.1.0 is fine, while 1.1.1.1 is not.