Its very annoying when there is some access rule or other security related setting hiding somewhere in the app that causes a button to become invisible once deployed. Studio pro provides no method of checking what it causing this, and the developer has to spend time carefully combing through all access rules and related microflows to try and find whats causing the button to become hidden. If the platform can detect when to hide the button, then it should be able to also tell us before we deploy what is causing it to be hidden. This issue becomes very apparent when you have a button that launches a complex microflow where its no longer an easy task of just looking at the 1-2 entities involved as there could be dozens of entities spanning mutliplpe modules. Instead, there should be some type of role trace tool that developers can use where they can open up a dialong popup from a button or other widget, select the role they wish to check and then get a list of access rules that are not allowed which would prevent access to that widget. If this can't be added or made easier for the developer, then the platform needs to stop performing these hidden checks behind the scenes.
definitely been there. Carefully sifting through entities and security settings only to realize that the role in question was not grant proper authorization before deployment. Digress..