fix: Handle NSNull
in iosCustomBrowser
param for logout
#1070
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
While there isn't an issue created specifically for what this PR is attempting to address, there are a few issues that seem to be related to it.
#1061 for example, which led to the fix introduced by #1064 addressed an issue on the
authorize
function.Unfortunately, the
logout
function is still failing to properly display the browser, causing the flow to silently fail wheniosCustomBrowser
is not provided, as[self getCustomBrowser:NSNull]
returnednil
.This seems to be happening on RN V0.77.1 with the new architecture enabled. Untested on other versions.
This PR adds a guard to fallback to the default external user agent when
iosCustomBrowser
isnil
orNSNull
.Steps to verify
iosCustomBrowser
option that includes:authorize(config)
andlogout(config)
in your code.authorize
(login) andlogout
calls via your application.