userinfo | Getting detailed information about the user from the query | Database library

You can use flex to align your element. like Bootstrap classes d-flex and justify-content-between. Wrap your content in above classes like below code snippet.

For more alignment options check bootstrap official docs https://getbootstrap.com/docs/4.6/utilities/flex/#justify-content

Users of external identity providers have to be registered before the can login.

You can find the details here: https://developers.tapkey.io/api/authentication/identity_providers/#working-with-users

When it is necessary for your use case, that these users are automatically created when they login, please send a request to tapkey support and they will enable this feature for you.

Try setting up the toggle-dark-mode event handler once when you start your Electron app.

Your code doesn't need to be in the ready event even.

Because every time you tap the button, you create another timer.

Did you ensure, back-end side, you were receiving the email and password properly before even trying to match passwords?

I think the problem lies here:

The way you use it caught my attention. Out of general use. Generally, api operations are done with packages such as saga or thunk. Action is only used as a hyperlink. I suggest you review the article below. I think this build will solve your problem.

https://blog.devgenius.io/reactjs-simple-understanding-redux-with-redux-saga-f635e273e24a

The solution you're looking for depends on how your app is designed. There are several things you can try out:

• Keep your app modularized - as @ADM mentioned split your repository into smaller
• Move live data out of repository - it is unnecessary to keep live data in a repository (in your case singleton) for the entire app lifecycle while there might be only few screens that need different data.
• That's being said - keep your live data in view models - this is the most standard way of doing. You can take a look at this article that explains Retrofit-ViewModel-LiveData repository pattern
• If you end up with complicated screen and many live data objects you can still map entities into screen data representation with events / states /commands (call it as you want) which are pretty well described here. This way you have single LiveData and you just have to map your entities.

Additionaly you could use coroutines with retrofit as coroutines are recomended way now for handling background operations and have Kotlin support if you wanted to give it a try.

Also these links might halpe you when exploring different architectures or solutions for handling your problem architecture-components-samples or architecture-samples (mostly using kotlin though).

I think the return value from the Promise inside the then callback does signify that the login operation is successful. But that doesn't mean you will get isAuthenticated as true because your handleSubmit would have been closing over the previous value of isAuthenticated which was false.

You would require to have a custom useEffect which triggers on isAuthenticated and other values that your logic requires.

The following changes should satisfy what you need :-

I was having this issue and I got it working after a little work.

First, I had to configure my project to give metadata write permission in Auth0's dashboard at Applications/Apis.

The two I added were read:current_user and update:current_user_metadata. Then, in my authorize request, I modified both scope and audience.

audience: 'https:///api/v2/'

scope: 'read:current_user update:current_user_metadata openid profile offline_access'

Next, I got the userId by passing my authentication token to auth.userInfo like so.