useFocus does not seem to work in the iOS simulator (tested with VoiceOver)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- react-native, typescript
- Domain
- accessibility, mobile-dev
Research direction
Start with lib/hooks/useFocus.ts and reproduce the reported behavior using the linked sample repository or the useFocus example from the documentation in an iOS simulator with VoiceOver. Compare the simulator result with a physical iPhone, then determine whether the duplicate AccessibilityInfo.setAccessibilityFocus call or simulator behavior explains the issue; done means a confirmed cause and an agreed fix or documentation clarification.
Written by the indexing model from the issue text.
Description
Sample git repo
Snack that doesn't work because it can't install react-native-ama but it is the example from the docs.
I have tried to use useFocus on two different projects (and machines), and neither work with the IOS simulator. I built a further third project and was able to run it on my personal iPhone with voiceover and it seemed to work. It does seem to work on a physical device fine.
Is there anything that can be done about this for those of us who use the IOS simulator as their primary development device?
I even copy/pasted the useFocus code and tried it as a standalone hook since it doesn't rely on anything from the <AMAProvider>. Same thing.
Any help would be appreciated.
Thank you!
Additional question:
Why is AccessibilityInfo.setAccessibilityFocus(elementId); ran twice in useFocus?
- Dominant language
- TypeScript
- Stars
- 295
- Forks
- 22
- Avg merge
- 20m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FormidableLabs/react-native-ama
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
FormidableLabs/react-native-ama#322 · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
FormidableLabs/react-native-ama#321 · 4 comments ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
FormidableLabs/react-native-ama#319 · 4 comments · 1 reaction ·
-
Upgrade linting and add ts:check to automationMay be free again @JDMathew claimed this 699 days ago, and no pull request is open. Open
FormidableLabs/react-native-ama#277 · 1 assignee ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 38/100
All issues in FormidableLabs/react-native-ama
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
prime-radiant-inc/evener#3726 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
FuRongJun-1999/dsh-memory#56 ·
Maintainers usually reply within 1 day
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
pingdotgg/t3code#15682 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openwatersio/slackwater.xyz#152 ·
Maintainers usually reply within 1 day
-
[BUG] 请修改标题为您遇到的问题Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
OpenListTeam/OpenList-Worker#103 ·
Maintainers usually reply within 1 day