There are a couple different scenarios where a login record could have a blank application Id. Usually it is #1 or #2. It occurs in scenarios where the user can have a JWT/access token that does not have the application Id in it.

If a user is not registered for the Application they are logging into FusionAuth makes a login record when a user is created since FA makes a JWT upon user creation If you use the Login API, you can log in without an App ID because you don't have to provide an application on the API call.

@batmysta Going to link to this issue.

I ran into a similar issue recently while trying to upgrade my stack. It seems like FusionAuth is generally pretty stable on the LTS versions, but things can get a bit 'interesting' if you're jumping to the absolute latest bleeding-edge Node release before they've officially validated it.
I've found that sticking to the even-numbered LTS releases usually saves a lot of headache with the client libraries. Are you seeing specific crash logs, or is it just a dependency resolution error during the build?

@mark-robustelli I just upgraded to 1.64, still happens, exact same behavior

@batmysta I know this is a bit of a "trick" answer, but the reality is the right answer depends on what exactly you want the user to have access for. I understand that the roles in FusionAuth may give more access than you may like (I.E. MFA is a tenant level settings, but there is no role just for MFA edit.), but there are some other options.

Again, depending on what you want to do and what version you are running, there is the idea of the Tenant Manager applicaiton. This will still not help you with MFA settings thought.

The other option is using the APIs. Since everything in The FusionAuth admin UI is API first, you could create your own application that would allow users you choose to edit them.

Hope this is useful.

@hvfa Apologies for being a bit AWOL. I hope for things to slow down and be able to take a look at this a little more closely next week.