+1 as it's been... 3 years!
I know there's conflicts happening when it's on by default, but let us resolve those after-the-fact on mobile view please.
The mobile native option doesn't work for a lot of us, since we don't want folks downloading yet another app! (and for us to build a whole new seperate retool app in parallel!!).
I am getting this component interection error when I try the show on mobile option. The workaround suggested in the comments above also doesnt work.
How does one proceed?
Hi @Bhushan_Dabir,
Unfortunately, I am not aware of another workaround for this bug 
I might try moving a couple of mobile components around to see if it helps 
Fairly new to Retool and have been having fun with it so far ... however, this issue makes having a reasonably responsive webpage very tedious (nigh impossible for the charity I'm supporting). Is there any known workaround or expected timeline for a fix of the "intersection bug"?
Hi @Annie_Ellenberger Unfortunately, I don't have a timeline yet
I don't have a clear workaround to the intersection bug, but I have been able to get around errors like "Could not make visible on mobile because component intersects with ComponentName", by going to ComponentName, and toggling visibility. Sometimes, you will get the same error with another component and need to handle that error in the same way. Once you get to a component that isn't throwing the error, toggle visibility on that component, and then you can go back and show previous components.
For use cases that rely on mobile device access, we recommend Retool Mobile
Is there any update on the intersection issue? This is the largest pain point in retool by a wide margin. I am starting to dread adding new features to existing pages because it means I will have to fight retool to add my new components to the mobile web version.
We should not have to move everything out of the way just to make space for new components and then shift the entire layout again to fix it. This process takes longer than building the new feature itself. Even if adding new components to mobile just automatically added them to the bottom of the page instead of giving the intersect error - that would be an amazing improvement. Then at least I could then drag the component to the right place on mobile without having to first move everything else out of the way just to get the component to appear.
+1 this is a much harder than it needs to be, why would anyone not want to be able to view on mobile if needed? Would be better to just be able to turn off mobile entirely if a dev team wasn’t planning to support mobile.
Hey @Steve_Crawford, I don't have a timeline to share on the intersection bug just yet, but I've flagged your check-in with the team. @Josh_L I've also added both your +1s to the internal feature request for defaulting "show on mobile" to true. I know this has been a long-running pain point, we do have both tracked and I'll update this thread when there's movement! Thanks for your patience! 