-
-
Notifications
You must be signed in to change notification settings - Fork 180
Adding JVM support for Firebase Storage #704
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
Conversation
Is it possible to implement these changes directly in my personal project? I tried to clone the repo and checkout to this branch (to import the library locally), but I can't even sync the project, I'm facing an issue in all modules. It happens in all
Could anyone help me please? I would really appreciate it. This usage of storage is blocking my project |
You'll have to do the following:
alternatively: you can open ~/.m2/repository and copy the whole |
@pontomedon - You need to run
Then fix the errors, commit this and we will be able to merge in. |
This is based on previous work by Cesar Ramirez and it is obviously depending on work done on the java sdk: GitLiveApp/firebase-java-sdk#44
I know the checks are failing, I'll need some input on how I can publish a snapshot of
firebase-java-sdk
to make them succeed. It all works locally when deploying to maven local.I needed to make sure we never call the firebase storage API with
null
metadata - when doing this on a desktop target, theCONTENT_LENGTH = 0
header gets removed somehow, causing the firebase backend to respond with a HTTP 411. Passing defaults causes a few bytes to be serialized in the first requrest before the upload, which circumvents the problem.The root cause for this must be in the http driver somewhere, as it doesn't happen when running the same code on Android.