-
Notifications
You must be signed in to change notification settings - Fork 230
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
iOS Integration Validator Bugfix (for client<>server URI scheme check) #1311
Conversation
… be the first URI scheme in the list for the integration validator to pass Looped through each of the URI schemes so that Branch doesn't have to be the first URI scheme in the list for the integration validator to pass
@rob-gioia-branch is this PR still valid? Do you need someone to review? |
@ahmednawar yes it is still valid, would be great if we could get someone to review it. Thanks! |
@NidhiDixit09 can you please review this PR? |
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 have validated fix with my test app and adding some random url schemes. Fix looks good to me.
Thanks @NidhiDixit09 ! Do you have recommendations on fixing the merge conflicts so that this can be merge into master? Thanks! cc: @ahmednawar |
Fix for iOS integration validator. This fix will loop through each of the URI schemes while matching.
@rob-gioia-branch I have merged master into this branch and we dont have any conflicts now. |
Merged, thanks @NidhiDixit09 ! I appreciate the help |
Reference
No ticket - this was confusing clients, so I wanted to fix this.
Summary
Currently, our iOS integration validator would check for the Branch URI scheme as the first URI scheme in the list (apart from a few like facebook, etc... that are hardcoded for it to skip when checking). The new code fixes this issue by looping through each of the URI schemes so that Branch doesn't have to be the first URI scheme in the list for the integration validator to pass.
Motivation
This was confusing clients.
To see an example of this issue, please view the Master ProServe iOS Branch
example-of-uri-scheme-bug
(Link: https://github.com/BranchMetrics/Master-Proserve-iOS/tree/example-of-uri-scheme-bug)I added
psmaster0
, an incorrect URI scheme, at index 0.This caused the integration validator check for the URI scheme to fail, even though the correct URI scheme of
psmaster
was in the list right below it.With the changes in this PR, the issue is fixed by checking if the correct URI scheme is present anywhere in the list
Type Of Change
Testing Instructions
To test this, do one of the following:
cc @BranchMetrics/saas-sdk-devs for visibility.