Anvil new Editor debug log off

Anvil Q&A
1

Good day everybody,

First I want to congratulate the Anvil team for the roll out of the new editor.
Really nice work and I have switched to it since it really helps productivity.
The only problem I have foud this far is the behaviour of the debug session when using authentication.
on the old editor you would authenticate the first time it run and the next runs would not ask authentication again (except when hitting the cookie expiration).
From the usage I have done so far in the new editor on every run needs to be authenticated.
Is this normal or I am doing something wrong?
I have managed to comment out the authentication part of the code to to make it easier (when mfa is in place its a little bit anoying) but I wonder if there is something Im missing.
This is rally a minor problem in contrast with the benefits but if comes from wrog usage from my part Id love to know it.
Thaks in advance for any tips.

2

I feel like I’ve experienced something similar intermittently but I’m not sure when/why. Does it depend on whether you use “Run in new tab” or not?

3

I’ve seen that now and again, too, but it definitely isn’t happening to me at the moment.

4

Well I think it was almost every time for me (either using custom logon or the functions for logon process) and it didn’t make any difference if in new tab or otherwise. I’ll try some empty apps with only various logon types to pinpoint it more methodically,
Now I know Im not the only one that faced it.

5

Hi @Eternal_Newbie,

It’s great to hear the new editor is helping your productivity!

I’ve tried to recreate the issue you’re having but the login status is being preserved between sessions. If you can recreate the issue in your empty apps, could you let us know which browser you’re using as well as what sign-in method you’re using?

Thanks,
Ryan

6

I stopped running the IDE in Incognito mode. Haven’t had a log-in problem since.

1 Like
7

Hi all,
@p.colbert yes that would explain the problem but I don’t use the Incognito mode. Thanks for the tip though.
@ryan I use mostly Chrome and I update it frequently. I think I tested an Edge for this particullar problem to no avail.
To make sure that Im not doing something sily with the code I share the below:

No need to create an account login with user:test@test.com pass:123
The way I test it:
-Start once and login (usually in New tab
-Write and delete something in the code to trigger the “the app has changed” ribon
-I click on the click here to restart (either from the app tab or in the editor)
-The app restarts and prompts me to login again.
Feel free to test it your self to see that you get the same reaction.

Thanks in advance for your efforts.

8

Just checking: on Chrome/Edge, have you enabled third-party cookies for the relevant url? And no extensions like Privacy Badger?

9

Does your Users service have the Remember Login Between Sessions checkbox checked? That may or may not be the default.

1 Like
10

On the Chrome I make the tests I have checked “Block third-party cookies in Incognito” and no urls on costumized.
I don’t have any security and privacy extensions.

1 Like
11

@jshaffstall Well that solved it !!! When having the “Remember Login Between Sessions” ticked when login in keeps the allready loged in state at the next run. I could add it even if I don’t want it and remove it in production versions. I switched back to Classic editor to test it and in Classic it makes no difference. It keeps the loged in state even when “Remember Login Between Sessions” is not used. So there must be a difference in behaviour between them but since I have a work around it’s ok.

Thanks for your time gentelmen I will consider the case as closed.

2 Likes