We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
startURLSchemeTask
A potentially nil value is passed to a method with a non-null specifier.
didReceiveData should not be called with a nil value
didReceiveData
nil can be passed
This is a quick fix: just wrap line 78 with an if statement.
The text was updated successfully, but these errors were encountered:
(ios): nil check in didReceiveData in schemehandler
adcf6ca
Closes apache#903
bfe31c9
Closes #903
Thank you for this report. This is indeed a problem I just submitted a pull request to fix this.
Sorry, something went wrong.
(ios): nil check in didReceiveData in schemehandler (#1035)
be1cd7d
Successfully merging a pull request may close this issue.
Bug Report
Problem
A potentially nil value is passed to a method with a non-null specifier.
What is expected to happen?
didReceiveData
should not be called with a nil valueWhat does actually happen?
nil can be passed
Information
This is a quick fix: just wrap line 78 with an if statement.
Command or Code
Environment, Platform, Device
Version information
Checklist
The text was updated successfully, but these errors were encountered: