-
Notifications
You must be signed in to change notification settings - Fork 270
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
Rename RCTWKWebView to CRAWKWebView to avoid symbol clash with RN 0.57 #195
Conversation
…NSHTTPURLResponse, so headers and status code might not be available
We really need this in master since it's not possible to upgrade to RN 0.57. And RN < 0.57 doesn't work with Xcode 10 |
+1 |
if([navigationResponse.response isKindOfClass:[NSHTTPURLResponse class]]){ | ||
headers = ((NSHTTPURLResponse *)navigationResponse.response).allHeaderFields; | ||
statusCode = ((NSHTTPURLResponse *)navigationResponse.response).statusCode; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How is this part related to the symbol clash and rename?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know about the duplicate symbol error. But the specific lines of code I commented on do not relate to those symbols. It looks like a different commit accidentally came along for the ride.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this happens to be a fix for #199
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this happens to be a fix for #199
I am on vacation now and I will merge it after I am back |
on npm now: 2.0.0 I have also renamed files and updated the example project to RN 0.57. |
Fixes #194