Skip to content
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

View Crawler crashes #507

Closed
gauravarora90 opened this issue Oct 14, 2017 · 7 comments
Closed

View Crawler crashes #507

gauravarora90 opened this issue Oct 14, 2017 · 7 comments

Comments

@patedit
Copy link
Contributor

patedit commented Oct 18, 2017

Hey @gauravarora90 ! Thanks for writing in! This is a very interesting crash that will be fixed in the next release (#508).

On Jelly Bean and below, the hashCode method for the com.android.util.Pair.java class assumed the first element of the duple is never null (see here: http://androidxref.com/4.1.2/xref/frameworks/base/core/java/android/util/Pair.java#62). It was later modified in following releases and that's why it only crashes on 4.1.X.

Thanks!

@sneerin
Copy link

sneerin commented Nov 23, 2017

It's almost December and no fixes yet, we are paying customer, but this shit will make us leave your product. really.That's something not acceptable.

@patedit
Copy link
Contributor

patedit commented Nov 28, 2017

hey @sneerin! A fix was implemented last October and it's currently on master. There has not been any release since then but you can point your gradle file to master 👍

@beast-shubham
Copy link

I don't understand, @patedit how does our pointing to Master solve the issue. I request you to please make a stable (tested) release with this fix (or a Hotfix), coz our app has quite a lot users on these Android versions.

@patedit
Copy link
Contributor

patedit commented Dec 12, 2017

@beast-shubham master contained the fix and is safe to point to that branch since it's stable. You can point an SDK to his github repo using gradle. Anyway, latest release 5.2.2 contains that fix :)

@beast-shubham
Copy link

@patedit thanks for the quick reply. I appreciate it. :)

I have always been using 5.+ version in my gradle, so I assumed I was always on the latest version. Do u think changing it to 5.2.2 would fix this.?

@patedit
Copy link
Contributor

patedit commented Dec 12, 2017

You can safely leave 5.+ and next time gradle syncs it will fetch the latest version 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants