-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
No marker after build to prod #953
Comments
Have you checked browsers console for errors? |
This error occurs :
The error only show in prod, in local all work great, for that I'm not able to debugg better. Can you please confirm if it is a general bug or a specific one? |
Looks similar to this: https://www.traccar.org/forums/topic/modern-build-from-source-and-deploy-y-is-not-defined/ |
I followed what will_ed suggested. It's really strange to get the error only in production, in your side, you can build the app and get the marker shown in the map? |
Haven't tried release version yet. |
That's not really a good solution. We want to support older browser versions as well, when possible. |
@tananaev |
Wonder if we can find where exactly it breaks. Is it some specific browser? |
|
I have a question out of the subject but it will be really helpful to me and to any one who want to collaborate in this project, how did you know that the problem was due to the browser support? I past the last 4 day trying to debug it without success. |
@BIhab - just look into package.json if it works on development and not on production it means there must be a difference somewhere |
Feels like I lack on experience, I'll learned from you thanks a lot |
Decided to go with this for now: "production": [
"defaults",
"not ie 11"
], |
Describe the bug
After build the app to prod, no marker shown on the map. - works fine on prod -
I think the problem occurred when svg icons was moved from public to resources and it's related to the asset being static, not sure about that, not even sure if I'm not the only one facing that issue.
To Reproduce
Steps to reproduce the behavior:
Desktop (please complete the following information):
Smartphone (please complete the following information):
On mobile too
Even on docker
The text was updated successfully, but these errors were encountered: