Florent De'Neve
Florent De'Neve
I can't reproduce either. Assuming this is fixed. Please reopen if I'm mistaken.
Oh wow, now I see it! It only happens on the first try, if you missed it you have to try again.
The proposal sounds good to me but >@bernhardoj I still saw some reports not making OpenReport API call with the mentioned changes but I think that could be fixed in...
@eVoloshchak can you please review the proposals?
@eVoloshchak based on your investigation and description, I would say let's go with @mollfpr's proposal. One thing I'm unclear on is: >wait for the second approach to work on all...
Right, is this problem fixable @mollfpr ?
That feels a bit overkill to me but I don't know a whole lot... what do you think @eVoloshchak ?
We discussed this internally with Contributor+s. The more discussion we are getting on this issue, the more this looks like something that needs to be fixed with `Touchable` in react-native-web....
Maybe this stack trace helps? ``` .getAttachmentName (address at index.android.bundle:1:2767055) .onPress (address at index.android.bundle:1:2763808) .onPress (address at index.android.bundle:1:2759457) .triggerPressAndUpdateSuccess (address at index.android.bundle:1:2761433) .onPress (address at index.android.bundle:1:2668225) ._performTransitionSideEffects (address at index.android.bundle:1:324697)...
Thanks for looking into this @hellohublot. @Santhosh-Sellavel how does this proposal sound to you? 🙏