question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

After version 0.2.0-nightly-200713151818 I'm unable to login

See original GitHub issue

Hello,

I’m implementing a solution with login with IdentityServer 4. Starting with version 0.2.0-nightly-200713151818 the login does not complete.

The process is:

  1. In a certain page, call the authentication/login
  2. The user is redirected to the IdentityServer. In here user log in and is redirected to the authentication/login-callback
  3. The login is completed and redirected to the calling page.

Starting with version 0.2.0-nightly-200713151818, step 3 never executes. The RemoteAuthenticatorView CompletingLoggingIn event is called, but does not go from there. The browser freezes and some times it gives an error:

Stacktrace: 
Error
    at 640908 (https://localhost:44312/_framework/wasm/dotnet.3.2.0.js:1:19012)
    at _emscripten_asm_const_iii (https://localhost:44312/_framework/wasm/dotnet.3.2.0.js:1:19197)
    at wasm_logger (https://localhost:44312/_framework/wasm/dotnet.wasm:wasm-function[3126]:0x9ab09)
    at eglib_log_adapter (https://localhost:44312/_framework/wasm/dotnet.wasm:wasm-function[6030]:0x10e78d)
    at monoeg_g_logstr (https://localhost:44312/_framework/wasm/dotnet.wasm:wasm-function[4574]:0xc99e6)
    at monoeg_g_logv_nofree (https://localhost:44312/_framework/wasm/dotnet.wasm:wasm-function[2192]:0x60c59)
    at monoeg_g_log (https://localhost:44312/_framework/wasm/dotnet.wasm:wasm-function[132]:0x2ffc)
    at monoeg_malloc (https://localhost:44312/_framework/wasm/dotnet.wasm:wasm-function[161]:0x3c89)
    at stack_frag_new (https://localhost:44312/_framework/wasm/dotnet.wasm:wasm-function[2019]:0x59758)
    at add_frag (https://localhost:44312/_framework/wasm/dotnet.wasm:wasm-function[1430]:0x3ccf2)
Could not allocate 4096 bytes
undefined
undefined
Uncaught RuntimeError: abort(undefined). Build with -s ASSERTIONS=1 for more info.Uncaught RuntimeError: abort(undefined).

Some times the step 2 freezes and the user is not redirected to the IdentityServer.

If I go back to version 0.2.0-nightly-200713124218 it works OK with a fast login.

Best regards,

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:14 (12 by maintainers)

github_iconTop GitHub Comments

1reaction
Ratomircommented, Jul 17, 2020

Hi, sorry, I forgot to include a script in the index page for the authentication service. Never mind, I fixed that and upgrade the Ant-Design on the latest version and it works as expected on my demo repository. Also, It works now in my project, which is good.

We don’t need to roll back into the past and looking differences between builds of 13th and 14th July. It would be hard to match that.

You can close the issue.

Kind regards,

1reaction
nelsonbatistacommented, Jul 17, 2020

Hi ElderJames,

I’ve upgraded and added the avatar again and it is working. Thank you very much for your help.

Read more comments on GitHub >

github_iconTop Results From Across the Web

No results found

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found