-
Notifications
You must be signed in to change notification settings - Fork 17
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
Possible bug in parsing URL's that are created with a Captial letter - Empty BUO #104
Comments
@kwacks sorry for delay, ping please our support team, it is not a xamarin sdk issue because all data sdk receives from backend |
@kwacks were you able to file a support ticket for this issue? |
Yes, but no response from your team so far. |
@kwacks would you be willing to email me your support ticket information? I can look into the status of this ticket for you. |
Happy to - what's your email or should I add it here?
+bdm
On Tue, Aug 27, 2019 at 5:38 PM -0700, "csalmi-branch" <[email protected]> wrote:
@kwacks would you be willing to email me your support ticket information? I can look into the status of this ticket for you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@kwacks have you heard anything back from the support team ticket you filed? |
I've emailed you the ticket and response. |
1 similar comment
I've emailed you the ticket and response. |
I'm using version 5.0.6 on latest iOS (12.2) and Android api level 28 on a pixel.
Consider the below urls, both have different id's but the first resolves correctly while the second doesn't. The only difference at creating time is that the "J" is capitalized. I tried this with a couple of others with similar results. .
This is an initial data point so more testing may be required to fully uncover the issue but so far I can reproduce this consistently in XF iOS and Android.
The text was updated successfully, but these errors were encountered: