-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Vercel Deployment Error #547
Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 300.0 DAI (300.0 USD @ $1.0/DAI) attached to it.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work has been started. These users each claimed they can complete the work by 1 month from now. 1) iamonuwa has been approved to start work. I've worked on MyBitFoundation app in the past. I've deployed to vercel (formerly now). This is a simple issue for me to resolve. Learn more on the Gitcoin Issue Details page. |
@iamonuwa if you have any questions please join t.me/mybitio |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work for 300.0 DAI (300.0 USD @ $1.0/DAI) has been submitted by: @cryptnotiq please take a look at the submitted work:
|
I am working on #545 and trying to deploy the app to vercel. After making some fixes and changes locally, I got the app to work locally. It even worked locally with
vercel dev
without any problems.But when I deployed it to
vercel
, it's not working. I am getting the following error in Functions tab of deploymentsThe error most likely is caused because of some package/library not existing(or a different non-compatible version exists) in vercel's environment. Since it's running locally in my system, my machine might already have that package/library.
From what I understand and read about similar errors, it is something to do with gcc/g++ compiler version being different in vercel environment? and One of the packages in this app requires that version of gcc/g++? I am not sure completely.
I tried contacting vercel support. But they need a min reproducible repo that has similar bug. Only then, they will help us to resolve it. But, I have no idea which package in this app is causing the error, so it's difficult to create a min reproducible repo.
There is some discussion regarding this at vercel/vercel#4581
For the app to run locally, you can apply the changes from #546
The text was updated successfully, but these errors were encountered: