Skip to content
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

Calling Storage.reference(...).putFile throws EXC_BAD_ACCESS. #3282

Closed
ghost opened this issue Jun 28, 2019 · 2 comments
Closed

Calling Storage.reference(...).putFile throws EXC_BAD_ACCESS. #3282

ghost opened this issue Jun 28, 2019 · 2 comments
Assignees
Milestone

Comments

@ghost
Copy link

@ghost ghost commented Jun 28, 2019

  • Xcode version: 10
  • Firebase SDK version: 6
  • Firebase Component: Storage
  • Component version: All of them

Calling Storage.reference(...).putFile throws EXC_BAD_ACCESS with a reference to

 - (void)dispatchAsync:(void (^)(void))block {
  dispatch_async(self.dispatchQueue, block);
}

The correct way to call this is Storage.storage().reference(). Lots of people are pretty confused. See this post and this.

I feel like a runtime warning would be appropriate if it can be done. I think the self variable is null in this case.

@schmidt-sebastian
Copy link
Member

@schmidt-sebastian schmidt-sebastian commented Jul 1, 2019

@sujeathpareddy Thanks for filing this! I will see what we can do to improve the observed behavior.

Loading

@schmidt-sebastian
Copy link
Member

@schmidt-sebastian schmidt-sebastian commented Jul 2, 2019

When #3294 gets released, we will throw an assertion for calls to Storage(), which will prompt the user to use one of the defined API endpoints.

Loading

@firebase firebase locked and limited conversation to collaborators Oct 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

3 participants