#90383: Issues in integrating FR iOS SDK along with AccessOne SDK #206
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
May 12, 2023 14:46
…n and FRAccessToken respectively
Contributor
|
@RabobankDigitalChannel Thanks for the PR. we will review this on our End. since the changes will breaks the test. we will need to evaluate this . we will keep posted. thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
JIRA Ticket
Raised FR support ticket number #90383
Description
Our mobile app was showing the run time error as AccessOne was also using the same class names as like FR for Token and AccessToken.swift files. We are raising the PR just by changing the class names from Token, AccessToken to FRToken and FRAccessToken.
Definition of Done Checklist: