Open adamrainsby opened 8 years ago
Hi @adamrainsby, can you please explain what the thinking is behind these changes? I see you added the empty onLayout but not sure what the purpose is, is this still a work in progress or does it work with these changes?
@gr4yscale See this issue for the onLayout thing. https://github.com/facebook/react-native/issues/3282
If you want to contribute and get it working with the animation again that would be great. At the moment it literally just shows and hides the content without any animation so it definitely can be improved.
Hey guys, thanks for moving this forward.
I would opt for a solution that retains the animations. @gr4yscale Have you had any luck fixing this?
@naoufal Just to be clear, the animations still work on iOS but it just opens and closes on android. That is an improvement on it not working at all on android.
I think it should be merged in and then we can open an issue for animations on android?
@adamrainsby you're right. Before merging, could you post a video of the example running on Android?
@naoufal I had to do a bit of work to get the example app running on android. I've updated my PR with those changes.
iOS specific components like NavigatorIOS were stripped out for the android version but they are still there when running on iOS. I also updated the version of react native to the latest version because there was a bug where the background would disappear after pressing the accordion.
Not sure the exact version this was fixed but for now we can say there is android support from 0.23?
@naoufal Is this ok?
@naoufal if this is okay , could you please merge the code and do a release ? i can t use your great module at the moment since my app has to be android / ios compatible. Thanks you !
+1
@adamrainsby Sorry for being MIA all. @adamrainsby If you rebase this branch, I'll gladly merge it.
@naoufal : Here is my test of @adamrainsby . Since i have copied directly @adamrainsby fork into my node_modules dir , i had to install react-tween-state and everything works fine ( except animations of course, but may that could be related to a tween effect or duration ? ) .. here is a screen cast :
@huitiemesens You can put "adamrainsby/react-native-accordion" instead of a version number in the package.json and npm install as usual instead of copy and pasting.
@adamrainsby thanks for this tips, i m more a composer guy , i didn t know that could be done within a package file
hi, I am facing some issue. I am using "react-native-accordion": "0.2.4" library for my project. This is working fine in IOS. when I run my app in android device in debugging mode. Then app is running fine. But if I used signed apk in same device then it is give this error. here I paste my application crash report log which are shown in android monitor. Error given below.
FATAL EXCEPTION: mqt_native_modules Process: com.ampsmobile, PID: 2139 com.facebook.react.modules.core.JavascriptException: Requiring unknown module "react-native-accordion", stack: t@2:387 i@2:177
In order to keep it clean @naoufal could you please merge this one ? Thanks
Apologies @huitiemesens, I still need to rebase. I'll try to do it soon.
@adamrainsby don t worry i already switch for your fork in my package.json , since @naoufal seems afk for a while now ...
In order to fix a great bug ( avoiding to compile a signed android apk ) could you please take a look at https://github.com/naoufal/react-native-accordion/pull/33/commits ( its basically renaming index.ios.js to index.js ) ! Thanks you !
@huitiemesens I already did that in my fork. Are you still having issues with it?
@naoufal Rebased, could you merge?
My last pull request had a bug. This one should work.
https://github.com/naoufal/react-native-accordion/issues/16