-
Notifications
You must be signed in to change notification settings - Fork 2.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
v6 Storage refFromUrl does not work correctly #2753
Comments
Could you try the URL shown in the Firebase console, e.g: The tests also show this working: https://github.com/invertase/react-native-firebase/blob/master/packages/storage/e2e/storage.e2e.js#L39 |
Hello 👋, to help manage issues we automatically close stale issues.
|
Closing this issue after a prolonged period of inactivity. If this is still present in the latest release, please feel free to create a new issue with up-to-date information. |
I'm having a similar issue with the I can reproduce this with
which results in
Using If you use Is this expected? v5 was working properly. |
This is 100% still an issue, btw. I'm experiencing it exactly as described above. I have no idea if it helps, but this is only happening on android. |
I have this issue too. Worked well on V5. |
@rkuncewicz We seem to have an issue with handling encoded urls which I will create a new issue for. @ThomasFindlay If you can still provide an example of what url you are using then we can potentially se that for an different test case? @sarykemmoun If you could also provide an example of this, most cases we have found so far have been encoded or incorrect urls |
PR Added at #3369 |
Seems to have something with how the ref is generated from HTTP URLs. I printed the storage ref that "doesn't exist" to console, it was missing the ".appspot.com" part of the bucket name. Normally you get something like gs://${project id}.appspot.com/${restOfPath} As a temporary workaround I grabbed the rest of the pathname and created a new ref using storage().ref().child( |
Hello 👋, to help manage issues we automatically close stale issues.
|
This issue still exists with version 7.0.1. The slashes within the path are now handled correctly, but the ref is still not valid. Like @HwangPeter observed, I confirmed that valid refs have a bucket named "{BUCKET}.appspot.com" but the refs from |
PR added at #3775 |
I am also facing the same issue, refFromURL is not working
And the error I got is
Any workaround for this? |
Solved this issue #3820 |
I am having the exact same issue when using refFromURL. And following temporary solution worked like a charm.
However, this is a workaround. This bug needs to be fixed. |
@enosh94 there's a PR #3775 working through review now, you can probably apply the fix locally via https://github.com/ds300/patch-package - when you say it "needs to be fixed" it implies someone should do it, with open source that's all of us and if you are suffering from this exact problem you would be a perfect test case, getting success reports for the proposed change would help it be fixed |
Thank you very much for this |
Issue
Describe your issue here
v6 refFromURL does not work on the url below. v5 worked without problems.
In v6 it throws an error that object was not found even though it exists. I was able to delete the file when using .ref(path).delete(). I don't think that the stack trace is really useful, but here it is.
Project Files
iOS
Click To Expand
ios/Podfile
:# N/A
AppDelegate.m
:// N/A
Android
Click To Expand
Have you converted to AndroidX?
android/gradle.settings
jetifier=true
for Android compatibility?jetifier
for react-native compatibility?android/build.gradle
:// N/A
android/app/build.gradle
:// N/A
android/settings.gradle
:// N/A
MainApplication.java
:// N/A
AndroidManifest.xml
:<!-- N/A -->
Environment
Click To Expand
react-native info
output:react-native-firebase
version you're using that has this issue:Firebase
module(s) you're using that has the issue:TypeScript
?Think
react-native-firebase
is great? Please consider supporting all of the project maintainers and contributors by donating via our Open Collective where all contributors can submit expenses. [Learn More]React Native Firebase
andInvertase
on Twitter for updates on the library.The text was updated successfully, but these errors were encountered: