Replies: 2 comments 2 replies
-
Why are you adding a |
Beta Was this translation helpful? Give feedback.
0 replies
-
Because it's the obvious API to use that's identical across multiple
dynamically added controls.
But that's kind of off-topic, the question is. What suddenly caused it to
stop working, just on iOS?
…On Tue, 28 Nov 2023, 17:48 sjordanGSS, ***@***.***> wrote:
Why are you adding a TapGestureRecognizer to a Button? Button has its own
properties for Command, CommandParameter and Clicked, so you don't need
to add a TapGestureRecognizer to receive user interaction with them.
—
Reply to this email directly, view it on GitHub
<#19083 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJFPZKWTAKLXBYYXYRCRUDYGYIWJAVCNFSM6AAAAAA76A2256VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TMOJUGYYTO>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Are we doing something wrong? We upgraded our app from MAUI 7 to MAUI 8. On Android it went smoothly, but on iOS every button whose click handling relied on
TapGestureRecognizer
stopped working. Since we dynamically load our UI, this meant that almost everything in our app stopped working, except the static settings screen, login and logout.Since I can't fathom that the people behind MAUI would release a new version where something as basic as buttons don't work, I'm really puzzled what we're doing wrong.
Anything that adds a
TapGestureRecogniser
to aButton
seems to break the button functionality, includingBehavior
s for animation and haptic feedback.Beta Was this translation helpful? Give feedback.
All reactions