Tap trigger interrupted by hover

[defaultfvddx04q8eiy]

Hello,

I have Component A which enlarges and unhides a related Component A' upon Hovering.  These components are Grouped.  The desired outcome is for the user to tap on either A or A' to trigger an action to transition to another artboard.  This works flawlessly in Preview.  However, when I publish the Prototype, tapping on A simply resets the group to the Default State, and replays the animation to Hover state.  (Tapping on A' does work as intended.)

Based on reading other questions and watching some videos, I have tried the following:

1. Changing the Hover Action Easing to "none" - No change in behavior. 
2. Adding a "Tap" state to the Group which triggers a new transition to the desired artboard - No change in behavior.
3. Adding a tap interaction to A in Default State to trigger a new transition to the desired artboard - No change in behavior.
4. Adding a new component (rectangle with no fill) on top of A with a tap interaction to trigger a new transition to the desired artboard - Initially, this appeard to work, but I could not replicate it on other components - perhaps it is interfering with what I tried in (2)?  Either way, this is not a very elegant work-around and I have to believe there is a better way.

I am new to XD, so I'm sure there's something simple that I am missing.  I appreciate your help!

HB

[Spas K.]

Hey there! Will it be possible for you to upload the file somewhere and share the link here or via PM in case it's confidential? Xd has a bit of a limitation when it comes to transitions - it won't do two at the same time, so there might be some conflict in the way it's set up. It would be most useful if I can click around your configuration and figure out what the issue might be 🙂

[defaultfvddx04q8eiy]

Let me see what I can do - my organization limits sharing.

[defaultfvddx04q8eiy]

Is there any precedent for why the funcationality would work perfectly in the Preveiw but not in browser?

[Spas K.]

It's a different type of environment. I remember in the past there were cases where something did work in the preview and not in browser and vice versa, but it's mostly been edge cases and I can't recall what exactly they were.

Won't you at least be able to share some screenshots of the element and layer order, triggers etc? You can just copy the problematic component / artboard to a new file and share that, or recreate the configuration with a few elements so I can see how you've set everything up. There might be a bug there, or a simpler way to do it.