I noticed that on Web and in iOS (in Android everything is just working fine!) Buttons (and Input fields) are in most cases (sometimes they work as expected) difficult to hit:
Example:
the upper button can be clicked on the full button area while the button below is responding only on the upper border of the button:
The setup in appgyver looks as follows with the lower buttons being shown/hidden by variable state (visible true/false) Upper Button and lower Button are in two different containers (Container 2 and Container 3):
I found out, that using the navigation menu (temporarily assigning all pages a navigation entry) and hopping to another page and then navigation can enable the buttons sometimes to work correctly.
I also noticed that sometimes black areas on this page trigger actions on other pages - such as alerts.
Ok thatās very odd, Iāve never seen anything like this before. I canāt help you like this, Iād need to have a look at your app in Composer to be able to have any inkling of whatās going on. Or if youād prefer, you can try removing different aspects of your pages one by one and seeing when the buttons start/stop working.
When I look at the developer console when opening your app, thereās a ton of āMissing required parameter āAdresseāā errors being fired. Perhaps look into your logic to not try to do whatever needs the āAdresseā before you have it, not sure if this is causing some of these problems, but it will be better for the running of the app.
I removed some of your excess empty containers just to get a better sense of what was going on. (You can undo this from History if you prefer)
For some reason if/when the UI starts to respond to clicks I get the error āDie Eingabe des BestƤtigungscodes hat nicht funktioniertā. Whereās this coming from? I couldnāt find it in any buttons on the page (Startseite).
I am aware of the Adresse error - I am currently using this as a workaround to prevent fetching addresses without a parameter. It resolves once the Adress-Parameter is available, will fix this later.
Sorry - correction!
That is quite strange for me as well - this message is on page āAdresse (not Mobilnummer) bestƤtigenā - when clicking āCode einlƶsenā. It is not even on the startpage!
The page is mounted if itās on the navigation menu when the app opens, so this was triggering on app start. This was on several pages, so I moved the logic to be triggered from focus instead.
However, thereās a lot more of this logic in your data variables as well, so you should perhaps have a look for yourself if some of the logic would be better served in page focused instead of mounted. In general you should not expect the page to be in view when it is mounted, only when itās focused. If you have any more of these type of āfocus inputā or other logic attached to page mounts, that causes problems.
I would recommend going through all data variables and other logic to check itās not on page mount if itās doing anything UI related or that it should only be doing after it is in view, and then if the problem persists, remove all other pages from navigation, see if that solves the problem, then start adding them one by one and see which one is causing the trouble.
Unfortunately I deactivated Navigation when trying this. The problem went away probably due to disabling the app navigation, now that I enabled it again, the problem re-occurs.
Any idea how this could be connected to app navigation?
Yep the reason why itās related to app navigation is that the pages that are in the navigation menu are mounted when the app is opened. That means all the logic starts to run at that point, if itās connected to the page mounted event. Remove any logic from the page mounted events (except hide spinner) to be in page focused instead.
