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
The hoops you have to jump through, to fail at the end #332
Comments
I just used create react native app to create a fresh react native project. I ran into similar issues. There isn't even a Not sure how to go about trying to solve this. |
@Unforgiven-wanda you are absolutely spot on. Too many OS projects make claims which are not even true just to increase their popularity. And the fact that most of us in the community have the mentality of "it is just an OS project so you can't expect the contributors to maintain it properly" has led to the community not holding contributors accountable to what they claim their project does. I have nothing against releasing half assed OS projects as long as this is clearly stated in the readme, such that developers who are actively spending time on selecting an OS project to add to their development stack can look elsewhere. p.s. I am glad I noticed this issue before going through the same hoops to try to get it to work with the latest version of react and react-native. |
We appreciate the criticism. TL;DR: Not TL;DR: Unfortunately, as the App Builder advanced later into it's lifespan, it absorbed more and more developer time, leaving little to no time for the developers behind the UI toolkit to dedicate to maintenance, fixes and improvements. We've now revitalized our efforts to bring the UI toolkit back up to snuff. A result of that is immediately visible from the version 0.22.0 update which makes it operational with React Native 0.50.3. The next thing I will personally look to do is cleaning up the documentation. Introducing undocumented components to it, improving existing component code snippets as well as fixing any inaccuracies that may exist. Again, we appreciate the criticism. |
Thank you for your answer @Vladimir-Vdovic |
I was about to start using this package but this issue made me feel scared a bit. I hope that it returns to being a well-maintained package :). |
I'm going to close this issue, since the issues described in it are resolved (from my understanding). Feel free to keep discussing in the issue. Short update: |
Now this is as much an issue as rant as the amount of problems this library raises is insane, so please bear with me:
Some the issues I encountered when using it:
react-native/Libraries/Renderer/shims/ReactNativeBridgeEventPlugin
, forcing me to fiddle with the peerDeps to fix itcannot read property 'shape'
which can only be fixed by installing additional depsprop-types create-react-class
and fiddling with node_modules/react/index.jsAnd all this while keeping in mind that you have to redo all those steps every time you update, add a dep, or clone the project anew, which is a huge waste of time.
And finally comes the time to build the app: You're thinking "Oof! That took the entire day, but hey, at least the app looks beautiful" and lo and behold, the released apk is completely broken and crashes at startup, possibly because of proguard, but so far I haven't been able to pinpoint the exact cause.
Is this the way Shoutem has to gently steer us towards expo? Because if that's the case I believe you could simply add at the top of the readme: "Does NOT work outside of expo; use at your own risk" then we'd know not to waste our time
I've been following Shoutem for a long time now, and been meaning to use it ever since, but the ridiculous amount of issues that it brings with him just don't make it worth it, at this point something like Native-base or KittenUI, although less beautiful in my opinion, are way better as they come without the headache and the hours of debugging
Please do not take offence at this issue: I understand fully that this is one of the drawbacks of open-source projects and that the contributors are in no way obligated to fix these issues, but I believe a bare minimum of explanation about what this lib can and can't do, and what to expect of it in different environments would go a long way.
tl;dr: Shoutem hardly works outside of expo, please update the readme to clarify this point.
Thank you.
The text was updated successfully, but these errors were encountered: