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

URGENT: Volunteer Page #258

Closed
danilobatson opened this issue Jan 20, 2021 · 2 comments
Closed

URGENT: Volunteer Page #258

danilobatson opened this issue Jan 20, 2021 · 2 comments

Comments

@danilobatson
Copy link
Collaborator

Describe the bug
The different roles on the volunteer page don't expand so you can see the job duties

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'spicygreenbook.org/volunteer'
  2. Click on 'the +'
  3. See error

Expected behavior
The copy should expand so you can see the duties of each role

Screenshots
If applicable, add screenshots to help explain your problem.
image

Desktop (please complete the following information):

  • OS: iOS]
  • Browser [ chrome]
@C-Garza
Copy link
Contributor

C-Garza commented Jan 21, 2021

This looks like another issue when react-native-web was upgraded to version 13 in this commit. The issue is with react-native-gesture-handler and it's described in this link here.

Possible solutions are to downgrade react-native-web or to upgrade react-native-gesture-handler to at least ~1.9.0.

I upgraded react-native-gesture-handler in my local branch and it seems to work just fine but I haven't really tested if there were any breaking changes. Can look more into it tomorrow unless someone else picks this up by then.

@JeroenGoddijn
Copy link
Contributor

This looks like another issue when react-native-web was upgraded to version 13 in this commit. The issue is with react-native-gesture-handler and it's described in this link here.

Possible solutions are to downgrade react-native-web or to upgrade react-native-gesture-handler to at least ~1.9.0.

I upgraded react-native-gesture-handler in my local branch and it seems to work just fine but I haven't really tested if there were any breaking changes. Can look more into it tomorrow unless someone else picks this up by then.

Running npm upgrade [email protected] seems to fix it for me too, when I test locally.

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

3 participants