Hello,
When I add an action to a screen like this: Markup 2021-09-13 at 20.29.27.png - Droplr
Then the screen is pushed down and back up again. See video here: RPReplay_Final1631539658.mp4 - Droplr
All the screen action is doing is updating the user’s DB with some data.
Anybody seen this weird behaviour? Is there a way to avoid it?
Hi @creativechili !!
For me No.
Hello @dilon_perera
It happens automatically, no scrolling or anything. It looks like the actual execution of the screen action is taking place (database update), and it somehow affects the screen when that happens. If I remove the screen action, there is no wobbling. 
@creativechili In your home screen are you using a list? 
@dilon_perera Yes, and the list data is pushed over to the “radio player” screen. So basically I update the user database with the radio channel that they selected. All works perfect, except the jumping effect.
@creativechili try to set that update action In the list . I mean in your home screen list
@dilon_perera I did that first, but doing it that way there is a small but annoying delay from the time they click until the new screen loads. So I thought it would make more sense to have that action on screen load and make the experience more fluid.
@creativechili but when you add that action to the screen it have to work.
@creativechili can you send a screen recording about setting up the action and the output?
@dilon_perera Sure, have a look at this: Screen Capture on 2021-09-14 at 17-10-20.mp4 - Droplr
Happen the same to me
does that happening in the Adalo preview?
@dilon_perera No, only in the native app. What I think is happening is that when the action is executed, it somehow affects the UI, but it should not since that is a backend action and it has nothing to do with the UI.
@creativechili put that update action on the Audio player . I mean when you add your audio player you can set the action when the music over. So try to set the action when the music over and check.
Thats not a valid workaround since I am doing an audio stream with autoplay, so there is no start or stop action. One would think the screen action should work without messing with the UI though.
Hi @creativechili,
Is there any specific reason you put this action to on-screen-enter? As an alternative, you can update Logged-in User on the screen before.
Best regards, Victor.
@dilon_perera I see now, this is a pretty long conversation.
Hello, it has been six months and this issue isthe same. I still find it hard to understand why a backend action affects the UI as it does. It makes the app look bad. Perhaps someone at Adoalo can look at this?