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

Android cannot be dragged and dropped #161

Open
bwor opened this issue Dec 3, 2018 · 7 comments
Open

Android cannot be dragged and dropped #161

bwor opened this issue Dec 3, 2018 · 7 comments

Comments

@bwor
Copy link

bwor commented Dec 3, 2018

Running demo on android emulator, unable to drag and drop normally

@fe-linjin
Copy link

I also found this issue!

@chetstone
Copy link
Collaborator

I'm seeing this issue on the device after upgrading to react-native 0.59. I'll look into it. @nihgwu if I find a solution, can you please review?

@nihgwu
Copy link
Collaborator

nihgwu commented Apr 5, 2019

@chetstone sure

@chetstone
Copy link
Collaborator

Trying Sortable with different RN versions, I find that the example works fine with 0.57.8.
0.58.6 has a serious problem --- when a row is picked up, it shifts the opening slot by one.
In 0.59.3, it simply doesn't work. You can't pick up the row and drag.

Looking at the Changelog nothing obviously related jumps out for me except the the changes in Android SDK level.

@kangju1
Copy link

kangju1 commented May 19, 2019

has this been solved or any further progress?

@chetstone
Copy link
Collaborator

chetstone commented May 19, 2019 via email

@chetstone
Copy link
Collaborator

I've decided to change to react-native-sortable-list in my app. The code is much cleaner, it works better, especially when dragging to the end of the list, and it's compatible with RN 0.59. At least on Android. I haven't tried with iOS. One downside is that it doesn't seem to work well with very compact lists--- you need to have a bit of padding/margin between elements.

@nihgwu Since you're no longer working with react-native and I'm no longer working with this component, should we post an issue looking for a new maintainer? And also, I'm thinking of adding a note at the top of the README suggesting people not use this component for new projects. What do you think?

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

5 participants