-
Notifications
You must be signed in to change notification settings - Fork 38
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
Opening URL on footer press causes images to "get stuck" #61
Comments
Is it really necessary the use of all those methods? If you just open the link on your onPress method I think it will work as you want const onPress = () => {
Linking.openURL('https://google.com');
} const stories = [{
id: 'user1',
name: 'User 1',
imgUrl: 'user1-profile-image-url',
stories: [{
id: 'story1',
source: { uri: 'story1-image-url' },
renderFooter: () => (
<TouchableOpacity
onPress={onPress}
style={styles.touchable}
>
<Text>{'Link to google'}</Text>
</TouchableOpacity>
)
}]},
]; |
In my case it is necessary because I need to open not only external links in the browser, but also links to other screens of the app, and in order to see them I need to hide the modal explicitly, otherwise they'll just open in the background (underneath the modal). |
At this point, I found only one possible workaround of the mentioned issue (when images or other elements like footer, content 'get stuck'). src/components/Image/index.tsx, line 74 - add
src/components/Footer/index.tsx, line 26 - add
src/components/Content/index.tsx, line 26 - add
After these changes the issue seems to be gone. |
Hi,
I have a story with 2 images and a footer for each of them. The footer (returned via
renderFooter
function) looks like this:The onPress function is:
So, the issue is - after pressing the footer, opening a URL (it can be an external URL or just a different screen of the same app) and going back to viewing the same story, the second image "gets stuck" and it won't switch to the first one when tapping the sides of the screen.
Here is the video:
example.mp4
From my experience, this issue only occurs when opening URL on the second image (I didn't encounter such behavior when opening URL on the first or third image). Version of the library in my case - 1.2.6.
Could you please look into it, if possible? I tried to figure out the cause of the issue by myself, no luck so far. I would highly appreciate any info on this matter.
The text was updated successfully, but these errors were encountered: