Same here, seems to be a permission issue?
@osdnk Can you fix this? Or is there anything I can do to help?
Probably a permission issue here. Can't clone it either.////
Would gladly help if possible
Under the same title, I'd like to mention that on android it says "This project uses SDK v27.0.0, but this Expo client requires at least v33.0.0"
A year on, no comment from anyone working on this repo, which is a bit awkward for a project that says it's supported by Expo and is on Expo's docs. Especially that its on release 27 (10 major releases ago).
Can only guess this project is dead and one to be avoided.
@fredrivett sure, you can. What鈥檚 the purpose?
You can also submit a PR fixing it and I鈥檓 pretty sure it will be more effective than complaining.
Hey @osdnk, thanks for the reply.
Agreed fixing it would be the most effective solution, but with no sign that the maintainers of this library think this is a problem (with multiple issues being raised over a period of a year with no comment from any maintainer), I'd hope why you can see this doesn't exactly signal "contributions desired".
I'm pretty new to React Native, only have experience with Expo and this isn't an area I can easily contribute on. If the fix is relatively simple and you can point me in the right direction I'm happy to take a look.
Am I right to assume this issue isn't being actively worked on right now?
Thanks for your work on this btw, apologies if my previous comment was overly snarky, I was just surprised to see such little comment on what seems like quite a big issue on such a popular library.
Should be resolved by #1131
Most helpful comment
@fredrivett sure, you can. What鈥檚 the purpose?
You can also submit a PR fixing it and I鈥檓 pretty sure it will be more effective than complaining.