You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After enabling Speak Selection in Settings > Accessibility > Spoken Content, the “Speak” option appears in the popup when selecting text in Readium Reader v2.7.3 (please refer to the attached screenshot). However, when tapping on it, there’s no sound. When doing the same in Safari or Chrome, the selected text is pronounced as expected.
How to reproduce?
Enable Speak Selection in Settings > Accessibility > Spoken Content.
Open any book in the Readium Test App.
Select text and look for the “Speak” option in the popup (you may need to tap the “>” button on the far right of the popup to see the “Speak” option).
Tap on the “Speak” option.
Expected result: The popup is dismissed, and iOS starts pronouncing the text.
Actual result: The popup is dismissed, but nothing happens.
Readium version
2.7.3
OS version
iOS 18.1
Testing device
iPhone 14 Pro
Environment
macOS: 15.0.1
platform: arm64
zsh: command not found: carthage
carthage:
Xcode 16.1
Build version 16B40
Additional context
I use the Swift Package Manager.
The text was updated successfully, but these errors were encountered:
Describe the bug
After enabling Speak Selection in Settings > Accessibility > Spoken Content, the “Speak” option appears in the popup when selecting text in Readium Reader v2.7.3 (please refer to the attached screenshot). However, when tapping on it, there’s no sound. When doing the same in Safari or Chrome, the selected text is pronounced as expected.
How to reproduce?
Expected result: The popup is dismissed, and iOS starts pronouncing the text.
Actual result: The popup is dismissed, but nothing happens.
Readium version
2.7.3
OS version
iOS 18.1
Testing device
iPhone 14 Pro
Environment
macOS: 15.0.1 platform: arm64 zsh: command not found: carthage carthage: Xcode 16.1 Build version 16B40
Additional context
I use the Swift Package Manager.
The text was updated successfully, but these errors were encountered: