-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
URI formate exception #73
Comments
Hi @purna-jobget. Thanks for opening this issue. I can see two parts here:
|
@alexstyl @purna-jobget this is a problem for us too. We're getting Crashlytics crashes about it. Unfortunately me trying to fix it would break everything. We're looking forward to it being fixed. Great work on the library btw! |
@nwainwright can you share android versions and OEMs you are getting the crashes from? |
@alexstyl Android 13 Galaxy S22 Ultra is one of our users that has crashed. Thank you! |
@nwainwright other android versions and models would help. trying to understand if this is OEM specific, Android version specific or unrelated. |
@alexstyl Significant Contributions by manufacturers:
By OS Version
|
@purna-jobget perfect. thanks for having a look. @nwainwright could you kindly check as well? That being aid, I will have a look this week (if not today) at the AOSP to see if something changed on Android 11+ which I was not aware about. |
Just pushed a fix for this in b8a3294 Keeping this open until released. EDIT: For those curious about why the URI might be invalid: I had a look at the AOSP. They are ignoring Uris they are not expecting. ContactStore will do the same to match that behavior. Those Uris are probably custom Raw Contact Uris created by apps, so probably not important for this part of the code base. |
@alexstyl Thanks, waiting for release :) |
@piavan07 Expect a new version this weekend |
Closing as done. Get the fix in 1.5.0 |
Faced the following issue while using the library in prod, any possible solution for
We just fetch the contacts in our application to show them to our users.
The text was updated successfully, but these errors were encountered: