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
Issue with ORKTextChoiceOther not behaving as expected #1556
Comments
Thank you for raising this issue. Since this issue was raised, we've published new versions of ResearchKit to main and haven't seen more info posted here. If you’re still seeing this issue in the latest release, please let us know, otherwise we will close it. |
@louie-apple We are unfortunately experiencing the issue that the "other" text field does not show up in the latest version on the main branch. You can reproduce it by opening the ORKCatalog app and navigating to the "Text Choice Question". Selecting "Other" does not present the text field: Interestingly it seems to work in the Form example: We noted this as we were updating ResearchKitOnFHIR and detected that one of our automated tests failed and caught the regression. |
@PSchmiedmayer Thank you for sharing this with us! We are taking a look! |
Thank you @louie-apple! |
Hi @PSchmiedmayer |
Amazing, thank you @louie-apple; I will take a look at this later this week. Thanks for working on an update! 🚀 |
When ORKTextChoiceOther.choice is used for allowing an "Other" text entry in a single-choice question with the exclusive parameter set to true, the expected behavior is not consistently observed. The issues are twofold:
Steps to reproduce
Expected Behavior
Actual Behavior
Code sample
The text was updated successfully, but these errors were encountered: