-
Notifications
You must be signed in to change notification settings - Fork 27.8k
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
Stocks example: 404 on resolving image assets #7
Comments
I noticed that the path mentioned in terminal is not the same as path of the resource: packages/sky/lib/assets/material-design-icons/navigation/2x-web Versus /packages/sky/assets/material-design-icons/navigation/2x-web |
@eseidelGoogle: Would you be willing to take a look at this on issue? |
You might want to try running this script: https://github.com/domokit/sky_sdk/blob/master/packages/sky/lib/download_material_design_icons |
To be sure I did a new test today:
I'm seeing this output: When verifying the path I'm seeing no files in the assets folder: |
Hi, sorry my team has been out of the office since the summit. As adam mentioned, there is a script included with the pub package which should download these icons for you. For example: cd examples/stocks Should start it with all the icons there. |
We've addressed this issue by introducing an FLX file that contains all the assets your app needs. |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
When running the sample application, material icons seem to be missing from the UI
Verifying the output in the terminal, I noticed the lines with a 404 code:
I went to check the mentioned paths and they were indeed non-exisitent. I stumbled on this python script to download the assets. In the screenshot below you can see the result after execution:
Running the application and remove/reinstalling the application resulted in the same 404 messages.
The text was updated successfully, but these errors were encountered: