-
-
Notifications
You must be signed in to change notification settings - Fork 167
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
File not uploded google storage bucket but I can see it in .meteor.../assets/app/upload folder #697
Comments
@nikhilgoswami we need more info, please follow our issue template:
Thank you |
metoer files version ostrio:files@1.10.2 |
@nikhilgoswami thank you for reporting about this, could you post your implementation of integration with google cloud. This tutorial is made by contributors: @salmanhasni, @amos-whitewolf, and @jeremywrnr — hope they can tell you more about Google Cloud integration |
@nikhilgoswami can you please enable the debug flag true |
@nikhilgoswami I have made the change to documentation, lets wait for reviewers to have a look over it meanwhile you can try it. |
Console logs when debug is set to true My Implementation
}
} |
This error was caused after I install react@16.8.0 and react-dom@16.8.0 and @material-ui/core using meteor yarn add. Funny thing is even after reverting back the changes doesn't resolve the problem it persists. |
Thanks for your help. It turns out meteor yarn was the culprit deleting node_modules and using good old meteor npm install is working smooth for now. If the problem persist I will reopen the issue. |
Seems like we all should follow best practices. |
I'm having an issue:
I get no errors on client and server I get file is uploaded successfully but then I cannot see it on google cloud storage bucket, but I can see it in assets/app/upload folder of .meteor
This started happening after I cloned project from github added settings.json. Ironically in 1st project the upload works and I can see it on google bucket but in new cloned project I get this defect. Any Idea what could be missing.
Documentation is missing something or incorrect (have typos, etc.):
I think the documentation for google is a bit old and needs to be updated.
The text was updated successfully, but these errors were encountered: