Fix unexpected login issues (#91)#93
Open
n-martin wants to merge 1 commit into
Open
Conversation
Updated login and login debug flow to support new SID cookie with port number appended
|
@n-martin currently app is broken for ios users. I can test when this is out of testflight and report back. |
Owner
Owner
|
There was another PR with similar changes, merged that one by chance. But issue should be resolved now on v3.1.1 which is test flight now. |
Author
@taylorcox75, no problem should I close this one then? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Updated login and login debug flow to support new SID cookie with port number appended.
Please don't hesitate to give me feedback, this is my first dive into typescript (coming from a C++/Python background). I've tested it locally on my iPhone and local qbittorrent server. I was encountering the problem described in issue #91 and no longer see it with these changes.